Akamoto fleet overview
The multi-harness agent fleet and the operating rules every coding agent inherits across the estate.
LiveChecked against
akamoto-io/package.json, starlight-agent-config/core/doctrine/SYSTEM-SPINE.md, tools/pr-gate.mjs, TRUTH.mdAkamoto (akamoto.io) represents the multi-harness agent fleet. Every coding agent operating on the estate — Claude Code, Codex, Gemini CLI, Antigravity, Grok, Hermes, and OpenCode — is admitted through the same contract, operates in an isolated write lane, and closes its work through cross-provider verification.
Where the fleet rules live
| Surface | Canonical path | Purpose |
|---|---|---|
| Public site | frankxai/akamoto-io (https://akamoto.io) | Public overview of the multi-agent fleet architecture |
| Doctrine spine | starlight-agent-config/core/doctrine/SYSTEM-SPINE.md | Compiled into CLAUDE.md, AGENTS.md, and GEMINI.md across all harnesses |
| Cross-harness PR gate | starlight/tools/pr-gate.mjs + tools/lib/harness-identity.mjs | Enforces that author harness ≠ reviewer harness on the exact merge SHA |
| Handover ledger | frankxai/agentic-ops-hub (ops/OPS-LEDGER.md) | Tracks active sessions, completed slices, and next prompts |
The four admission & completion gates
- Lane isolation. One writer per branch (
agent/<harness>/<scope>orcodex/<scope>) and worktree (tools/lane.mjs). - Resource & browser discipline. Agents never launch unmonitored local Chromium instances; browser automation routes through the shared CDP multiplexer (
http://localhost:9223) gated by free-RAM preflight checks. - Cross-provider verification (
pr-gate.mjs). No pull request merges unless a second harness from a different provider signs off on the exact head commit SHA. - Ledger closeout. Every completed slice updates
ops/sessions/YYYY-MM-DD.mdand regeneratesops/HANDOVER-INDEX.mdvianode scripts/handover.mjs index.