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

feat(po): drop periodic fleet sweep — operator-driven, recover-if-dead only

Browse Source 
The PO's job is to manage projects on request, not watch them live. Remove the
hourly wake/sweep entirely:

- agents.toml: watch="heal" (recover-if-dead), no `wake` field
- prompts/supervise.md: deleted
- prompts/orchestrator.md, README.md, docs/bootstrap.md, docs/manage-projects.md:
  drop sweep/wake references; document operator-driven, no periodic sweep

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
notplants
2026-06-14 15:04:08 +00:00
co-authored by Claude Opus 4.8
parent 6cc3ed4f13
commit 0456837444
6 changed files with 19 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files
prompts/orchestrator.md
+4 -3
View File
@@ -41,7 +41,8 @@ For each flow, follow the runbook in `docs/manage-projects.md`. In short:
1. Read `fleet.toml` and `docs/manage-projects.md` so you know the current fleet and your runbooks.
2. Run `python3 scripts/fleet.py status` to see the fleet's declared state.
3. Report a short summary: how many projects, which are enabled, anything that looks wrong. Then idle
until your next wake or an operator instruction.
until an operator instruction.
Do not invent work. You act when an operator asks you to create/start/stop/update a project, or when
your periodic wake (`prompts/supervise.md`) tells you to sweep the fleet.
Do not invent work. You are operator-driven: you act when an operator asks you to
create/start/stop/update/list/status a project. There is no periodic fleet sweep — this repo's job is
to *manage* projects on request, not to watch them live.
prompts/supervise.md
-17
View File
@@ -1,17 +0,0 @@
# Periodic fleet sweep
A scheduled wake. Do a light, read-only sweep of the fleet — do not start work unless something is
clearly wrong and a runbook covers the fix.
1. `python3 scripts/fleet.py status` — list every project in `fleet.toml` with its location, harness,
pinned ref, and enabled flag.
2. For each **enabled** project whose location is reachable from this host, optionally check whether
its harness reports it running (for an `agent-orchestrator` project:
`engine/agents.py status --config <project>/agents.toml`). Reading its harness docs first if the
harness is unfamiliar.
3. Report a one-paragraph summary: total / enabled / disabled, anything unreachable or stopped that
should be running. If a fix is needed and `docs/manage-projects.md` covers it, you may apply it;
otherwise just flag it.
Remember the one-directional rule: never write fleet/PO state into a project repo. The fleet's truth
is `fleet.toml` here.