11 — GPT/MCP-Readable Checkpoint (long-form)

Macro: INFORMATION_PIECE_AXIS_TOPIC_REGISTRIES_PIVOT_UI_AUTOMATION_READINESS Date: 2026-06-03 (run 2026-06-04). Status: PARTIAL. Execution mode: AUTHOR_MODE_ONLY (EXECUTION write channel available, deliberately unused). Live mutation: NO.

One-line thesis

A topic is an axis node (taxonomy facet FAC-08), not a hardcoded level; the substrate is ~85% live; only axis_registry + axis_assignment are missing; Registries-Pivot renders any registered axis through the live pivot engine + a new graph-aware companion surface. Topic is the pilot axis.

Live facts (verified this session, query_pg directus RO)

• RP surface LIVE: v_registries_pivot_surface (34 cols, tree-shaped), v_registries_pivot_node_contract, v_registries_pivot_tree, v_rp_aggregate_candidate_register, registry_pin (empty), rp_grouping_policy (50). pivot_definitions 39/37-active, parent_code graph live, engine reads FROM any relation.
• IU: information_unit = 219 (law_unit 187 + design_doc_section 32) = PIV-311. iu_metadata_tag 536 total; topic assignments 25 over 16/219 IUs. iu_relation 60. knowledge_documents 5,710.
• Topic/taxonomy: taxonomy_facets 10 facets; FAC-08 "Chủ đề nội dung?" active, 0 nodes; FAC-07/FAC-09 also 0; FAC-01 expertise 29 nodes (hierarchical). taxonomy store has parent_id/depth/status/replaced_by (dynamic depth + lifecycle). Parallel ungoverned topic vocab: iu_metadata_tag_registry tag_kind='topic' = 7 flat keys.
• Governance: governance_object_ownership, governance_responsibility_scope, universal_edges, system_issues, event_type_registry, approval_requests, birth_registry all EXIST (docs said some were unbuilt — corrected). axis_registry/axis_assignment/axis_node/axis_relation/entity_relations/topic table all ABSENT.

Decisions

• Reuse/Extend/New: REUSE-dominant. NEW = exactly 2 objects (axis_registry, axis_assignment), owner-gated. EXTEND = populate FAC-08, reconcile topic tags→candidates, add PIV-310/320..332, add companion surface. No topic island table.
• Topic-axis model: topic = FAC-08 node; dynamic depth via parent_id ∪ universal_edges; many-to-many parents; Layer-1 = active roots; no topic_level_1/2/3.
• IU measure: raw IU count = low map value (keep PIV-311, demote from headline); headline = topic axis.
• Pivot map: PIV-310 docs + PIV-320..332 topic axis (defined; honest 0/small; candidates in register not canon).
• Auto-scale: axis_registry row per axis; STOP conditions detected like orphans; topic = pilot only.
• UI/API: graph-aware companion v_registries_pivot_axis_surface (tree surface is DAG-unsafe); 7 net-new fields; apply-packet authored NOT applied.
• 4 Mothers: topic axis = control surface for MOW (workflow select), MOT (task group/route), MOIT (improvement route), document-building (template select); edges via universal_edges; not yet wired.
• Old prompt: REPLACED; UI patch deferred behind contract.

Honest gaps / not-faked

• Topic axis is defined but empty (FAC-08 0 nodes; doc topic coverage 0; IU topic coverage 7%). Reported honestly.
• IU is an island (0 approval_requests reference IU; no owner). Topic governance must be stood up, not assumed.
• axis_assignment + topic↔workflow/DOT/event edges do not exist → relation pivots (PIV-325/327/328) defined but report 0.

Blockers (exact)

1. Owner law ratification of axis_registry + axis_assignment + AX-TOPIC registration.
2. GOV-COUNCIL approval of initial FAC-08 root topics (Điều 32 APR). AI may propose candidates only (Điều 39 Golden Rule).
3. Operator apply of the additive packet (companion surface, resolver, pivots) + topic ownership rows.

Next macro

TOPIC_AXIS_RATIFY_AND_PILOT_POPULATE → RP_UI_CONSUME_AXIS_SURFACE → TOPIC_AXIS_EDGE_POPULATION_AND_AUTOMATION. (Aggregate law RP_AGGREGATE_LAW_OWNER_RATIFICATION remains separately open.)

Report

knowledge/dev/reports/architecture/information-piece-topic-axis-registries-pivot-design-2026-06-03/ docs 00–11. Short checkpoint: knowledge/dev/reports/architecture/checkpoint-information-piece-topic-axis-design-2026-06-03.md.

Forbidden honored

No new collections beyond 2 proven-necessary; no hardcoded topic levels; IU count not treated as sufficient; no UI patch before contract; no faked topic governance; no AI topic promoted to root; no birth/governance/pre-birth broad change; no RP cleanup; no dot-pivot-update; no Nuxt count math; did not stop at design summary — all 7 workstreams (A–G) complete.