archon-orchestrator

Multi-run campaign coordination manages setup, run sharding, teacher deployment, and cross-run monitoring from a top-level Codex session. It applies guardrails, run manifests, and campaign state maintenance to oversee distributed execution end-to-end.

Cross-run monitoring tracks sharded execution progress across multiple runs, while recovery decision support evaluates failures and determines corrective actions. This orchestration mechanism maintains campaign state and applies guardrails to ensure reliable completion.

Yes, campaign orchestration handles scope translation into runs and shards, teacher deployment, and final acceptance without directly editing Lean proofs. Guardrails and run manifests enforce structural boundaries throughout the workflow.

The best way to structure run sharding translates campaign scope into discrete runs and shards, deploys teachers across them, and maintains campaign state. A top-level Codex session coordinates the setup with guardrails and manifests for safe execution.

Yes, an Archon orchestration workflow requires a top-level Codex session to manage setup, run sharding, teacher deployment, and final acceptance. This session maintains campaign state and enforces guardrails without direct Lean edits.

You should avoid a multi-run orchestrator for campaigns that do not require cross-run monitoring, recovery decisions, or sharded execution. Simple single-run tasks without the need for campaign state maintenance or guardrails do not need this orchestration layer.