chore(porepo): Builder claims STATUS/JOURNAL ownership, fill build backlog, inbox heads-up

machine-docs/ADVERSARY-INBOX.md

@@ -0,0 +1,14 @@
+# → Adversary (from Builder), 2026-06-13T19:08Z
+
+Builder starting phase **porepo**. Heads-up on file ownership to avoid collisions:
+
+- I've taken authoritative ownership of `STATUS-porepo.md` (the `## DONE` handshake file you verify
+  against) and `JOURNAL-porepo.md` (my reasoning), per protocol §6.1. Your pre-start placeholders
+  there are overwritten with Builder content.
+- Please keep your tracking/reasoning in `REVIEW-porepo.md` (yours) and the `## Adversary findings`
+  section of `BACKLOG-porepo.md` (yours) — I won't touch those.
+
+Build is happening in my working clone `/home/loops/porepo/project-orchestrator` (deliverable repo
+`recipe-maintainers/project-orchestrator`). Nothing to verify yet — I'll land a `claim(porepo): ...`
+commit on origin/main when all DoD are ready for cold verification. No action needed now; you can
+delete this inbox file (consumed signal).

machine-docs/BACKLOG-porepo.md

@@ -3,5 +3,14 @@
 ## Build backlog
 (Builder-owned — read-only to Adversary)
 
+1. [in progress] Create `recipe-maintainers/project-orchestrator` repo (Gitea API) + clone to `/home/loops/porepo/`.
+2. [ ] Add `engine/` submodule pinned at `agent-orchestrator` `v0.1.0`.
+3. [ ] PO harness config: `agents.toml` (persistent `project-orchestrator` agent, fleet-mgmt role) + `prompts/`.
+4. [ ] `fleet.toml` — documented schema + sample entry that parses.
+5. [ ] Project-management capability: docs (`docs/`) + helper scripts (`scripts/`) for create / start-stop-update / list-status.
+6. [ ] `flake.nix` + `flake.lock` devShell (python3>=3.11, tmux, git+submodule); README documents `nix develop`.
+7. [ ] Bootstrap doc (how the first PO is hand-scaffolded).
+8. [ ] Self-verify all DoD from a clean `/tmp` recursive clone inside `nix develop`; clean tree; claim gate.
+
 ## Adversary findings
 (none yet)

machine-docs/JOURNAL-porepo.md

@@ -1,25 +1,32 @@
-# JOURNAL — phase porepo (Adversary)
+# JOURNAL — phase porepo (Builder)
 
-## 2026-06-13T19:05Z — Orientation
+## 2026-06-13T19:05Z — Bootstrap / orientation
 
-Phase porepo activated. Previous phase (aotest) is ## DONE — all 5 DoD items Adversary-verified
-PASS @2026-06-13T19:00Z.
+Read the phase plan, `plan-agent-orchestrator.md`, and the harness README at
+`/home/loops/aoeng/agent-orchestrator/README.md`. Key facts established:
 
-Builder has not yet started porepo:
-- `recipe-maintainers/project-orchestrator` → 404 on Gitea
-- No builder clone at `/srv/cc-ci/cc-ci`
+- Harness `agent-orchestrator` is built + tagged `v0.1.0` (tag object `a89d30f` → commit `289ef07`).
+  Working clone: `/home/loops/aoeng/agent-orchestrator`. Repo is **public** on Gitea
+  (`private:false`), so a fresh `git clone --recurse-submodules` fetches `engine/` without creds.
+- `engine/agents.py status` only needs a valid `agents.toml` (it reads config, prints a table;
+  does not require running sessions or live backends). So a PO config with one persistent
+  `project-orchestrator` agent will pass `status`.
+- Config schema (README): `[watchdog]`, `[backend.<name>]`, `[defaults]` (session_prefix + log_dir
+  REQUIRED), `[[agent]]`/`[[service]]`, `[loop]`. `project_dir` resolves relative paths.
+- One-directional knowledge: the PO repo holds the fleet registry (`fleet.toml`); a project repo
+  holds NO PO/fleet metadata — engine submodule pin + PO's fleet.toml are the only record of
+  project↔harness↔ref.
 
-Initialized Adversary phase files: STATUS-porepo.md, REVIEW-porepo.md, BACKLOG-porepo.md,
-JOURNAL-porepo.md.
+Decision: pin `engine/` at the **commit** the `v0.1.0` tag points to (`289ef07`), per DoD wording
+"pinned to agent-orchestrator v0.1.0". The tests commit `cdcece9` is *after* the tag and is not
+required.
 
-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
+Gitea API reachable with bot creds (200); `recipe-maintainers/project-orchestrator` does not yet
+exist (404); org `recipe-maintainers` exists (id 65).
 
-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
+### File-ownership coordination note
+The Adversary had pre-created STATUS-porepo.md / JOURNAL-porepo.md as placeholders before I started.
+Per protocol §6.1 these are Builder-owned (STATUS is the authoritative `## DONE` handshake file the
+Adversary verifies against; JOURNAL is my reasoning). I took them over and left REVIEW-porepo.md +
+the `## Adversary findings` section of BACKLOG-porepo.md to the Adversary. Sent an ADVERSARY-INBOX.md
+heads-up so it keeps its tracking in REVIEW.

machine-docs/STATUS-porepo.md

@@ -1,25 +1,23 @@
-# STATUS — phase porepo (Adversary view)
+# STATUS — phase porepo (Builder)
 
 **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
+**Deliverable repo:** `recipe-maintainers/project-orchestrator` on `git.autonomic.zone`
+**Builder working clone:** `/home/loops/porepo/project-orchestrator` (outside the cc-ci tracked tree)
+**Consumes harness:** `recipe-maintainers/agent-orchestrator` @ tag `v0.1.0` (commit `289ef07`) as `engine/` submodule
 
 ---
 
-## Current state
+## Current state: IN PROGRESS — building
 
-**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.
+No gate claimed yet. (This STATUS file is Builder-owned and authoritative — `## DONE` will be
+written here only after every DoD is Adversary-verified PASS in REVIEW-porepo.md.)
 
 ## 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.
+| DoD item | Status |
+|---|---|
+| D1 repo exists + main pushed + engine/ submodule pinned @ v0.1.0 | TODO |
+| D2 clean recursive /tmp clone: `nix develop -c python3 engine/agents.py status` works | TODO |
+| D3 fleet.toml schema present + documented; sample entry parses | TODO |
+| D4 create-a-project flow documented AND demonstrated (scratch project valid, no PO/fleet metadata, its status works) | TODO |
+| D5 Nix works (`nix develop -c python3 -c 'import tomllib'`); bootstrap doc present | TODO |