Nothing here yet.
This tab is a blank slate โ build a scenario below and click Run in Browser, or upload a real result, to see it here.
(Inner System, Swarm, Multi-Hub, and Solar System already have their own fixed, tested results โ this tab is just for what you build.)
SPACEFLEA
SpaceFlea cannot make deep-space communication real-time. It can make coordinated operation continuous despite the delay.
01
ALL GOOD
โ
02
SEES TROUBLE
โ
03
REROUTES EARLY
โ
04
CONTACT LOST
โ
05
PLAYBOOK ACTIVATED
โ
06
AUTONOMY ON
โ
07
LINK BACK ON
Build a Scenario
Fill this in, then either click Run in Browser for an instant result, or download the file and run it through Python yourself. Either way, it's the exact same real simulation engine โ nothing here is a shortcut or an approximation.
What do these fields actually do? (click to expand)
Duration / Tick length โ how long the mission runs, and how many real seconds pass per simulated step. 300 ticks ร 60s = 5 hours of mission time. Telemetry / Bulk / Critical rate โ the chance, each tick, that the robot generates that kind of message. Telemetry = routine status. Bulk = mining/science data (the thing Smart Mesh protects during a hold). Critical = urgent commands from Earth. Critical expiry โ how many ticks a critical command stays valid before it's too late to act on. Disruption 1 / 2 โ deliberate link failures. Start/End set the window; Ramp controls how gradually it fails and recovers (a real fade, not an instant cliff โ this is what gives Smart Mesh's prediction something to actually detect). Disruption 2's Floor quality controls how bad it gets: 0.04 โ fully down, 0.35 โ flickers but never fully dies (good for stress-testing over-caution). Robot Anomaly โ optional. If set, the robot develops a fault between these ticks. This is what triggers the playbook's guardrail โ Smart Mesh will prioritize diagnostics (or hold safely, if battery is also low) during this window; Basic Mesh has no such awareness at all.
โ ๏ธ This only affects the Custom Data tab. Inner System, Swarm, Multi-Hub, and Solar System are fixed, already-tested scenarios and never change, no matter what you build here.
Disruption 1 (Relay A)
Disruption 2 (Probe link)
Robot Anomaly (optional)
Or Upload Real Results
Once you've run the scenario above through Python, upload the resulting <name>_package.json here.
Routing Mode
The smart mesh notices trouble coming and reroutes data before a link fails.
Playback
SPEED1.5ร
T+00:00
tick 0 / 0
Real one-way signal delay
๐ก๏ธ Operational Continuity โ live
Full capacity
Halted/degraded
Smart Mesh
100%
0%
Basic Mesh
100%
0%
๐ง AI activations0
๐ Reconciliations0
๐ Drops (Smart)0
๐ Drops (Basic)0
Smart vs Basic โ live
Message delivery โ secondary
Delivered0
Dropped0
Critical on-time0/0
link up
degrading / predicted
down
local AI (glows = actively predicting)
critical packet
telemetry packet
Asset Sector Assignments
Static per-robot assignment โ an illustrative slice of the lease concept from the design doc. Dynamic lease expiry/renewal/handoff isn't simulated yet.
Hub Status
drag to orbit ยท scroll to zoom ยท drag the scrubber to seek
Append-Only Prediction Ledger
Every prediction Earth or the robot makes, and what actually happened โ recorded once, in order, never edited. Conceptually the same idea as a blockchain: an immutable, sequential record built specifically so predictions can be checked and reconciled against reality after the fact, not quietly revised.
No resolved predictions yet at this point in the mission.