Macro-5 Caveat Register — R2-B2 (2026-06-19)

Date: 2026-06-19 · Workstream: R2-B2-MACRO-5-STAGING-BUILD-AUTHORIZATION-PACKAGE-2026-06-19 (Deliverable 101 of 110) · Editorial revision: rev1 Class: caveat register · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO write performed.

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

---

0. Status and non-authorization

STATUS: PASS — engineering / design-only. The caveats carried into and out of Macro-5. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Keep every carried caveat visible; resolve none.

2. Sources / evidence read

Macro-4 caveat register (D-lineage); R1a/R2a Codex caveats (CAV-1…6); FRESH 2026-06-19 checks. Main process, no reader-agents.

3. Accepted baseline (carried)

Caveats are carried, not closed; new evidence does not retroactively resolve a caveat.

4. Evidence / analysis — caveat register

Caveat	Statement	Status
CAV-1	no executor log; DB/contract-layer evidence only	carried
CAV-2	no provenance SoT; substrate-only	carried
CAV-3	old 2026-03-21 logs unavailable	carried
CAV-4	synced mirror ≠ live binary	carried
CAV-5	app.birth_gate_mode GUC unreadable via query_pg (OOB); inherited warn-mode	carried (FRESH-reconfirmed)
CAV-6	prior combined-exec metadata typo	carried
WC-1…3	three wording constraints (recommendation≠decision; design≠TD; engineering≠authority)	carried
process caveat	read first-hand, main-process, no reader-agents; /tmp-style decode = scratch	honored

5. Candidate / requirement / gate / result

All caveats remain carried; Macro-5 resolved none. CAV-5 is reconfirmed FRESH (GUC still OOB). The process caveat was honored this run.

6. Owner-gated future work

Resolving any caveat (e.g. log recovery, GUC read) is Owner-gated/out-of-band; not done here.

7. What remains unresolved

All caveats carried.

8. Ready for GPT/Codex review

Yes — Codex should confirm no caveat is silently closed.