history: Otto-93 tick-close — multi-Claude peer-harness experiment design (reshaped per Aaron don't-be-bottleneck)

docs/BACKLOG.md

@@ -2622,8 +2622,11 @@ within each priority tier.
 
   **Scope limits of the refinement:**
 
-  - Does NOT commit Otto to cede control. Otto remains primary while Aaron is in Claude Code (which is now). Async-mode Codex work only starts when Aaron is in Codex; Otto doesn't dispatch Codex work unilaterally.
-  - Does NOT authorise Codex session to edit `.claude/skills/` or any Otto-owned substrate. Symmetric: Otto should not edit Codex's own-harness substrate.
+  - Does NOT commit Otto to cede control. Otto remains primary while Aaron is in Claude Code (which is now). **Otto DOES dispatch Codex async work** — the primary coordinates; Aaron-harness-context determines which agent is primary at any given moment. Aaron Otto-79 correction: *"you do dispatch codex work, i will just switch whenver i feel like it once it's ready, i'll just go back and fourth from time to time probably when new models come out, you guys need to know when one is primary based on the harness im in and just do the right things so it's not an issue when you launch in tandem/async with you."*
+  - **Tandem / simultaneous launch is out-of-scope today; explicit Aaron opt-in required for a future test.** Aaron Otto-79: *"I won't launch both of you at the same unless i say, this is a future test to see if you can run indenpendenty without interference, but for now one of your will be the corrdinator at a time based on the harness i'm in."*
+  - **Progression model — stepping stones to peer-harness.** Aaron Otto-79 (confirming the direction): *"yeah i think we are building to this which is subtly different from a peer-harness model. this mean i launch you both at the same time right? that's peer harness. we will get there slowly with experiments where one is in controll."* The CURRENT model (one coordinator at a time, based on Aaron's harness-context) is a **stepping stone** toward a future **peer-harness** model where Otto + Codex-loop-agent both run simultaneously + independently. Stages in that progression (each an explicit Aaron opt-in): (a) today = single coordinator, primary-by-context; (b) bounded experiment = short parallel sessions with Aaron observing for interference; (c) peer-harness = both running concurrently with handoff discipline, Aaron can walk away. We aim at (c); we don't assume (c).
+  - **Each harness owns its own named loop agent — start from there.** Aaron Otto-79: *"yeah i guess in peer mode each harness will need it's own 'Otto' might as well start it out like that so code designs it's own named loop agent, you got the good name claude otto :)"* So: **Otto** is the Claude Code loop agent (Aaron-affirmed as *"the good name"*). The **Codex CLI** session picks its own loop-agent persona name — not inherited from Otto, not pre-assigned by Otto. Consistent with the existing persona-naming pattern (Kenji / Amara / Iris / etc. — names chosen in conversation with Aaron, not imposed). The Codex session's first Stage-1b research doc is an appropriate place for the Codex loop agent to name itself. Composes with named-agent-email-ownership (Otto-76) — each loop agent owns its own reputation + eventually its own email.
+  - Does NOT authorise Codex session to **edit** `.claude/skills/` or any Otto-owned substrate. Symmetric: Otto does not **edit** Codex's own-harness substrate. **BUT** — cross-harness **review** and **question-asking** are explicitly encouraged. Aaron Otto-79: *"yall should review each other and ask questions to better understand eachs others harness form the inside to improve our cross harness support."* The distinction is edit-not vs read-and-comment-yes — same shape as peer code review between humans: reviewer reads, comments, asks; author owns the edit.
   - Does NOT require harness-swap for Otto. The arc supports either-primary-any-time, not forced migration.
   - Does NOT bypass the harness-choice ADR (Stage 5) — that's still the decision surface when asymmetries warrant a reset.