Topic Promotion Governed Activation — 00 Overview & State Recovery (2026-06-03)
00 — Overview & State Recovery
Macro: ONE_ROOF_NONPROD_CLONE_TOPIC_PROMOTION_GOVERNED_ACTIVATION_AND_DRIFT_DETECTION
Date: 2026-06-03
Mode: Clone-only persistent commits (TEST_CLONE); production READ-ONLY.
Clone DB: directus_gov_test_20260602 (isolated; 1202 MB).
Production DB: directus (unchanged; read-only proof channel).
Verdict
PASS — all 8 clone objectives (A–H) advanced. The clone moved from "axis/topic substrate works" to "governed topic activation is operationally ready": topics promoted through the candidate→active lifecycle, the topic axis reconciled against the live entity_labels/taxonomy projection, a 10-detector drift suite built, the scanner expanded to a unified idempotent governance scan, the issue/event boundary shaped fail-closed, UI/API projection contracts proven live, and a validated production rollout packet produced. Production is byte-unchanged.
Production baseline (entry == exit, read-only)
db=directus; ownership=0; v_object_owner_gap=210; ospa=0; axis_* tables=0; gov emit=0; idle-in-txn=0; system_issues=202,518 (organic).
Clone baseline (entry)
- ownership seed 30 → gap 0 (100% coverage).
- axis substrate: 6 tables + 16 views. 3 axes: responsibility (active, 210/gap0, canonical), topic (active, 6 assignments/gap2), containment (candidate).
- coverage_rule: CR-RESP-ALL (cross_product), CR-TOPIC-ASSIGNED (per_assignment). axis_object_ownership=4; axis_candidate_finding=34.
Already proven (prior macros)
Substrate build, ownership 100% coverage, topic candidate→active (one pass), assignment coverage, scanner/candidate integration, issue/event boundary, base UI/API reads, gated prod rollout packet.
What this macro advanced
- Containment axis + multiple topic values promoted across 3 provenance lanes.
- Topic axis reconciled vs real entity_labels (804k) / taxonomy (58) / label_rules (38).
- 10 drift detectors (5 reused + 5 new).
- Unified governance scanner (ownership + topic + axis + drift), idempotent/bounded.
- Fail-closed event shaping for all detector types.
- Two-lane (candidate vs official) UI projection + review queue.
- Validated, gated production rollout packet.
Forbidden production scope (honored)
No production writes, schema/data mutation, axis/topic creation, ownership/candidate/ruleset/scan writes, event/issue/log writes, DOT/UI/Directus/Qdrant/Nuxt mutation, approval/os_proposal writes, law/version/status changes.
Rollback / drop strategy
- Objective A data:
sql/Z_rollback_A.sql(deletes by tagTEST_CLONE_topic_promo_2026-06-03; restores containment candidate). - Structure (B–F):
sql/G_prod_99_rollback.sqlpattern. - Clone retained as harness; droppable via
DROP DATABASE directus_gov_test_20260602(~1.2 GB).
Clone final state (exit)
3 active axes; 7 active topic values (gap 1 = quarantine cell only); 41 open drift findings (0 critical); 3 idempotent scan runs; 41 clone-local event-log rows (0 emitted).