07 — End-to-End Proof Package (Workstream F)

A usable path from live data → topic node → substrate → evidence → decision queue → future automation route. All values below are from production on 2026-06-04.

1. Axis list

SELECT axis_code, status FROM axis_registry → AX-TOPIC | CANDIDATE. Appears in /api/axes sample (doc 02).

2. Candidate topic list (7 nodes)

v_registries_pivot_axis_surface → knowledge_graph(10), architecture(5), governance(3), dot_trigger(3), workflow(2), cut_pipeline(1), render_pipeline(1). All UNGOVERNED_CANDIDATE, flags {CANDIDATE_NODE, ORPHAN_TOPIC_NODE}.

3. Candidate topic substrate — knowledge_graph

fn_topic_node_substrate('TOPIC-CAND:knowledge_graph') returned (live):

• information_unit_count: 10; information_units: 10 uuids (09682146…, 10649925…, 3676cc0c…, 57553011…, 620f7646…, a448e397…, a7bba115…, c96b53fd…, e97fc334…, f1273184…).
• evidence_tags: 10 iu_metadata_tag:<uuid> (full provenance to source tags).
• taxonomy_node: null, birth_record: null, governance_owner: null (proves: ungoverned, no birth, no owner — correct).
• documents/workflows/dots_agents_events: empty (bridge not yet populated).
• parent_codes: [] (no edges yet).

4. Decision queue (recommended action)

v_axis_topic_decision_queue row for knowledge_graph → evidence_strength=STRONG, review_bucket=LIKELY_ROOT, proposed_classification=ROOT_CANDIDATE, proposed_lifecycle_action=PROPOSE_PROMOTE_TO_ROOT, gov_council_decision_needed=true, approval_ref=null. Sibling-suspect example: cut_pipeline/render_pipeline → duplicate_synonym_suspicion=POSSIBLE_SIBLING_GROUP:pipeline, PROPOSE_GROUP_UNDER_SHARED_PARENT.

5. Automation bridge (proposed routing for the same node)

Once promoted (LBL-NNN): add axis_assignment rows KG→document_template(selects), KG→workflow(routes_to); file approval_requests(improvement). PIV-327/328 then compute; resolver arrays populate. (Owner-gated; doc 06.)

6. UI render contract (how the frontend should display knowledge_graph)

• Candidate badge: "CANDIDATE" + "UNGOVERNED" (from lifecycle_status / governance_status).
• Evidence count: "10 information pieces" (count_value / iu_count).
• Strength chip: STRONG (green).
• Review action button: "Propose as root → GOV-COUNCIL" (from proposed_lifecycle_action; drafts an approval_requests row, owner approves).
• Substrate panel: lists 10 IUs + 10 evidence tags; "no documents/workflows yet" empty states.
• Multi-parent warning: none today (has_multiple_parents=false); the renderer must support it (array parent_codes) for when edges land.
• Sibling warning (cut_pipeline/render_pipeline): "Possible sibling group: pipeline — consider grouping".

Proof conclusion

The chain live data → node → substrate → evidence → decision → (proposed) route → UI is demonstrable end-to-end today with real production values. The only steps not live are the owner-gated mutations (promotion, routing rows, activation), which are packaged in docs 04–06.