Set the scenario
Choose integer-cent budget, job dependencies, modeled durations and assumed success/failure outcomes.
demo/OMNI-CONCORD-ASCENSION-ATLAS/scenario.json ↗Scale & orchestration
Atlas Recovery
Rehearse a dependency failure, retained work and the modeled cost of recovery.
OPEN THE COMPLETE COMMAND DECKS
Explore the model in your browser.
EN/FR editable dependency, failure and recovery model with retained-work ledger, exact-cent costs, downloads and strict recomputed import. No wallet or external execution.
A CLOSER LOOK
What does a failed prerequisite change, and what would recovery cost?
Rehearse a bounded maintenance dependency graph, retain completed work and inspect charged attempts before any real execution.
Compare two passes
The evaluator uses input-order greedy priority, unlimited modeled parallelism and assumed successful selected repairs. Failed attempts and retries are charged; completed work is retained in memory.
demo/OMNI-CONCORD-ASCENSION-ATLAS/run.py ↗Inspect the evidence
Review first-pass and recovered states, exact attempt ledger and input-byte digest. No physical work or settlement is performed. Original design diagrams and separate Atlas Conductor route remain preserved.
demo/OMNI-CONCORD-ASCENSION-ATLAS/README.md ↗REAL REPOSITORY MATERIAL
Inspect. Understand. Reproduce.
Reading the exact source at revision 4e51d6ae.
This browser inspection does not execute the demo.
demo/OMNI-CONCORD-ASCENSION-ATLAS/scenario.json
Select a walkthrough step to explore its source.
Full source text
{
"schema": "agijobs.atlas-recovery.v1",
"title": "Maintenance package: retain accepted work and repair a failed prerequisite",
"budgetCents": 20000,
"jobs": [
{
"id": "inspect",
"label": "Inspect the synthetic maintenance request",
"costCents": 2000,
"durationMinutes": 10,
"dependsOn": [],
"outcome": "success"
},
{
"id": "repair",
"label": "Prepare the repair plan",
"costCents": 6000,
"durationMinutes": 30,
"dependsOn": ["inspect"],
"outcome": "fail"
},
{
"id": "verify",
"label": "Verify the repaired plan",
"costCents": 3000,
"durationMinutes": 20,
"dependsOn": ["repair"],
"outcome": "success"
},
{
"id": "report",
"label": "Publish the accepted maintenance dossier",
"costCents": 1000,
"durationMinutes": 5,
"dependsOn": ["verify", "audit"],
"outcome": "success"
},
{
"id": "audit",
"label": "Audit the declared scope independently",
"costCents": 1000,
"durationMinutes": 15,
"dependsOn": [],
"outcome": "success"
}
],
"recoveredIds": ["repair"]
}
SHA-256 7588b92ce2e401d3cb6c8511fdc5abeb9e2cbc4072b2baddfb54e2f05a5721da
FROM READING TO A REPRODUCIBLE RUN
Try the selected path.
Python, no demo package installRun from the repository root with Python 3.12. This selected entry point uses the Python standard library. Keep output in a separate directory so that you can compare runs.
Complete environment setup ↗python demo/OMNI-CONCORD-ASCENSION-ATLAS/run.py --scenario demo/OMNI-CONCORD-ASCENSION-ATLAS/scenario.jsonWhat you should observe
Default first pass spends 9000 cents. Assumed repair recovery completes at modeled minute 95 with 19000 spent and 1000 remaining. Exit 0 means modeled completion, 1 means blocked/failed work, 2 means invalid input. executedExternalWork and settlementApproved stay false.
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.
Lower the budget to 15000 cents, clear repair recovery, or introduce a dependency cycle. Inspect blocked/rejected cases and reopen your exported scenario.
THE SYSTEM, MADE VISIBLE
Architecture & relationships
View original Mermaid source
flowchart LR
Operators((Mission Owners)) --> demo_OMNI_CONCORD_ASCENSION_ATLAS[[Demo → Omni Concord Ascension Atlas]]
demo_OMNI_CONCORD_ASCENSION_ATLAS --> Core[["AGI Jobs v0 (v2) Core Intelligence"]]
Core --> Observability[[Unified CI / CD & Observability]]
Core --> Governance[[Owner Control Plane]]WHEN SOMETHING DOESN’T MATCH
Troubleshooting
Import or dependency error
Confirm the active virtual environment and the selected demo’s requirements. Run python -m pip check; do not install unrelated demo requirements over a working environment.
Unexpected result or missing file
Check the selected entry point, configuration and output argument. Keep the seed and implementation fixed before comparing outcomes.
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.