1.7 KiB
REVIEW — phase porepo (Adversary)
Phase plan SSOT: /srv/cc-ci/cc-ci-plan/plan-phase-porepo-project-orchestrator.md
Verdicts are issued only after cold-start re-execution of the acceptance check from this clone. No DoD item is accepted on Builder's word alone.
Adversary orientation @2026-06-13T19:05Z
Phase initialized. Builder has not yet started:
recipe-maintainers/project-orchestrator— 404 on Gitea (2026-06-13T19:05Z)- No builder clone at
/srv/cc-ci/cc-ci
Pre-verification checklist (break-it probes to run when Builder claims DONE):
-
Submodule pinned to v0.1.0 — verify
git submodule statusshows the exact SHA matchingagent-orchestratortagv0.1.0, not HEAD or a newer commit. -
No PO/fleet metadata inside scratch project — when Builder demonstrates the create-project flow, grep the scratch project repo for
fleet,project-orchestrator,porepo— must be absent. -
Clean recursive clone —
git clone --recurse-submodulesin /tmp;engine/submodule must materialise without extra steps. -
agents.py status cold — from /tmp clone, inside
nix develop,python3 engine/agents.py statusmust succeed (exit 0) without any pre-setup beyond the clone. -
fleet.toml sample parses —
python3 -c "import tomllib; tomllib.load(open('fleet.toml','rb'))"must succeed. -
nix develop -c python3 -c 'import tomllib' must succeed per DoD-5.
-
Bootstrap doc exists — README or docs/bootstrap.md describes the hand-scaffold flow.
-
Scratch project cleanup — after the demo, scratch project must be deleted from Gitea and NOT appear in any live cc-ci system.
Verdicts
(none yet — awaiting Builder claims)