KB-1FC5
Topic Promotion Governed Activation — 02 Governed Topic Promotion (2026-06-03)
2 min read Revision 1
one-roof-governancenonprod-clonetopic-promotionlifecycleprovenance2026-06-03
02 — Objective A: Governed Topic / Axis Promotion — PASS
Artifact: sql/A_topic_promotion.sql (single BEGIN..COMMIT, self-guarded). Rollback: sql/Z_rollback_A.sql. Tag: TEST_CLONE_topic_promo_2026-06-03.
Committed on the clone
- A1 Containment axis candidate→active (lifecycle register→active). Reference axis (structural/deterministic), no coverage_rule — does not impose ownership cells. 3 axes now active.
- A2 New topic values, 3 provenance lanes: observability (ai_proposed)→active; data-platform (human_designated)→active; kg-domain-x (kg_provisional) held candidate (provisional, not auto-activated). Lifecycle = INSERT candidate then UPDATE active, proven in-txn.
- A3 Split: active child
workflow-exec(parent=workflow, op=split). - A4 Deprecate/merge:
gov-legacy→ deprecated, provenance merged_into=governance. - A5 Ownership ratification: accountable owner for modules/workflow (GOV-DOT, kind=human_ratified) — human override of the low-confidence (0.55) assignment.
Result — topic gap reached expected target
Coverage gap 2 → 1 (self-guard asserted exactly −1). Topic axis: required 6, gap 1, ok 3, low_conf 1, stale 1, quarantine 1. Remaining gap = iu_staging_record/ai-ops (quarantine) — correctly uncovered; quarantine items must be cleared before ownership (fail-closed, not a defect).
Value lifecycle post-commit: active 7, candidate 1 (kg-domain-x), deprecated 1 (gov-legacy).
Verdict
PASS. Candidate→active lifecycle, all 3 provenance lanes, split, merge, deprecate, ownership ratification all proven & committed on clone; production untouched.