---

title: 01 — Overview & Control package: registries-pivot-ratify-foundation-commit-preview-campaign-2026-05-31 date: 2026-05-31 host: contabo VPS · DB directus (container postgres, postgres:16) read_channel: KB + live PG read-only (context_pack_readonly) + ssh read apply_channel: ssh contabo → docker exec -i postgres psql -U workflow_admin -d directus (BEGIN..ROLLBACK ONLY) approval_artifact_found: NO (definitive — 3 independent sources) commit_status: DEFERRED (no valid human/council approval; self-approval forbidden) mutation: ZERO net to PG/Directus/Qdrant (4 BEGIN..ROLLBACK sections, all clean) outward_change: 1 — static UI preview deployed (files only, no prod Nuxt/DB), reversible status: PASS

01 — Overview & Control

Human-gated campaign building on registries-pivot-ratification-commit-ready-gateway-2026-05-31 (the canonical detail pack) + the GPT review gpt-review-after-registries-pivot-ratification-gateway-next-command-2026-05-31.md.

Gate 0 (re-verified live 2026-05-31)

contabo VPS · DB directus · role context_pack_readonly · idle_in_tx 0 · six objects still absent (no commit occurred) · pin/threshold tables absent. Routes: /knowledge/registries 200 · /knowledge/pivot 200 · /knowledge/registries-pivot 200 · /ui-preview/registries-pivot/v1/ was 404 → now 200 (deployed). Baseline counts unchanged (meta_catalog 169, pivot_definitions 37, pivot_results 126, entity_labels 722,803, …).

Headline decisions

1. APPROVAL = NO_APPROVAL_FOUND (definitive). KB has no registries-pivot ratification outcome; the GPT-review doc states none was found; the PG approval spine (approval_requests 211) shows only 2 approved rows (old/unrelated) and the 16 registries-related requests are all 2026-03-28 auto-generated birth_orphan/accuracy_drift reviewed by orchestrator-s142b/auto-apply-function — machine, not human/council. Latest request 2026-04-22 (predates all registries-pivot work). → COMMIT FORBIDDEN. Six-object commit DEFERRED. Final ratification pack delivered (doc 03).
2. Live count-integrity re-verified: leaf 160 / Σrecord 2,002,057 / Σactual 2,001,909 / net_gap +148 / drift 3 / unverified 5 / orphan 0. Still FAILED but explainable; net_gap is live-fluctuating ~+147–148 because CAT-023 birth_registry is actively writing (record 985,488 vs actual 985,471 = +17; was +1 then +16 then +17 across the session). CAT-006 +146 and CAT-007 −15 are stable. Drift closure proven (net_gap == Σ drift gap).
3. All foundation rehearsals GREEN this session, zero net mutation (doc 04/15): six-object pack, additive pin/threshold/drill overlay, missing-pivot temp-clone, AND a real pivot INSERT (PIV-311, is_active=false) that fired the full trg_pivot_def_refresh (refresh_meta_catalog + refresh_pivot_results over 35 active pivots) and completed <45 s, rolled back to 37, idle_tx 0.
4. Pivot-engine capability discovered (pivot_query source): allowed_ops = =,!=,>,<,>=,<=,in,not_in,is_null,is_not_null,like (no not_like, no column-vs-column); allowed_funcs = count,sum,avg,min,max. → PIV-500 (needs not_like to drop %_total) and drift/phantom totals (need record<>actual) must be view-backed (v_registry_leaf_set/v_count_drift); PIV-31x label-by-facet and PIV-301 orphan-total are native-DSL-expressible. (Doc 05.)
5. Real no-hardcode violations located in live source /opt/incomex/docker/nuxt-repo/web (doc 13): server/api/registry/health.get.ts:123 totalGap = reduce(+Math.abs(gap)); pages/knowledge/ registries/index.vue:312 hardcoded code:'CAT-017', :271 orphan_count: hd.totalGap, :161-162 reduce-count; [entityType]/index.vue:80-81 reduce; raw-counts.get.ts:58 reduce. No localStorage pins. (Branch K can now run real, not hypothetical, CI.)
6. Static UI preview DEPLOYED (Branch I): https://vps.incomexsaigoncorp.vn/ui-preview/registries-pivot/v1/ HTTP 200 — draft, mock-data only, no prod Nuxt/DB touched, rollback = remove the dir.

Document map

02 approval scan · 03 final ratification session pack · 04 six-object commit/deferred + rehearsal · 05 missing-pivot bundle (+engine capability) · 06 drilldown parent/pivot mapping · 07 threshold/label · 08 registry_pin · 09 phantom law patch · 10 Directus/API exposure · 11 static preview deploy report · 12 legacy retirement readiness · 13 no-hardcode enforcement (+ real violations) · 14 next macro chain · 15 SQL appendix/evidence · 16 self-review.

Forbidden compliance

No COMMIT · no self-approval · no persistent PG/Directus/Qdrant mutation · no production Nuxt change · no route cutover · no legacy retirement before replacement · no fake approvals · no hardcode introduced · no event/job/notification emit. The only outward change is the explicitly-authorized static preview.