Read the mission
Inspect jobs, specifications, rewards and scenario objectives. These are configured requirements, not completed deliverables.
demo/infinity-symphony/config/mission@v2.json ↗Scale & orchestration
Infinity Symphony
Inspect the Infinity scenario, its orchestration model and preserved guides.
A CLOSER LOOK
How can a mission bundle combine job evidence and owner diagnostics?
For mission operators: inspect the Infinity job manifest, its scenario-specific controls and the assembly of governance evidence.
Follow the wrapper
The script combines ASI Take-Off planning, a mission kit and owner reporting. Review its environment and report-path expectations before using it as a complete rehearsal.
demo/infinity-symphony/bin/infinity-symphony-local.sh ↗Inspect the thermostat assumptions
Read the modeled control parameters and compare them with the defaults of the workflow actually selected by the wrapper.
demo/infinity-symphony/config/infinity-symphony.thermostat@v2.json ↗REAL REPOSITORY MATERIAL
Inspect. Understand. Reproduce.
Reading the exact source at revision 5b4cebb3.
This browser inspection does not execute the demo.
demo/infinity-symphony/config/mission@v2.json
Select a walkthrough step to explore its source.
Full source text
{
"version": "v2",
"scope": "infinity-symphony",
"description": "Planetary-scale coordination drill composed of macro governance, infrastructure, emergency, and trade programs executing under the AGI Jobs v2 one-box orchestrator.",
"jobs": [
{
"name": "Macro Governance Kernel",
"specPath": "demo/infinity-symphony/config/spec-macro-governance@v2.json",
"resultURI": "ipfs://infinity-symphony/macro-governance/result",
"agentSubdomain": "macro.kernel",
"reward": "840000000",
"workerStake": "360000000",
"validatorStake": "720000000",
"deadlineOffsetSec": 7200,
"metadata": {
"objective": "Balance fiscal, energy, and stability mandates across five blocs",
"priority": "critical",
"budget": "1200000000"
},
"notes": "Executes treaty harmonisation, stake re-weighting, and pause rehearsals triggered by the Infinity thermostat lattice."
},
{
"name": "Critical Infrastructure Lattice",
"specPath": "demo/infinity-symphony/config/spec-critical-infra@v2.json",
"resultURI": "ipfs://infinity-symphony/critical-infra/result",
"agentSubdomain": "infra.lattice",
"reward": "760000000",
"workerStake": "310000000",
"validatorStake": "650000000",
"deadlineOffsetSec": 10800,
"metadata": {
"objective": "Deploy cross-continental power, transit, and communications upgrades",
"priority": "high",
"capex": "250000000000"
},
"notes": "Leverages deterministic mission specs to chain job postings, validations, and treasury flows for the macro grid."
},
{
"name": "Emergency Swarm Directorate",
"specPath": "demo/infinity-symphony/config/spec-emergency-response@v2.json",
"resultURI": "ipfs://infinity-symphony/emergency-swarm/result",
"agentSubdomain": "emergency.swarm",
"reward": "540000000",
"workerStake": "220000000",
"validatorStake": "460000000",
"deadlineOffsetSec": 3600,
"metadata": {
"objective": "Stabilise simultaneous coastal, seismic, and epidemiological events",
"priority": "critical",
"coverage": "planetary"
},
"notes": "Bootstraps validator-guided microtask swarms, supply routing, and quality arbitration using existing commit-reveal flows."
},
{
"name": "Planetary Trade Harmonics",
"specPath": "demo/infinity-symphony/config/spec-planetary-trade@v2.json",
"resultURI": "ipfs://infinity-symphony/trade-harmonics/result",
"agentSubdomain": "trade.harmonics",
"reward": "680000000",
"workerStake": "270000000",
"validatorStake": "520000000",
"deadlineOffsetSec": 12600,
"metadata": {
"objective": "Harmonise cross-border settlement, carbon clearing, and validator diplomacy",
"priority": "critical",
"budget": "480000000000"
},
"notes": "Publishes ENS-signed trade ledgers, validator dispute logs, and thermostat triggers for carbon-negative routing."
}
]
}
SHA-256 d8173485b5f762e17c1d6f199759a980f704cbaf1f83dad85cfdd98b6186caf9
FROM READING TO A REPRODUCIBLE RUN
Try the selected path.
Disposable local chainFrom the repository root, use nvm install, nvm use and npm ci with the pinned Node/npm versions. The local driver uses mock assets; its owned development node stops at the end. If port 8545 is occupied, use DEMO_PORT=18545.
Complete environment setup ↗npm run demo:asi-takeoff:localWhat you should observe
The related ASI Take-Off component executes local jobs. Use its fresh receipts to understand the evidence required by Infinity’s broader bundle; this command is not an Infinity-specific full run.
The source inspector above reads bundled repository material. Local commands run separately on your computer. Recorded examples may contain historical timestamps, placeholders and simulated metrics.
MAKE IT YOUR OWN
One useful experiment.
Trace each Infinity job specification and identify where the wrapper selects it. Confirm the effective configuration instead of assuming the scenario name selects it.
THE SYSTEM, MADE VISIBLE
Architecture & relationships
View original Mermaid source
flowchart LR
Operators((Mission Owners)) --> demo_infinity_symphony[[Demo → Infinity Symphony]]
demo_infinity_symphony --> Core[[AGI Jobs v0 (v2) Core Intelligence]]
Core --> Observability[[Unified CI / CD & Observability]]
Core --> Governance[[Owner Control Plane]]WHEN SOMETHING DOESN’T MATCH
Troubleshooting
Port already in use
Choose DEMO_PORT=18545 before the command. Do not connect a demo to an unrelated or valuable chain.
No final settlement evidence
Read the first failed transaction or validation step. Compare the effective mission, committee thresholds and report scope; a partial report is not a completed run.
TRACE THE CHECKS
Verification & next steps
This directory has no standalone test source files. Follow the shared implementation and its behavioral tests before making correctness claims.
For live commissioning, consult the production readiness record.
EVERY VARIANT, PRESERVED
Complete document library
REPRODUCE & INSPECT
Registered commands
Run commands from the repository root after following this demo's guide. Network and owner actions require their documented setup.
No root-level launch command is associated with this source path. Follow the guide or source directory for its own entry point.