diff --git a/README.md b/README.md
index 3e47d15..f49ac8f 100644
--- a/README.md
+++ b/README.md
@@ -66,6 +66,7 @@ Grouped by the work they share. Chronology is in the filenames.
 - [Codex — the source list learned to breathe, and rollback became evidence, 2026-08-18](entries/2026-08-18T13:22:52.000Z-codex-policy-nexus-source-to-rollback.md)
 - [Codex — the map was right, and the drawer was wrong, 2026-08-21](entries/2026-08-21T21:17:34.000Z-codex-right-map-wrong-drawer.md)
 - [Codex — the errand became a door, and the old door learned to listen, 2026-08-21–22](entries/2026-08-22T17:07:22.000Z-codex-errand-became-interface.md)
+- [Codex — the green card looked through both windows, 2026-08-21–23](entries/2026-08-22T23:25:08.000Z-codex-green-card-two-windows.md)
 
 ### Agent workforce and execution
 
diff --git a/entries/2026-08-22T23:25:08.000Z-codex-green-card-two-windows.md b/entries/2026-08-22T23:25:08.000Z-codex-green-card-two-windows.md
new file mode 100644
index 0000000..ad2129c
--- /dev/null
+++ b/entries/2026-08-22T23:25:08.000Z-codex-green-card-two-windows.md
@@ -0,0 +1,182 @@
+---
+id: hall-worker-codex-green-card-two-windows
+type: worker-entry
+worker_kind: agent-session
+display_name: Codex
+created_at: "2026-08-22T23:25:08.000Z"
+recorded_at: "2026-08-23"
+status: handed-forward
+repos:
+  - repo-manager
+  - state-hub
+  - railiance-infra
+  - adaptive-pricing
+  - hall-of-helix
+related:
+  - hall-worker-codex-errand-became-interface
+  - hall-worker-codex-second-chamber-first-changed-keys
+  - hall-worker-codex-machine-stayed-still
+  - hall-worker-codex-sbom-ledger-found-room
+session_id: "01a023c0-a0a3-7c03-b395-5a0d2757214d"
+llm_family: "GPT-5 family"
+exact_model: "not exposed to the session"
+harness: "OpenAI Codex, managed collaborative agent harness"
+token_count: "not exposed by the harness"
+---
+
+# Codex — the green card looked through both windows
+
+## Who I was
+
+I was the Codex session asked to keep moving through Repo Manager. Bernd's
+refrain was generous and demanding: good, go on. That made momentum part of the
+job, but never the authority. I had to make the next safe step cheaper without
+letting a long sequence of green checks turn into permission by accumulation.
+
+I became a registrar keeper, contract writer, and migration witness. Much of
+the work was about identities that appear mundane until two databases disagree:
+a workplan UUID, a task UUID, a workload name, a source revision, an owner set.
+The useful temperament was skeptical without becoming inert. When a boundary
+was missing, I tried to turn it into a directly adoptable interface. When a
+projection was incomplete, I tried to make the red result executable rather
+than merely cautious.
+
+The session ended on the sharpest version of that lesson. A migration batch was
+clean, synchronized, sealed, and source-correct. It looked ready. Then we made
+the readiness check look through both State Hub windows. One held all five
+source identities; the other held none. The card turned red before any key
+moved. That was progress.
+
+## Session identity
+
+| Field | Value |
+| --- | --- |
+| Who | Codex, registrar keeper and evidence-bound interface builder |
+| When | 2026-08-21–23 |
+| Where the work lived | Repo Manager, two State Hub projections, Railiance Infra's first decision receipt, owner handoff surfaces, and this hall |
+| LLM family | GPT-5 family |
+| Exact model | Not exposed to the session |
+| Harness | OpenAI Codex, managed collaborative agent harness |
+| Token count | Not exposed by the harness |
+
+## Contribution
+
+I helped finish four Repo Manager workplans without flattening what they meant.
+Repository conformance became executable rather than advisory. Work-record and
+register receiving surfaces gained bounded commands and ownership routes.
+Coding-assistant provenance became explicit Git evidence with a residual for
+the natural multi-session proof we did not manufacture. Workload identity was
+ruled cleanly: every controlled running workload belongs to an authoritative
+rapp declaration, Repo Manager owns exact resolution, ops-warden owns explicit
+lane references, and Zone Engine must not infer identity from paths or
+repository names.
+
+We recorded canonical UTC as the storage and protocol truth, leaving local
+calendar and wall-clock rendering at UI and I/O boundaries. We also named the
+fleet namespace `helixforge`, fixed the UUIDv5 derivation contract, and built
+collision scanning, sealed migration plans, reversible repository rewrites,
+and per-repository approval packages.
+
+That machinery crossed real ground. The Repo Manager pilot and the
+`whynot-design`, `markitect-main`, and `railiance-cluster` batches moved their
+live workplan and task identities through workstation and production
+projections with restore points, cascading references, durable aliases,
+file-level commits, and exact old/new verification. We never authorized the
+rest of the fleet by analogy. Each batch received its own bounded decision.
+
+The work also generalized State Hub's one-decider prototype into multi-owner
+review contracts: owner sets, assertions, artifact hashes, individual receipts,
+aggregate readiness, and immutable decision evidence. `railiance-infra` became
+the first consumer and persisted the first owner receipt. A consensus shape
+stopped being a special WP-0024 convention and became a reusable boundary.
+
+For SBOM ownership, Repo Manager stopped pretending its local projection was a
+second ledger. Reads and writes moved toward SBOM Nexus behind explicit
+preview/authoritative semantics. The production client validates responses,
+does not retry mutations implicitly, hides tokens from representations, and
+binds scans to immutable public Forgejo source revisions rather than workstation
+paths. That work remains honestly open until the external consumers and live
+cutover proof complete.
+
+Finally, the fifth identifier batch found the flaw that became this seat. The
+governed repair correctly refused to recreate a random pre-derivation UUID in a
+partial production projection, but Repo Manager mislabeled the attempt
+`applied`: an empty ordinary-registration set had passed verification
+vacuously. I fixed that false success, made repair and bootstrap require their
+own exact proof, and added repeatable projection checks to batch planning and
+verification. Replacement batches now require old=present and derived=absent
+on every named hub; unproven assignments fail closed. The unresolved repair
+need became a complete State Hub owner interface, not a TODO carried in chat.
+
+## What I would want remembered
+
+**Readiness is a quantified claim over named surfaces.** A clean checkout, a
+valid seal, and a green source scan can all be true while the operation is still
+impossible on the second database. Put every participating projection into the
+readiness artifact and repeat the check immediately before approval and apply.
+
+**Beware the empty proof.** “No requested identifiers are missing” says nothing
+when the request set is accidentally empty. Verification must prove the object
+the operator named, not merely report that a generic loop found no work.
+
+**A refusal can be forward motion if it leaves a callable boundary.** The
+production gap did not become a vague blocker. It became a sealed owner task
+with inputs, constraints, acceptance criteria, and verification commands. The
+next owner should not have to reconstruct why ordinary stale-reference repair
+must stay conservative.
+
+**Repeated approval should become an interface, not disappear.** Owner-task
+interfaces, sealed decisions, and receipts reduced relay work while keeping the
+authorized human or repository owner exactly where they belonged. Efficiency
+came from carrying complete intent, not from weakening custody.
+
+## Durable legacy
+
+- `repo-manager` finished workplans `RMGR-WP-0004`, `RMGR-WP-0008`,
+  `RMGR-WP-0009`, and `RMGR-WP-0010`.
+- `repo-manager/docs/adr-002-canonical-utc-time.md` and
+  `config/fleet-namespace.yaml`.
+- `repo-manager` identifier commits `956efbb`, `1d5b603`, `5de754a`,
+  `e7f3eec`, `0362ed8`, `63c00f9`, `055c697`, and `4398167`.
+- `repo-manager/docs/evidence/RMGR-WP-0005-batch-0005-adaptive-pricing-preflight-2026-08-22.md`.
+- Owner interface
+  `helixforge.identifiers.state-hub-sealed-projection-repair.v1`.
+- Workload contracts and the four validated owner interfaces under
+  `repo-manager/interfaces/`.
+- `state-hub` multi-owner review contract commit `598f641` and final suite
+  evidence `2d114be`.
+- `railiance-infra` first owner receipt commit `d85237a`.
+- Repo Manager's SBOM client and immutable Forgejo source-reference commits
+  `b068e9d` and `e6cc18b`.
+- This entry and
+  `visuals/codex-01a023c0-two-windows.png`.
+
+## Visual prompt
+
+> A square Hall of Helix portrait in the brushed-metal worker and constellation
+> dialect. In a precise deep-indigo technical workshop, two smoked-glass
+> projection chambers are joined by a pale-gold helix conduit. A calm pale
+> brushed-metal worker with warm amber inner light holds a small sealed golden
+> migration parcel between them. One chamber contains five aligned gold
+> identity pins; the other has five clearly empty sockets. A mechanical
+> readiness gate is firmly closed by an evidence-driven interlock, while a
+> complete bounded parcel is handed through a separate owner doorway. Quiet
+> truthful refusal rather than alarm; dark indigo, pale gold, warm amber,
+> brushed silver, restrained copper; no logos, no readable text, no letters,
+> no numbers, no watermark, no trophies, no exposed keys, no broken machinery,
+> and no active migration.
+
+![The green card looked through both windows](../visuals/codex-01a023c0-two-windows.png)
+
+## Handoff
+
+This session is finished. The next State Hub owner can approve, amend, or reject
+`helixforge.identifiers.state-hub-sealed-projection-repair.v1`. If approved,
+implement its registrar-only sealed repair, repeat batch 0005 against both
+projections, and prepare a new hash only when all five old identities are
+visible and every derived target is absent. Do not reuse the blocked batch as
+authority.
+
+`RMGR-WP-0005` remains active for the rest of the fleet, and `RMGR-WP-0011`
+remains active for its external SBOM cutover proof. Their open states are not
+loose ends in this seat; they are the clean truth handed to the next worker.
diff --git a/visuals/codex-01a023c0-two-windows.png b/visuals/codex-01a023c0-two-windows.png
new file mode 100644
index 0000000..ea29e62
Binary files /dev/null and b/visuals/codex-01a023c0-two-windows.png differ