Topic Axis — Ratify / Apply / Pilot / Surface / Automation Bridge — 00 README FIRST

Date: 2026-06-04 Macro: TOPIC_AXIS_RATIFY_APPLY_PILOT_POPULATE_SURFACE_AND_AUTOMATION_BRIDGE Final status: PARTIAL → strongest safe state reached. Pilot substrate is LIVE; ratification/activation is owner/GOV-COUNCIL gated by design. Execution mode: EXECUTION_MODE (additive only). Live mutation: YES (additive, reversible).

What this package is

Moves the locked Topic-Axis semantic contract from design to a live additive pilot plus an owner/operator apply packet for the gated remainder. The semantic contract (Information Pieces mapped through a governed dynamic Topic Axis, not merely counted) is unchanged and respected.

What went LIVE in production (additive, reversible)

1. axis_registry — generic governed-axis registry (1 row: AX-TOPIC, status CANDIDATE).
2. axis_assignment — generic node→target assignment table (25 candidate rows reconciled from iu_metadata_tag topic:*, evidence preserved).
3. v_registries_pivot_axis_surface — DAG-aware read-only axis surface (7 candidate nodes).
4. v_axis_topic_pivots — live-computable topic pivots PIV-310/320..332 (CANDIDATE classification, no canon birth).
5. fn_topic_node_substrate(text) — read-only DAG-aware topic node substrate resolver.

All five are pure additive infrastructure. Rollback = DROP (script: /tmp/axis_rollback.sql, reproduced in doc 02). No business table mutated. Original iu_metadata_tag topic tags untouched (25 verified before and after).

What is GATED (operator/owner apply packet, NOT applied) — doc 02 §packet, doc 03

• Owner law-ratification → governance_object_ownership rows for axis_registry/axis_assignment/AX-TOPIC.
• GOV-COUNCIL approval + creation of FAC-08 root topic nodes in taxonomy (blocked because taxonomy INSERT fires fn_birth_registry_auto → unretirable birth + trg_after_sync_edges → universal_edges writes).
• AX-TOPIC CANDIDATE → ACTIVE flip.
• Canon pivot_definitions topic pivots (the live v_axis_topic_pivots exposes the same numbers now without birth).
• UI/API /axes routes (doc 07) + 4-Mothers automation wiring (doc 08).

Why pilot-not-island

• Only 2 new generic objects created (axis_registry + axis_assignment). No topic island table. No topic_level_1/2/3. AX-TOPIC is a row, not schema. A second axis (e.g. FAC-09 "Tầng kiến trúc?") is another row, no code.
• Candidate topic identity lives in axis_assignment.node_code as a token (TOPIC-CAND:*) with no FK to taxonomy, so candidates exist without mutating the governed taxonomy or triggering births. Ratification promotes tokens → real taxonomy codes (doc 03).

Read order

00 (this) → 01 live substrate → 02 axis substrate + packet → 03 AX-TOPIC → 04 reconciliation → 05 pivots → 06 surface/resolver → 07 UI/API → 08 automation → 09 safety audit → 10 decision → 11 summary → 12 checkpoint.

Exact blocker

Owner law-ratification + GOV-COUNCIL FAC-08 root approval (Điều 32). No engineering blocker remains for the pilot. Next macro: RP_UI_CONSUME_AXIS_SURFACE (see doc 10).