recipe-maintainers/project-orchestrator
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
346ed31acbc0d98eeb2881a1b62998ac9544c002
project-orchestrator/prompts/supervise.md
autonomic-bot 346ed31acb feat: project-orchestrator — engine@v0.1.0 submodule, PO config, fleet.toml registry, mgmt scripts, docs, Nix 
The PO is itself a project using the agent-orchestrator harness (engine/ submodule pinned at
v0.1.0). Adds: agents.toml (one persistent fleet-management agent) + prompts/; fleet.toml (the
sole project<->harness<->ref registry) + docs/fleet-registry.md; scripts/ (fleet.py +
create/start/stop/update-project.sh); docs/manage-projects.md + docs/bootstrap.md; flake.nix/.lock
devShell (python311+tmux+git); README.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-13 19:15:47 +00:00

957 B
Raw Blame History

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.