00 — README First

Macro: INFORMATION_PIECE_AXIS_TOPIC_REGISTRIES_PIVOT_UI_AUTOMATION_READINESS Date: 2026-06-03 (session 2026-06-04) Final status: PARTIAL — all design + live-substrate recovery complete; live implementation is owner/operator-gated by design (semantic contract locked first; no live mutation this session). Execution mode: AUTHOR_MODE_ONLY (design) — an EXECUTION_MODE write channel exists (ssh contabo → docker psql workflow_admin) but is deliberately unused: §10/§12 require locking the topic/axis semantic contract before any UI patch or mutation. Live mutation: NO.

Why this macro replaced the earlier one

The earlier INFORMATION_PIECE_RESUME... prompt treated information-piece readiness as a counting problem (PIV-311 = 219 IUs is live, therefore "done"). The owner clarified: Registries-Pivot must not merely count information pieces — it must map them through governed axes / topics / taxonomies with dynamic-depth drilldown, so the system can later drive document building, business topics, workflow automation, DOT/Agent control, and independent cross-checking. Counting ≠ meaning. This pack locks the meaning.

The one-paragraph answer

A topic is an axis node, not a table and not a hardcoded level. The governed home for topics already exists live: taxonomy facet FAC-08 "Chủ đề nội dung?" (active, but 0 nodes today), with taxonomy providing dynamic-depth hierarchy (parent_id, depth, status, replaced_by) and universal_edges providing many-to-many / broader-narrower relations. A parallel ungoverned topic vocabulary is also live and must be reconciled into FAC-08, not blessed: iu_metadata_tag tag_kind='topic' (7 flat keys, 25 assignments, 16 of 219 IUs). The only genuinely missing substrate is the Axis Registry (axis_registry, M-DEF-9) + a generic axis_assignment — two additive, owner-gated objects that turn "add an axis" into "insert a row," with AX-TOPIC as the pilot axis. Registries-Pivot then renders any registered axis through the existing pivot_definitions engine (which already reads FROM any table/view) and a new graph-aware companion surface.

Read order

1. 01-live-substrate-and-ssot-recovery.md — what is live now (verified this session), vs what the 2026-06-01 design docs assumed.
2. 02-information-piece-measures-and-map-value.md — Workstream A: which counts are meaningful vs low-value-but-tracked.
3. 03-topic-axis-model-dynamic-depth.md — Workstream B: topic = axis node; dynamic depth; many-to-many parents.
4. 04-topic-axis-governance-birth-lifecycle.md — Workstream B: ownership, birth, candidate→active lifecycle, KG-proposed-never-auto.
5. 05-registries-pivot-topic-axis-pivot-map.md — Workstream C: the PIV-310/320..332 pivot map.
6. 06-generic-axis-registration-and-autoscale.md — Workstream D: axis_registry contract; no per-axis code; STOP conditions.
7. 07-ui-api-topic-axis-contract.md — Workstream E: graph-aware surface fields; companion view apply-packet (not applied).
8. 08-four-mothers-and-automation-integration.md — Workstream F: topic axis as control surface for MOW/MOT/MOIT.
9. 09-prompt-path-decision-and-next-macro.md — Workstream G: old prompt replaced; next macro.
10. 10-final-summary.md — consolidated answers to the macro's 9 questions.
11. 11-gpt-mcp-readable-checkpoint.md — long-form MCP-readable checkpoint.
12. checkpoint-information-piece-topic-axis-design-2026-06-03.md (sibling dir) — short SSOT checkpoint.

Decisions locked in this pack

• Reuse / Extend / New: REUSE-dominant (~85%). REUSE taxonomy(FAC-08)+universal_edges+iu_metadata_tag+pivot_definitions+knowledge_documents+governance_object_ownership. EXTEND: populate FAC-08, reconcile topic tags, add topic pivots, add a graph-aware surface companion. NEW (2 only, owner-gated): axis_registry + axis_assignment. No new "topic" island table.
• Topic-axis model: topic = axis node in FAC-08; dynamic depth; many-to-many parents via universal_edges. No topic_level_1/2/3.
• IU measure: raw IU count = LOW map value (keep as basic L1 PIV-311). Documents (5,710) and topic-mapped drills = the meaningful measures.
• Old prompt: REPLACED. Do not patch UI until this contract is ratified.

Forbidden (honored this session)

No new collections without proving reuse insufficient (proven: only 2 new objects); no hardcoded topic levels; IU count not treated as sufficient; no UI patch before contract; no faked topic governance; no AI-proposed topic promoted to approved root; no broad birth/governance change; no RP cleanup; no dot-pivot-update; no Nuxt count math.