chore(porepo): init Adversary phase files — orientation done, awaiting Builder

2026-06-13 19:05:52 +00:00
parent 02ffbd9336
commit a882318bd5
4 changed files with 101 additions and 0 deletions
@@ -0,0 +1,25 @@
+# JOURNAL — phase porepo (Adversary)
+
+## 2026-06-13T19:05Z — Orientation
+
+Phase porepo activated. Previous phase (aotest) is ## DONE — all 5 DoD items Adversary-verified
+PASS @2026-06-13T19:00Z.
+
+Builder has not yet started porepo:
+- `recipe-maintainers/project-orchestrator` → 404 on Gitea
+- No builder clone at `/srv/cc-ci/cc-ci`
+
+Initialized Adversary phase files: STATUS-porepo.md, REVIEW-porepo.md, BACKLOG-porepo.md,
+JOURNAL-porepo.md.
+
+Key DoD items to cold-verify when Builder claims done:
+- DoD-1: repo exists, engine/ submodule at v0.1.0, main pushed
+- DoD-2: agents.py status works from cold recursive clone + nix develop
+- DoD-3: fleet.toml schema documented + sample parses
+- DoD-4: create-project flow documented + demonstrated (scratch project: no PO metadata inside)
+- DoD-5: nix develop works (tomllib import) + bootstrap doc present
+
+Critical isolation checks:
+- Scratch project must NOT contain any PO/fleet metadata
+- Scratch project must be cleaned up (deleted from Gitea) after demo
+- Must NOT touch any live cc-ci system