Read scenario inputs
Inspect actors, workloads, budgets and controls. Values describe a synthetic scenario and must not be interpreted as live economic performance.
demo/LARGE-SCALE-OMEGA-BUSINESS-3/config/omega.simulation.json ↗Scale & orchestration
Large-Scale Omega Business
Explore the large-scale business scenario, its inputs and operator documentation.
A CLOSER LOOK
How do modeled missions turn into an operator control report?
For operators: inspect the business scenario, its inputs and the orchestration logic before using the accompanying interface or network launch paths.
Follow the orchestrator
Trace the configuration through planning, calculations and generated evidence. The separate mainnet launcher is a different, deployment-sensitive workflow.
demo/LARGE-SCALE-OMEGA-BUSINESS-3/orchestrator.ts ↗Review the operator journey
Read the original guide for report locations, UI use and network prerequisites. Preserve the distinction between rehearsal outputs and authorized operational actions.
demo/LARGE-SCALE-OMEGA-BUSINESS-3/ui/operator-playbook.md ↗REAL REPOSITORY MATERIAL
Inspect. Understand. Reproduce.
Reading the exact source at revision 5b4cebb3.
This browser inspection does not execute the demo.
demo/LARGE-SCALE-OMEGA-BUSINESS-3/config/omega.simulation.json
Select a walkthrough step to explore its source.
Full source text
{
"reportLabel": "omega-business-3",
"ipfsGateway": "https://ipfs.io/ipfs/",
"ensRoot": "omega-business.eth",
"nations": [
{
"name": "Solaris Continuum",
"wallet": "solaris",
"ensSubdomain": "solaris",
"mission": "Transmute heliostat free-energy telemetry into autonomous infrastructure credits",
"specCid": "bafybeiaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"resultCid": "bafybeibbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb",
"rewardTokens": "150000",
"deadlineHours": 72,
"budgetUsdc": "5000",
"modeledWorkerCostUsdc": "350",
"estimatedReviewMinutes": 10,
"agentEns": "worker01.agent.agi.eth"
},
{
"name": "Arctic Quantum Accord",
"wallet": "arctic",
"ensSubdomain": "arctic",
"mission": "Balance polar energy reserves with planetary logistics networks",
"specCid": "bafybeiccccccccccccccccccccccccccccccccccccccccccccccccccccc",
"resultCid": "bafybeiddddddddddddddddddddddddddddddddddddddddddddddddddddd",
"rewardTokens": "132500",
"deadlineHours": 64,
"budgetUsdc": "7500",
"modeledWorkerCostUsdc": "480",
"estimatedReviewMinutes": 12,
"agentEns": "worker02.agent.agi.eth"
},
{
"name": "Celestial Silk Road Coalition",
"wallet": "silkroad",
"ensSubdomain": "silkroad",
"mission": "Tokenize deep space supply chains for inter-nation prosperity",
"specCid": "bafybeieeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee",
"resultCid": "bafybeiffffffffffffffffffffffffffffffffffffffffffffffffffff",
"rewardTokens": "188000",
"deadlineHours": 96,
"budgetUsdc": "10000",
"modeledWorkerCostUsdc": "620",
"estimatedReviewMinutes": 15,
"agentEns": "worker03.agent.agi.eth"
}
],
"validators": [
{
"name": "Horizon Arbitration Collective",
"wallet": "horizon",
"ensSubdomain": "validators.horizon",
"mission": "Curate validator proofs for cosmological asset routing",
"validatorEns": "validator01.club.agi.eth"
},
{
"name": "Atlas Integrity Guild",
"wallet": "atlas",
"ensSubdomain": "validators.atlas",
"mission": "Guarantee cross-domain energy balance sheets",
"validatorEns": "validator02.club.agi.eth"
}
],
"treasury": {
"name": "Omega Stewardship Treasury",
"wallet": "omega-treasury",
"ensSubdomain": "treasury",
"mission": "Recycle burns and fees into sovereign dividend schedules"
},
"schemaVersion": 2,
"mode": "synthetic",
"marketAnnualUsd": "40000000000000",
"marketBasis": "Project vision planning assumption; not a verified TAM, revenue forecast or reliability claim",
"businessPolicy": {
"budgetCurrency": "USDC",
"budgetDecimals": 6,
"platformFeeBps": 250,
"reviewCapacityMinutes": 40,
"reviewRateUsdcPerHour": "90",
"maxReviewerMinutesPerJob": 15
},
"referenceStatus": "Original specCid/resultCid values are preserved historical placeholders, not published or verified evidence. Runs produce real content hashes and offline CIDs for their actual files."
}
SHA-256 d02ea69fa85e16c113bb74f3a90393d91675e5792809682a5e6b2a059198f72a
FROM READING TO A REPRODUCIBLE RUN
Try the selected path.
Node.js workspaceRun from the repository root after nvm install, nvm use and npm ci. Use the versions pinned in .nvmrc and package.json. Commands below describe the selected path; optional app/server packages can have their own locked dependencies.
Complete environment setup ↗npm run demo:omega-business-3What you should observe
The local orchestrator produces scenario evidence and prints its output paths. Inspect generated reports before launching the optional UI.
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.
Pick a budget or control from the configuration and trace it into the report. Identify whether it is checked, calculated or merely described.
THE SYSTEM, MADE VISIBLE
Architecture & relationships
View original Mermaid source
flowchart TD
Brief["Work brief and exact source bytes"] --> Budget["Budget and review capacity"]
Budget -->|Admit| Task["Reviewed task and allowed environment"]
Budget -->|Defer| Queue["Revise scope or reserve capacity"]
Task --> Fixture["Deterministic local rehearsal"]
Task --> Worker["Commissioned computer-use worker"]
Fixture --> Files["Candidate and evidence files"]
Worker --> Files
Worker -->|Unknown outcome| Recovery["Stop and reconcile effects"]
Files --> Check["Independent task-specific checks"]
Check -->|Pass| Human["Human acceptance review"]
Check -->|Fail| Correction["Retain evidence and correct"]
Human -->|Authorized| Signer["Separate settlement signer"]WHEN SOMETHING DOESN’T MATCH
Troubleshooting
A command or service fails
Start at the first error, confirm the working directory and pinned toolchain, then follow the linked component guide. Optional packages and provider services have separate prerequisites.
A report looks successful but lacks evidence
Check its source revision, configuration, timestamps and underlying events. Historical fixtures and generated plans do not prove a fresh execution.
TRACE THE CHECKS
Verification & next steps
4 tracked test source files are available in this directory. Inspect the tests and their environment before choosing a suite; file counts do not establish test results.
Browse the test sources
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.
npm run demo:omega-business-3npm run demo:omega-business-3:ui