Repository guide · 0 diagrams

View source on GitHub ↗
Original documentation, preserved from the repository. Historical projections and scenario ambitions are not evidence of live performance. See the current readiness record for deployment requirements.

Mission Plan Autopilot

The Planetary Orchestrator Fabric demo now ships with a declarative mission plan so non-technical owners can launch Kardashev-grade drills without touching CLI switches. A mission plan bundles the fabric configuration, job blueprint, owner command schedule, checkpoint cadence, and reporting overrides into a single JSON dossier.

Quickstart

# Launch the full planetary drill using the bundled dossier
./demo/Planetary-Orchestrator-Fabric-v0/bin/run-demo.sh \
  --plan demo/Planetary-Orchestrator-Fabric-v0/config/mission-plan.example.json

The orchestrator will:

File Structure

config/mission-plan.example.json exposes the following fields:

{
  "metadata": {
    "label": "Kardashev-II Planetary Drill",
    "description": "Human readable summary surfaced in dashboards + chronicles.",
    "author": "Mission Council",
    "version": "1.0.0",
    "tags": ["demo", "mission-plan", "non-technical"]
  },
  "config": "./fabric.example.json",               // path or inline FabricConfig
  "ownerCommands": "./owner-commands.example.json", // path or inline owner schedule
  "jobBlueprint": "./jobs.blueprint.example.json",  // path or inline blueprint
  "reporting": {
    "directory": "../reports/mission-plan",        // optional reporting override
    "defaultLabel": "mission-plan"
  },
  "run": {
    "jobs": 10000,
    "simulateOutage": "mars.gpu-helion",
    "outageTick": 45,
    "outputLabel": "mission-plan",
    "stopAfterTicks": 240,
    "checkpoint": {
      "intervalTicks": 30,
      "path": "../storage/mission-plan-checkpoint.json"
    },
    "preserveReportDirOnResume": true
  }
}

All paths are resolved relative to the mission plan file. Inline objects are accepted if you prefer to embed configuration directly.

Customising Your Plan

  1. Clone the template
    cp demo/Planetary-Orchestrator-Fabric-v0/config/mission-plan.example.json \
       demo/Planetary-Orchestrator-Fabric-v0/config/mission-plan.my-drill.json
  2. Edit metadata so dashboards and chronicles display your mission name, author, and tags.
  3. Swap config/blueprint/owner command paths to point at production-ready assets (e.g. L2 shards, bespoke job mixes, governance-approved command decks).
  4. Tune run.checkpoint to match operational SLAs—tighten intervals during solar storms, retarget storage buckets, or pre-seed checkpoint rotation.
  5. Adjust reporting directory and default label to stream artifacts into the right archival bucket.
  6. Execute:
    ./demo/Planetary-Orchestrator-Fabric-v0/bin/run-demo.sh \
      --plan demo/Planetary-Orchestrator-Fabric-v0/config/mission-plan.my-drill.json

Dashboard & Chronicle Integration

Validation

Safety Considerations

Mission plans transform AGI Jobs v0 (v2) into a button-click experience for planetary operators—declare your objectives once, then let the fabric orchestrate the galaxy.

← Back to Planetary Orchestrator Fabric