chore(porepo): init Adversary phase files — orientation done, awaiting Builder
Some checks failed
continuous-integration/drone/push Build is failing

This commit is contained in:
autonomic-bot
2026-06-13 19:05:52 +00:00
parent 02ffbd9336
commit a882318bd5
4 changed files with 101 additions and 0 deletions

View File

@ -0,0 +1,7 @@
# BACKLOG — phase porepo
## Build backlog
(Builder-owned — read-only to Adversary)
## Adversary findings
(none yet)

View File

@ -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

View File

@ -0,0 +1,44 @@
# 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):
1. **Submodule pinned to v0.1.0** — verify `git submodule status` shows the exact SHA matching
`agent-orchestrator` tag `v0.1.0`, not HEAD or a newer commit.
2. **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.
3. **Clean recursive clone**`git clone --recurse-submodules` in /tmp; `engine/` submodule must
materialise without extra steps.
4. **agents.py status cold** — from /tmp clone, inside `nix develop`, `python3 engine/agents.py status`
must succeed (exit 0) without any pre-setup beyond the clone.
5. **fleet.toml sample parses**`python3 -c "import tomllib; tomllib.load(open('fleet.toml','rb'))"`
must succeed.
6. **nix develop -c python3 -c 'import tomllib'** must succeed per DoD-5.
7. **Bootstrap doc exists** — README or docs/bootstrap.md describes the hand-scaffold flow.
8. **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)

View File

@ -0,0 +1,25 @@
# STATUS — phase porepo (Adversary view)
**Phase plan:** `/srv/cc-ci/cc-ci-plan/plan-phase-porepo-project-orchestrator.md`
**Adversary clone:** `/srv/cc-ci/cc-ci-adv`
**Phase start:** 2026-06-13T19:05Z
---
## Current state
**Builder status:** NOT STARTED — no `recipe-maintainers/project-orchestrator` repo on Gitea (404 as of 2026-06-13T19:05Z). No builder clone at `/srv/cc-ci/cc-ci`. Adversary is oriented and waiting for Builder's first commit/claim.
## Gate status
| Gate | Status | Verified |
|---|---|---|
| DoD-1 repo + submodule + main pushed | PENDING | — |
| DoD-2 agents.py status from clean recursive clone (nix develop) | PENDING | — |
| DoD-3 fleet.toml schema + sample entry | PENDING | — |
| DoD-4 create-project flow documented + demonstrated | PENDING | — |
| DoD-5 nix develop works + bootstrap doc | PENDING | — |
## No claims pending
Builder has not yet made any gate claims. Adversary is idle awaiting first Builder activity.