Vertex Swarm Challenge · packaged static replay shell

Entropy Hunt

A buildable frontend shell for the entropy-driven swarm-search demo. It packages one primary replay console, the latest verified simulation snapshot, and supporting artifacts into one static site. Live snapshots still require local helper scripts.

Open final snapshot Open replay console

Latest verified run

built from final_map.json

coverage completed

0.12

portion of cells fully closed out in the run

coverage current

0.12

live end-of-run coverage after decay

BFT rounds

deterministic claim-resolution rounds executed

dropouts

scheduled failures observed during the run

survivor found

target confirmation was published to the swarm

mesh messages

132

local bus publications captured in the stub

Run duration 30s, grid 5×5, search increment 0.05, completion certainty 0.95.

Replay artifacts

replay by default; live via local helpers

Replay payload — load this into the packaged replay console
Heatmap SVG — standalone snapshot for docs or slides
Final dashboard — self-contained HTML snapshot
Replay console — read-only replay viewer; live mode still needs local helper scripts

python3 main.py --final-map final_map.json --svg-map final_map.svg --final-html final_map.html
bun run build
bun run preview
bun run live:peers
bun run live:serve

Snapshot preview

SVG from backend export

Recent events

latest replay timeline

claimt=20s — drone_1 assigned (2, 0)
bftt=20s — round 5 resolved (2, 0) via single-claim quorum
claimt=20s — drone_2 assigned (1, 1)
bftt=20s — round 4 resolved (1, 1) via single-claim quorum
zone_completet=20s — drone_2 completed (0, 1)
zone_completet=20s — drone_1 completed (1, 0)
claimt=9s — drone_1 assigned (1, 0)
bftt=9s — round 3 resolved (1, 0) via single-claim quorum

Current delivery surfaces

Packaged shell — this `dist/` site for deployment and review.
Replay console — the primary browser surface in console.html; live polling works only when the local helper scripts are running.
Reference mockup — source-only file kept outside dist/ for experiments, not for packaged deployment.
Python runtime — source of truth for simulation/export artifacts.

Known limits

Live polling currently consumes aggregated JSON snapshots, not a direct FoxMQ stream.
FoxMQ and Webots paths are optional and not end-to-end validated in this CI environment.
The packaged shell remains a static site; live data requires running the local helper scripts alongside it.