10 — Final Summary

Consolidated answers to the macro's nine questions, grounded in live-verified substrate.

Q1 — What should Registries-Pivot count for information pieces?

Three tiers: substrate (raw IU count PIV-311=219, documents PIV-310=5,710 — low map value), axis (topic-axis nodes/relations PIV-320..324 — high value, the real map), relation (documents/IU/workflows/DOTs-by-topic PIV-325..328 — the drill edges to action). The headline is the topic axis, not the IU count.

Q2 — Which counts are meaningful vs low-value-but-tracked?

Meaningful: documents, topic axis, relation drills. Low value but tracked: raw IU count (kept as PIV-311, explicitly demoted from headline).

Q3 — How to represent business topics / cấp cao / con / cháu?

A topic = an axis node in taxonomy facet FAC-08 (live, active, 0 nodes today). Depth is dynamic via taxonomy.parent_id + universal_edges (broader/narrower/related, many-to-many). No topic_level_1/2/3. Layer 1 = approved active roots; Layer N = children by relation.

Q4 — Can current substrate handle this, or new collections?

~85% reuse. Node store, hierarchy, relations, confidence assignment, lifecycle, ownership, birth, pivot engine, documents — all live. Only 2 new objects needed: axis_registry (M-DEF-9, the missing governed registry) + generic axis_assignment. No "topic" island table. Reuse-sufficiency proven (6 of 7 axis components already in PG).

Q5 — How do new axes auto-scale without hardcoding each axis?

Via axis_registry: a new axis is a row declaring its node_source/relation_source/root_rule/child_rule/lifecycle/owner/pivots/resolver. The pivot engine already reads FROM any declared source; the coverage scanner detects unregistered axes like orphans. Topic is the pilot, not a coded special case.

Q6 — What pivots/registries for topic layers?

PIV-310 (documents) + PIV-320..332 (topic axis: roots, nodes, candidates, relations, by-lifecycle, docs-by-topic, IU-by-topic, workflows-by-topic, DOTs/Agents/events-by-topic, orphan topics, phantom relations, needs-grouping, governance-gap). All slot into the live pivot_definitions engine; honest 0/small counts where data is sparse.

Q7 — How does a topic layer drill to documents/pieces/workflows/DOTs/events/governance?

A fn_topic_node_substrate(topic_code) resolver (design, analogous to live fn_registries_pivot_node_substrate) assembles the node's real substrate: documents, IUs, workflows, DOTs/Agents/events, governance owner/status, birth record, lifecycle state.

Q8 — What must be added to the UI/API contract?

A graph-aware companion surface v_registries_pivot_axis_surface (the tree surface is DAG-unsafe). 7 net-new fields: axis_code, parent_codes[], has_multiple_parents, path/breadcrumb, relation_type, lifecycle_status, governance_status. New endpoints: /axes, /axis/{code}/rows, /axis-node/{code}. UI must not assume a tree, must not hardcode levels, must not compute counts in Nuxt. Authored as an unapplied apply-packet.

Q9 — Next implementation macro?

TOPIC_AXIS_RATIFY_AND_PILOT_POPULATE (owner ratifies axis law + AX-TOPIC; COUNCIL approves root topics; reconcile 7 tags → candidates; apply packet; assign ownership) → then RP_UI_CONSUME_AXIS_SURFACE → TOPIC_AXIS_EDGE_POPULATION_AND_AUTOMATION.

Headline findings (live evidence)

1. The topic axis is defined but empty: FAC-08 active, 0 nodes; a parallel ungoverned flat topic vocab is live (iu_metadata_tag topic:*, 7 keys / 25 assignments / 16 of 219 IUs). Reconcile, don't bless.
2. Governance substrate the 2026-06-01 docs called "unbuilt" is live (governance_object_ownership, governance_responsibility_scope, universal_edges). Ownership can be bound relationally now.
3. The only true missing substrate is axis_registry (+ axis_assignment). Two additive, owner-gated objects.
4. The RP surface is tree-shaped; topics are a DAG → companion surface required.
5. IU is still an island (0 approval_requests ever reference IU; no owner) — topic governance must be stood up, not assumed.

Status

PARTIAL — all design + recovery complete; live implementation owner/operator-gated by design. Live mutation = NO. No forbidden action taken. Counting is not faked; near-empty reality reported honestly.