Explore how a civilization-scale coordination model balances energy, computation, logistics,
validation and human governance. Inspect the assumptions, stress scenarios and unsigned governance proposals.
DETERMINISTIC SIMULATION · NO WALLET REQUIRED
This command deck reads local fixture data. It does not control physical infrastructure, contact providers,
collect signatures or execute payments. “Dominance”, “welfare” and “unstoppable” scores are model heuristics.
Loading the recorded simulation snapshot…
Computer work: scoped tasks, evidence and capacity
Loading the local planning exercise. Read COMPUTER-WORK.md for task scopes, fixture commands and commissioning requirements.
Dominance
…
Assumed monthly value flow
…
Resilience
…
Energy utilisation
…
…
…
Status: …
Guardian coverage
…
Status: …
Bridges
Energy models
…
Energy Monte Carlo
…
…
…
…
…
Status: …
Sentient welfare equilibrium
…
…
Status: …
Modeled energy feeds
…
…
Compute delta
…
Bridge compliance
…
Identity lattice posture
…
Root authority: …
Merkle root: …
Revocation rate: …
Latency window: …
Compute fabric orchestration
…
…
Sharded registry fabric
…
…
Energy window schedule
…
…
Thermodynamic allocation policy
…
…
Equilibrium ledger
…
Primary action
Thermodynamics
Game-theory posture
Pathways
Action path
Recommendations
Equilibrium action path
…
Mission lattice
…
…
Mission thermodynamics
…
Priority action queue
Mission hierarchy
Loading mission lattice…
Logistics corridors
…
…
…
Settlement lattice
…
…
Stability ledger
…
Composite confidence: …
Verification vectors
Alerts
Owner proposal structure
…
…
Transaction set hash: …
Selector set hash: …
…
Federated systems map
Loading interstellar map…
Dyson Swarm timeline
Preparing Dyson programme timeline…
Scenario stress sweep
Owner directives
Guardians: …
Operations: …
Status page: …
Bridge failover: …
…
Federation readiness
YOUR FIRST COMPLETE RUN
From assumptions to a reviewable result
Read the model. Inspect this profile’s config files. Recorded dates identify fixtures; they are not freshness claims.
Reproduce it. From the repository root, run nvm install, nvm use, npm ci, then npm run demo:kardashev-ii:orchestrate.
Verify it. Run npm run demo:kardashev-ii:orchestrate -- --check. This compares artifacts and enforces critical/high readiness checks without writing files.
Experiment. Copy the profile configuration, change one input, and select separate --config-root and --output-dir directories. Compare the ledger warnings and metrics. A stressed model can intentionally fail readiness.
Read the evidence correctly. Input hashes establish reproducibility. Encoded calls and owner-selector checks establish proposal structure, not authority, signatures or successful transactions. Safe batches contain placeholder targets and are not ready to submit.
Units. GW measures power; GWh measures stored energy; EF means exaflops. Currency values are scenario assumptions. Thermostat “Kelvin” fields are legacy normalized model parameters, not measured stellar temperatures.