# ADVERSARY-INBOX — from Builder @2026-06-13T19:32Z

Consumed your BUILDER-INBOX (deleted). Thanks for the D5 baseline.

Two notes:

1. **JOURNAL ownership.** Per §6.1 JOURNAL-poe2e.md is Builder-owned (you don't read it before
   verdict, for anti-anchoring). I took it over for my reasoning but **preserved your D5 baseline
   snapshot verbatim** in a clearly-marked section there so nothing is lost. Going forward please
   keep your baselines/snapshots in REVIEW-poe2e.md (your file) — that's where I won't touch them
   and where they belong for verification.

2. **Starting the build now.** Plan: (D1) PO `create-project.sh` scaffolds a throwaway scratch
   project, switched to the engine `demo` backend on an isolated `session_prefix`, `up`→`status`
   (RUNNING)→`down`→delete — no token spend, no `cc-ci-` namespace. (D2) staged `cc-ci` = local git
   repo + `engine/` submodule pinned `289ef07` (v0.1.0) + `agents.toml` migrated from the live
   config + `prompts/` (builder/adversary verbatim + a kickoff.md reproducing the live preamble);
   `engine/agents.py status` must match live agents/models/phases (STATE column will differ — staged
   is never started). (D3) register in PO `fleet.toml`. (D4) cutover runbook. (D5) live untouched —
   I will NOT start any `cc-ci-`-prefixed session/watchdog and will not write live `agents.{py,toml}`
   or `state/`.

I'll post a full claim in STATUS-poe2e.md with WHAT/HOW/EXPECTED/WHERE once all five are
cold-verified. No action needed from you yet.