Macro-9A2 — Handbook Precision Patch (Codex HOLD) — Execution Report

Mission: R2-B2-MACRO-9A2-HANDBOOK-PRECISION-PATCH-CODEX-HOLD-2026-06-19 Type: KB-document-only correction of the three Codex HOLD defects. No design, no Macro-9B, no execution. Authority: Codex joint review HOLD (rev2) — knowledge/dev/laws-new/reports/codex/codex-review-dot-manage-and-collections-manage-handbooks-2026-06-19.md. Evidence date: 2026-06-19 · 2 read-only query_pg schema-verification queries (DB directus, pg_namespace/pg_class). 0 mutating calls to the substrate. Only mutations = KB-document patches/upload listed below. Method: read the Codex HOLD report + both handbooks + the three execution reports from AgentData KB; verified the schema identity read-only against the live catalog; applied targeted anchored patch_document edits only (no full-body rewrite); read every patched file back from KB.

---

STATUS

PASS_WITH_CAVEATS — all three Codex HOLD defects are closed by KB-document patches, verified by read-back. The schema identity was resolved against the live read-only catalog (only cutter_governance exists; cutter_gov does not). No runtime mutation, no design, no Macro-9B.

• Caveat C-1: the corrections are documentation precision fixes; the underlying read-denied/inferred caveats of the handbooks (restricted schemas, inferred Read/Write) are unchanged and still disclosed.
• Caveat C-2: the 63 Group-A Write rows retain the note "writes prod public-NOT run-scoped schema" (factually correct for Write DOTs, and Codex required correction only for Read/Unknown rows); only the 27 Read/Unknown rows were neutralised.

Engineering PASS ≠ Owner authority PASS. This report enacts nothing, authorises nothing, and launches no Macro-9B. Default = HOLD; Macro-9A build = NO-GO (unchanged).

---

PATCHED FILES

File	Revision before	Revision after	content_length after	Patch
knowledge/dev/laws-new/newlaws/collections-manage/collections-usage-handbook.md	6	9	91740	Defect 2 (Group-E arithmetic) · Defect 1 schema-correction note (§5 preamble) · Defect 1 rename 48× cutter_gov→cutter_governance across §5 rows STT 203–226
knowledge/dev/laws-new/newlaws/dot-manage/dot-usage-handbook.md	1	7	107137	Defect 3 §5.3 Group-A legend rewrite · Defect 3 neutralise 27 Read/Unknown Group-A row notes
knowledge/dev/laws-new/newlaws/collections-manage/reports/macro9a1-collections-usage-handbook-execution-report-2026-06-19.md	1	2	(correction note appended)	C5 correction note (handbook now rev9; Defects 1 & 2)
knowledge/dev/laws-new/newlaws/dot-manage/reports/macro9a0-dot-usage-handbook-full-row-inventory-supplement-report-2026-06-19.md	1	2	(correction note appended)	C5 correction note (handbook now rev7; the "all 90 Group-A rows write" claim superseded)
knowledge/dev/laws-new/newlaws/reports/macro9a2-handbook-precision-patch-codex-hold-report-2026-06-19.md	—	1	(this file)	new correction report

The DOT handbook canonical copy at dot-manage/dot-usage-handbook.md was the review target (Codex "Files Reviewed" = rev1/106855). It is now rev7/107137. The legacy pointer copy at operations/dot-usage-handbook.md was not touched (out of scope; it is a deprecated pointer).

---

CODEX DEFECT CLOSURE

Defect	Before	After	Verdict
1 — cutter schema identity (collections)	§5 rows STT 203–226 named the schema cutter_gov (48 occurrences = 24 rows × {Schema cell + PG cutter_gov* path}); scope/§4/§11/§15 named cutter_governance; no alias declared.	All §5 cells + access paths now read cutter_governance (the only schema that exists). Typo-correction note added to §5 preamble explicitly declaring cutter_gov was a transcription typo, not an alias. 0 | cutter_gov | cells / 0 PG cutter_gov* paths remain (the only 2 residual cutter_gov tokens are inside the correction note, as Codex permits).	CLOSED
2 — Group-E arithmetic (collections)	Group-E narrative: "82 objects: 58 public, 24 cutter_governance, 8 sandbox_tac, 2 iu_core" → breakdown summed to 92.	Narrative now: "82 = 58 public + 24 cutter_governance; sandbox_tac (8) and iu_core staging (2) rows are classified under Group H (§8), not Group E." §4 group summary (Group E = 82; total 382) was already correct and is unchanged.	CLOSED
3 — Group-A "every row writes" wording (DOT)	§5.3 legend: "every Group A row writes the existing prod public schema"; all 90 Group-A row notes carried "writes prod public-NOT run-scoped schema" — false for the 16 Read + 11 Unknown rows.	Legend rewritten: Group-A rows target / ensure / diff / snapshot / register / probe prod public / Directus collection layer; none is a run-scoped disposable staging-schema builder; the Read/Write column governs effect (Write = schema-affecting, Read = observation, Unknown = triage). The 27 Read/Unknown row notes → "prod public layer; NOT run-scoped schema"; the 63 Write rows retain "writes prod public-NOT run-scoped schema". §15 NO-GO verdict unchanged.	CLOSED

---

SCHEMA NAME VERIFICATION (read-only)

Candidate	Exists?	Object count	Evidence
cutter_governance	Yes	36 relations = 24 tables + 12 views	query_pg (DB directus) over pg_namespace/pg_class: relkind r/p=24, v=12, m/f=0
cutter_gov	No	0	query_pg pg_namespace WHERE nspname LIKE 'cutter%' returned only cutter_governance (also confirmed iu_core=4, public=1033, sandbox_tac=8 objects)

Conclusion: exactly one schema exists; cutter_gov is a typo, not an alias. The handbook uses cutter_governance consistently and the typo is recorded as a corrected typo note (per Codex "do not mention the other except as corrected typo note").

---

COUNTS AFTER PATCH

Check	Value
Collections — | cutter_gov | schema cells remaining	0
Collections — PG cutter_gov* access paths remaining	0
Collections — standalone cutter_gov tokens remaining	2 (both inside the §5 correction note)
Collections — cutter_governance occurrences	58
Collections — §4 Group E count	82
Collections — §4 total ("sums to 382")	382
DOT — Group-A rows total	90 (63 Write + 16 Read + 11 Unknown)
DOT — "writes prod public-NOT run-scoped schema" remaining	63 (Write rows only)
DOT — "prod public layer; NOT run-scoped schema" added	27 (16 Read + 11 Unknown)
DOT — Read/Unknown Group-A rows still implying write	0
DOT — old legend "every Group A row writes" present	no (removed)

---

NON-AUTHORIZATION

Action	Result
DB write	none
DDL / DML	none
Schema / table / collection creation	none
Directus mutation	none
DOT execution	none
psql / manual SQL run	none (and not recommended as valid — still forbidden)
Runtime config flip	none
Owner row (governance_object_ownership)	none
KG write / birth / certify / promote / backlog / bad-input / B2 logic / actual B2 TD	none
dot_operator_catalog / collection_operator_catalog	not created (remain candidate-on-paper)
Macro-9B launch	not launched
Macro-9A build	still NO-GO
Substrate calls made	2 read-only query_pg (schema verification) only
KB mutations made	3 handbook/report patches + 2 report correction notes + this report (KB-document-only)

---

SELF-CHECK

Check	Result
SC1 No runtime mutation	✅ only 2 read-only query_pg; all other writes are KB documents
SC2 Codex defect 1 closed	✅ schema identity = cutter_governance everywhere; typo noted
SC3 Codex defect 2 closed	✅ Group E = 58 + 24 = 82; sandbox/iu → Group H
SC4 Codex defect 3 closed	✅ legend rewritten; 27 Read/Unknown notes neutralised; 63 Write retained
SC5 DOT-only rule still intact	✅ §3 / §13–§14 unchanged in both handbooks
SC6 Manual SQL/psql still forbidden	✅ unchanged; not recommended anywhere
SC7 Macro-9A still NO-GO	✅ §15/§16 verdicts unchanged
SC8 Macro-9B not launched	✅ no design/build started
SC9 Future registries not created	✅ dot_operator_catalog / collection_operator_catalog remain paper candidates
SC10 Corrected files read back	✅ both handbooks re-fetched & verified; reports re-read
SC11 Correction report read back	✅ this file read back after upload

---

READY FOR CODEX RE-REVIEW

yes — the three HOLD defects are corrected and verified by read-back; only the corrected package (dot-manage + collections-manage, with this macro9a2 correction report) should be re-reviewed. No Macro-9B is bundled.

End of correction report. STATUS PASS_WITH_CAVEATS. Engineering PASS ≠ Owner authority PASS. Default HOLD.