Job settlement

Atlas Conductor

Orchestrate four connected energy, food, health and macroeconomic scenarios.

A CLOSER LOOK

How do several missions share one verifiable execution pipeline?

For mission designers: follow the energy, food, health and economic coordination scenarios from their individual requirements into local contract execution.

Read the mission

Expand jobs to inspect each objective, specification path, deadline, reward and result URI. The sector objectives describe synthetic scenarios, not completed real-world projects.

demo/atlas-conductor/config/mission@v2.json ↗

Inspect the local driver

The launcher prepares the disposable local chain and calls the shared AURORA workflow. Follow the referenced specification for each job; committee sizes may differ between jobs.

demo/atlas-conductor/bin/atlas-conductor-local.sh ↗

Understand the wider plan

Compare the project plan with the executable mission. Planning dependencies and ambitious targets are context; transaction receipts establish which local jobs actually ran.

demo/atlas-conductor/project-plan.json ↗

REAL REPOSITORY MATERIAL

Inspect. Understand. Reproduce.

Reading the exact source at revision 5b4cebb3.
This browser inspection does not execute the demo.

demo/atlas-conductor/config/mission@v2.json

Select a walkthrough step to explore its source.

Full source text
{
  "version": "v2",
  "scope": "atlas-conductor",
  "description": "Tri-sector convergence mission that executes energy, food, health, and macro-economic coordination in a single deterministic pass.",
  "jobs": [
    {
      "name": "Planetary Energy Equilibrium",
      "specPath": "demo/atlas-conductor/config/spec-energy@v2.json",
      "resultURI": "ipfs://atlas-conductor/energy/result",
      "agentSubdomain": "energy.maestro",
      "reward": "18750000",
      "workerStake": "52000000",
      "validatorStake": "94000000",
      "deadlineOffsetSec": 18000,
      "metadata": {
        "objective": "Stabilise renewable baseload across five continental pools",
        "priority": "critical",
        "kpi": "< 3% demand variance"
      },
      "notes": "Runs ASI take-off dry-run harness for multi-region energy dispatch and validator settlement."
    },
    {
      "name": "Sovereign Food Resilience",
      "specPath": "demo/atlas-conductor/config/spec-food@v2.json",
      "resultURI": "ipfs://atlas-conductor/food/result",
      "agentSubdomain": "food.arcology",
      "reward": "16200000",
      "workerStake": "41000000",
      "validatorStake": "88000000",
      "deadlineOffsetSec": 14400,
      "metadata": {
        "objective": "Synchronise regenerative agriculture, logistics, and validator QA",
        "priority": "high",
        "kpi": "< 2h delivery latency"
      },
      "notes": "Coordinates north/south contractor cooperatives and civic validators across the ASI stack."
    },
    {
      "name": "Open Health Intelligence",
      "specPath": "demo/atlas-conductor/config/spec-health@v2.json",
      "resultURI": "ipfs://atlas-conductor/health/result",
      "agentSubdomain": "health.synapse",
      "reward": "13900000",
      "workerStake": "36000000",
      "validatorStake": "82000000",
      "deadlineOffsetSec": 10800,
      "metadata": {
        "objective": "Deploy telemedicine, epidemiology, and validator-led audits",
        "priority": "high",
        "kpi": "95% SLA compliance"
      },
      "notes": "Exercises validator quorum for data integrity while thermodynamics adjusts clinical throughput."
    },
    {
      "name": "Macro-Economic Orchestration",
      "specPath": "demo/atlas-conductor/config/spec-economic@v2.json",
      "resultURI": "ipfs://atlas-conductor/economics/result",
      "agentSubdomain": "economy.chamber",
      "reward": "20500000",
      "workerStake": "61000000",
      "validatorStake": "99000000",
      "deadlineOffsetSec": 21600,
      "metadata": {
        "objective": "Execute labour thermostat updates, Hamiltonian monitoring, and treasury balancing",
        "priority": "critical",
        "kpi": "capital velocity within ±5%"
      },
      "notes": "Calls owner Atlas, Mission Control, and Hamiltonian tracker to align treasury actions with validator energy."
    }
  ]
}

SHA-256 298d16ee7475bde49c70a46b943f9364165f5b307f8ebf352eb384c63b3025c7

FROM READING TO A REPRODUCIBLE RUN

Try the selected path.

Disposable local chain

From 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 ↗
SELECTED EXECUTION PATH
npm run demo:atlas-conductor:local

What you should observe

Inspect reports/localhost/atlas-conductor/. Match every mission job to its own completed validation and settlement evidence; do not infer completion from the aggregate narrative.

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.

Compare two job specifications and identify differences in required approvals, validator count and deadline. Re-run with a separate report directory or preserve the first run before comparing.

THE SYSTEM, MADE VISIBLE

Architecture & relationships

Architecture diagram · source preserved below
View original Mermaid source
flowchart LR
    Operators((Mission Owners)) --> demo_atlas_conductor[[Demo → Atlas Conductor]]
    demo_atlas_conductor --> 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.

npm run demo:atlas-conductor:local

Full command catalog and troubleshooting ↗

ORIGINAL DIRECTORYdemo/atlas-conductorView on GitHub ↗