05 — Topic Axis Pivots PIV-310 / PIV-320..332 (Workstream D)

Status: LIVE as computable view (v_axis_topic_pivots); canon birth = operator-gated packet

The pivot map is exposed live and honestly through the read-only view v_axis_topic_pivots — no canon pivot_definitions rows were birthed over unapproved topics (forbidden). The view computes each count from live substrate and labels its classification. Canon insert SQL is in the operator packet (doc 02 step 5) for the day the owner wants them in pivot_definitions.

The live numbers (from v_axis_topic_pivots, 2026-06-04)

Pivot	Name	Count	Classification
PIV-310	Documents — Total	5,723	FINAL_COMPUTABLE
PIV-320	Approved root topics	0	NEEDS_GOV_COUNCIL_APPROVAL
PIV-321	Topic nodes — Total (incl candidates)	7	CANDIDATE
PIV-322	Topic candidates	7	CANDIDATE
PIV-323	Topic relations (edges)	0	CANDIDATE
PIV-324	Topics by lifecycle (candidate)	7	CANDIDATE
PIV-325	Documents by topic (assignments)	0	CANDIDATE
PIV-326	Information pieces by topic (assignments)	25	CANDIDATE
PIV-327	Workflows by topic	0	DEFER_NO_SOURCE
PIV-328	DOTs/Agents by topic	0	DEFER_NO_SOURCE
PIV-329	Orphan topics (no parent, not approved)	7	CANDIDATE
PIV-330	Phantom topic relations	0	NEEDS_LAW_DEFINITION
PIV-331	Topics needing grouping	0	CANDIDATE
PIV-332	Topic governance gap (candidate, unowned)	7	CANDIDATE

Classification logic (honest, no faked counts)

• FINAL_COMPUTABLE — source already governed (documents). Safe to birth canon now.
• CANDIDATE — count is real but derived from candidate substrate; will move to FINAL after ratification. PIV-326 = 25 equals exactly the reconciled assignments; PIV-321/322/329/332 = 7 equals the distinct candidate nodes (all currently orphan + unowned, hence equal — an honest signal, not a coincidence to hide).
• NEEDS_GOV_COUNCIL_APPROVAL — PIV-320 approved roots = 0 because no FAC-08 node is approved yet.
• NEEDS_LAW_DEFINITION — PIV-330 phantom topic relations: the law for what counts as a phantom topic edge is not yet defined; reported as 0, flagged, not invented.
• DEFER_NO_SOURCE — PIV-327/328: workflow/DOT→topic assignment rows do not exist yet (the 4-Mothers bridge, doc 08, creates them); reported 0 with the reason, not silently dropped.

Engine compatibility

Each pivot is engine-shaped (source_object + filter/group/metric jsonb). Canon inserts in the packet target governed sources: knowledge_documents (PIV-310), v_registries_pivot_axis_surface (PIV-321), axis_assignment grouped by node_code (PIV-326). Birthing them fires the count-refresh side-effect documented in prior RP macros — hence operator-gated.

Why not insert canon now

Forbidden: no final pivots over unapproved topics; no birthing unratified law as final. The computable view satisfies "pivots live or apply-ready" without crossing that line: numbers are visible today; canon law waits for approval.