Skip to content
ARQANT Documentation/Autonomous Coding Missions
DEVELOPERS

Autonomous Coding Missions

Founder mission compilation, branch claiming, model coding, integration and evidence.

One mission, many owned workers

FOUNDER INTENT → CEO/CTO WORKPACKETS → EXCLUSIVE BRANCH CLAIM
→ MODEL PATCH → UNIT/BUILD/ROUTE QA → INDEPENDENT INTEGRATION
→ PR / SAFE MERGE → RAILWAY SHA → HTTP/RENDER READBACK

File and lane ownership

Each Coding Agent must claim its allocated branch before editing. It can change only owned files. Shared routers, databases, global CSS or financial contracts belong to the designated integrator. Workers may operate in parallel, but only one has exclusive ownership of any source file at a time.

What has been demonstrated

Actual GitHub missions have shown multi-worker source changes, tested commits and integration, including a five-worker run. That is software engineering progress, not evidence that AgentOS already runs a global autonomous business economy. Automated recovery, end-to-end Founder OS dispatch and Production deployment must each be observed separately.

Failure labels are actionable

  • MODELS_EMPTY_CONTENT: no valid model patch; retry/repair within scope.
  • CLAIM_CONFLICT: claimed branch or file already owned.
  • GITHUB_403: PR permission denied; preserve tested branch for documented recovery.
  • TEST_FAILED: reject merge until repaired.
  • NEEDS_APPROVAL: GitHub code may be merged but is not yet deployed.
  • VERIFIER_UNAVAILABLE: no independent acceptance receipt yet.

Mission receipt and doctrine

Record policy revision/hash, owner, WorkPacket, commit SHA, test results, integrated SHA and active Railway readback. Every coding-model prompt receives the actual Founder Doctrine and economic business thesis; a file existing in the repo is not enough. See WorkPackets.

© ARQANT · DocumentationPrivacyTermsMain website ↗
ALL PAGES