KB-1694

PD Full Operationalization — 06 AX-PROCESS Pivots/Canon

3 min read Revision 1

06 — AX-PROCESS Pivots / Canon Readiness (Workstream E)

Live state

axis_registry AX-PROCESS = CANDIDATE. v_axis_process_pivots exposes PIV-340..353, all classification=CANDIDATE:

  • PIV-340 Process/workflow objects — Total (governed) = 2
  • PIV-341 DOT-contained processes (Type 1) = 57
  • … through PIV-353 (job_queue / events / runs surfaces). Governance gap (v_axis_process_governance_gap): 4 OWNER_MISSING (AX-PROCESS, WF-001, WF-002, PIPELINE:cut), bootstrap_request_code=AXR-PROCESS-OWNER (a pending ownership_bootstrap/assign_axis_owner request already exists).

Decision: candidate surfaces stay; NO canon insert (owner-gated)

Canonizing PIV-340..353 means inserting pivot_definitions rows — each is an unretirable birth (≈14 births), plus auto-managed edges. Prior analysis: name-dependent birth amplification. Therefore no canon insert this run (forbidden: unsafe birth/canon, AX-PROCESS promotion). The candidate pivot view is already live and is the safe surface.

Candidate vs canon split

  • Candidate (live, safe): v_axis_process_pivots (PIV-340..353), v_axis_process_inventory_v2 (on-demand producers included, pair-grouped), v_axis_process_candidates, v_axis_process_governance_gap. These can be shown in the UI now with a CANDIDATE badge.
  • Canon (owner-gated): promote each PIV-3xx to a pivot_definitions row under parent. Requires owner ratify of the axis (Điều-XX) + GOV FAC roots.

Pivot parent_code plan

Parent = AX-PROCESS axis pivot root (sibling to AX-TOPIC's PIV-310 root). On canon: PIV-340 (total) is the root; PIV-341..353 are children (Type-1/Type-2/Type-3 + job_queue/events/runs surfaces). Code remap candidate→canon is a 1:1 relabel (no count change), same pattern as the AX-TOPIC TOPIC-CAND→LBL-NNN remap.

UI layer plan

Read-only /process-discovery/axis route over v_axis_process_pivots with CANDIDATE badges; no Nuxt math; flips to canon badges automatically once pivot_definitions exist (owner step).

Rollback caveat

Canon inserts are not retirable — that is exactly why this run stops at the live candidate surface. No fake canon.

Completion: Process Axis can be shown now (candidate) and canonized later by owner; no unsafe action taken.

Back to Knowledge Hub knowledge/dev/reports/architecture/process-discovery-full-operationalization-endpoint-dryrun-ui-registration-pivots-content-2026-06-04/06-ax-process-pivots-canon-readiness.md