---

title: 03 — Final Human Ratification Session Pack date: 2026-05-31 gate: RG1 + RG2 · decision by human/council only (Đ32) · agent records, never signs

03 — Final Human Ratification Session Pack

Single-sitting pack so the human/council can ratify in one pass. Full design detail = gateway pack doc 02; this is the final, live-refreshed session sheet.

A. Decision summary (what the signer is being asked)

Ratify RG1 (Master Design v0.1) + RG2 (count-integrity model), which unlocks macro M2 = COMMIT of the six read-only objects. Everything else stays gated.

B. Live state the signer must see (not the stale numbers)

• Leaf 160 · net_gap +148 (live-fluctuating ~+147–148; CAT-023 birth writing) · drift 3 · unverified 5 · orphan 0 · status FAILED (explainable).
• Drift: CAT-006 +146 (model-B phantom candidate, stable) · CAT-007 −15 (model-B unregistered, stable) · CAT-023 +17 (model-A live-write race).
• Pivot coverage 21/160 (139 PIVOT_MISSING + 5 unmeasured) — surfaced honestly.
• Six objects re-rehearsed GREEN this session; rolled back clean (doc 04).
• No prior approval exists (doc 02). This is the first human gate.

C. Commit scope (exactly what M2 will create — read-only layer)

v_registry_leaf_set · v_count_integrity · v_count_drift · v_living_lists · v_registries_pivot_tree · fn_registries_pivot_node_substrate(text). Pure views + one STABLE fn over existing tables. No base-table change, no row change, no Nuxt change.

D. EXACT APPROVAL WORDING (human/council fills; agent MUST NOT)

REGISTRIES-PIVOT RG1+RG2 RATIFICATION — <date>
Ratifier: <name> / <role>   (Đ32: human/council; not an agent or orchestrator-* function)

RG1  Master Design v0.1 ratified ........................ [ APPROVE / DEFER / REJECT ]
RG2  Count-integrity model accepted (leaf-scope+invariant+drift; live net_gap ≈ +148,
     FAILED-but-explainable; 3 drift + 5 unmeasured) ..... [ APPROVE / DEFER / REJECT ]

Unlocks M2 — COMMIT six read-only objects (doc 04):
  v_registry_leaf_set / v_count_integrity / v_count_drift /
  v_living_lists / v_registries_pivot_tree / fn_registries_pivot_node_substrate(text) [ APPROVE / DEFER ]

Explicitly DEFERRED (not approved here): missing pivots PIV-500/30x/31x (RG3);
  parent_code+pivot_code drill wiring; display_policy threshold (RG5); registry_pin (RG5+Đ32);
  phantom law (RG4 council); Directus/API (P2); Nuxt render-shell (P4); legacy retirement (P4).

Conditions: COMMIT off-peak; re-run the BEGIN..ROLLBACK rehearsal immediately before COMMIT and
confirm V1=160, drift-closure holds, tree 37/37/0; 999_rollback staged.
Signature: ____________________   Date: __________

E. Rollback statement (Đ30)

Objects are additive, read-only. COMMIT changes no base table and no row. Reversal = DROP … IF EXISTS in reverse dependency order (gateway doc 03 / this doc 04). Pre-commit rehearsal demonstrates clean teardown (0 leftover, idle_tx 0).

F. Risk statement

risk	sev	mitigation
numbers move between ratify & commit	low	views compute live; re-run rehearsal at commit
CREATE OR REPLACE column drift on re-run	low	fresh first commit; CI diff (M12)
coverage 21/160 PIVOT_MISSING	med	honest flag; fixed by M3 (PIV-500/30x/31x), not by faking
reviewer anchors on stale +36,783	med	§B shows live +148

G. What happens if REJECTED

• No objects created; system stays exactly as today (legacy /knowledge/registries + gap-math API keep serving).
• The deferred commit-ready pack (doc 04) remains valid for a future session; nothing is lost.
• If RG2 is rejected specifically over "FAILED", note: FAILED is the correct status; the views EXPOSE the 3 drift + 5 unmeasured honestly rather than hiding them. Rejecting blocks the honest surface and leaves the Đ28-violating gap-math in place. A "DEFER with conditions" (e.g. require PIV-500 first) is the likely middle path → routes to M3 before M2.

H. Governance note

Agent prepared this packet (proposal only). Recording the signed outcome to KB knowledge/dev/laws/.../registries-pivot-rg1-rg2-ratification-outcome-<date>.md is macro M1. No self-approval. No fake approval.