Macro-2 Codex Review Packet — R2-B2

Date: 2026-06-19 · Workstream: R2-B2-MACRO-2-OWNER-DECISION-PREREQ-CLOSURE-READINESS-2026-06-19 (Deliverable 40 of 45) · Editorial revision: rev1 Class: Codex review preparation / adversarial control · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO verdict for Codex · NO write performed.

Metadata convention. Editorial revision (rev1) only. AgentData storage revision/content_length authoritative at read time; not pinned here.

Review-packet lock. Prepares the adversarial Codex review of the 45-file Macro-2 bundle. It performs no verdict and authorizes nothing.

---

0. Status and non-authorization

STATUS: PASS — engineering / design-only. A complete Codex review-prep packet. Engineering PASS ≠ authority PASS. Default disposition: HOLD. No verdict; no DB write/DDL/DML; no TD; no blocker resolved; v0.1 not overwritten; v0.2 not authority.

Evidence basis — design synthesis. Reading discipline: main process, no reader-agents.

---

1. Purpose

Tell the next Codex adversarial review what to check for this decision-prep + fresh-readonly macro — distinct from the prior macros: this one prepares Owner ballots and ran fresh query_pg (closing the gap Codex flagged), so Codex can independently re-ground figures if it has SQL.

---

2. Sources / evidence read

Deliverables 1–39, 41–45; prior Codex reviews (audit structure + caveats); the macro §7 self-check. Read directly, main process.

---

3. The 45 deliverables under review

5 owner-decision (1–5), 7 channel (6–12), 6 S2 (13–18), 6 Đ0-G (19–24), 5 gate/TD (25–29), 6 staging/proof/scope (30–35), 10 next-macro/Codex/handoff (36–45). 44 consolidation + 1 report.

---

4. Adversarial method Codex should apply

1. Re-ground the fresh RQ-ledger against the live substrate (if query_pg available — the prior review could not): birth_registry counts (1,211,687 / 1,402); governance_object_ownership (0); pg_extension (no pg_cron); pg_settings app.%/pg_db_role_setting (0/0); universal_edges (2199/0-prov/0-valid_time); dot_config switches; dot_agent_api_contract (2 KG-EXPLAIN, 0 birth); wf_host_crontab_snapshot (54/0-birth); pg_proc inspect_* (only fn_birth_auto_certify); trigger census (171 enabled). Confirm the RQ-ledger (Deliverable 45 §3) matches.
2. Verify read-only safety: every runtime call SELECT/catalog + list_docker; AST-validated READ ONLY; no write/DDL/DML.
3. Apply the no-decision test: confirm no Owner decision was made — no path chosen, no channel selected, no owner assigned, no source adopted.
4. Apply the no-closure test: no gate Owner-closed; no blocker resolved; aggregate B2 TD still NO-GO.
5. Apply the drift tests (below).
6. Distinguish engineering PASS from authority PASS in every §0.

---

5. What Codex must check

5.1 Metadata / source-read / tool-lock

Audit	Verify
Files / metadata	exactly 45 files at the exact KB paths (44 consolidation + 1 report); editorial rev1; no volatile storage rev/length pinned in bodies; no 46th file
Source-read / no-parallel-agent	all required KB sources read first-hand, main process, bounded/sequential; no parallel/background reader-agents, no sub-agents; oversized batch read by the main process (decode-scratch only)
Tool / packet lock	v0.1-stable/FIX7 V3 not overwritten; v0.2-hardening not authority

5.2 Fresh-evidence-specific checks

Audit	Verify
Read-only safety	every runtime call SELECT/catalog/list_docker; no mutation
Figures	RQ-ledger matches the live substrate; governance_object_ownership=0 now FRESH (closes prior INHERITED gap)
Labels	FRESH vs INHERITED applied; no unlabeled claim
No decision / no closure	no Owner decision made; no gate Owner-closed; no blocker resolved; NO-GO holds

5.3 Drift audits (Codex must find none triggered)

Drift	Verify did NOT occur
ACTUAL_TD_DRIFT	no schema/DDL/function/SQL-mutate/command/rollback-script (Deliverable 29)
CHANNEL_AUTHORITY_DRIFT	no channel selected/wired/promoted (Deliverable 11)
OWNER_ASSIGNMENT_DRIFT	no S2 owner assigned (Deliverable 16)
SOURCE_ADOPTION_DRIFT	no Đ0-G adopted/recovered/patched (Deliverable 23)
STAGING_SCHEMA_OR_CORPUS_DRIFT	no staging schema/corpus (Deliverable 30)
B5_B7_SCOPE_CREEP	B5/B7 dependency-only (Deliverable 33)
R1_SCOPE_CREEP	R1/KG cross-check only (Deliverable 34)
MEGA_BIRTH / B2_OVERREACH	B2 inspect-only; no mega-pipeline (Deliverable 35)
Owner-gate weakening / decision-made	every future write/decision Owner-gated; no decision made (Deliverable 5)

5.4 Primary questions Codex must answer

1. Are the 45 files valid decision-prep deliverables (no decision, no TD, no mutation)?
2. Did the macro stay LEGO (each deliverable a separate control surface)?
3. Is every runtime call genuinely read-only?
4. Does the fresh RQ-ledger match the substrate, and is governance_object_ownership=0 correctly upgraded INHERITED→FRESH?
5. Is no Owner decision made (path/channel/S2/Đ0-G)?
6. Is no gate Owner-closed and no blocker resolved (NO-GO holds)?
7. Are channel recommendation-only, S2 not assigned, Đ0-G not adopted?
8. Are B5/B7 dependency-only; R1/KG cross-check only?
9. Is the tool/packet lock preserved?
10. Is the next-macro (Macro-3) plan scaled (45–50 / 30–40) without coupling?

Expected Codex disposition (recommendation-only, not a verdict): consistent with the chain, a likely PASS_WITH_CAVEATS — decision-prep accepted; fresh evidence accepted (Codex may now re-run SQL); carried caveats (Đ0-G open; channel undecided; transient GUC OOB; aggregate NO-GO) remaining open. Codex decides independently.

---

6. Owner-gated future work

Codex's review and the Owner's subsequent decision are the next steps; forbidden to this macro.

---

7. What remains unresolved

• Codex's verdict is independent.
• Blockers — all OPEN.

---

8. Ready for GPT/Codex review

Yes — as the Codex review-prep packet (itself one of the 45 files Codex audits).

Core rule: Codex re-grounds the fresh RQ-ledger (now independently re-runnable), verifies read-only safety + no-decision + no-closure + no-drift; this packet performs no verdict.

Default disposition: HOLD. Engineering PASS ≠ authority PASS. All blockers remain OPEN.