recipe-maintainers/cc-ci-orchestrator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: orchestration.md as the root agent map; wake prompt + AGENTS.md point to it

Browse Source 
One root doc maps every agent (Builder, Adversary, Orchestrator, Assistant,
Upgrader) -> its prompt + plan, with the watchdog and git coordination
protocol as the subtlety beneath. Fold the orchestrator supervision routine
into it (remove orchestrator-supervision.md). The hourly wake prompt and
AGENTS.md now just point at orchestration.md.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
autonomic-bot
2026-06-02 01:42:49 +00:00
parent 37a422bc31
commit 35f83a4b74
4 changed files with 71 additions and 50 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
AGENTS.md
View File

@ -5,16 +5,15 @@ server. It holds the plan, the launch/supervision tooling, and the two loop prom
project (NixOS config, test runner, recipe tests) lives in a **separate** repo the loops create at
`git.autonomic.zone/recipe-maintainers/cc-ci` — do not confuse the two.
## Three roles (don't conflate them)
## The agent map lives in `cc-ci-plan/orchestration.md`
1. **Orchestrator** — *this* session/role. Supervises: checks in on the two loops, reads their
logs/STATUS, makes changes to the plan/prompts, restarts loops, and owns the VM-level fallback.
It is **separate** from the loops and is the only role that should power-cycle/recreate the VM.
2. **Builder loop** — builds the CI server (`cc-ci-plan/prompts/builder.md`).
3. **Adversary loop** — independently disbelieves/verifies (`cc-ci-plan/prompts/adversary.md`).
That doc is the **root structure**: every agent (Builder, Adversary, Orchestrator, Assistant,
Upgrader) → its prompt + plan, plus the watchdog and the git coordination protocol. Read it first.
The two loops coordinate **only** through the cc-ci git repo (see `plan.md` §6.1). The orchestrator
watches from outside.
In short: the **Orchestrator** (*this* session/role) supervises and keeps everyone on track — it is
**separate** from the loops and is the only role that should power-cycle/recreate the host. The
**Builder** and **Adversary** loops coordinate **only** through the cc-ci git repo (`plan.md` §6.1);
the orchestrator watches from outside.
## On startup: read the journal, announce yourself, report reboots