08 — AX-PROCESS Pivots & PIV-340..353

Live finding: PIV-340..353 do NOT exist as physical pivot_definitions rows.

pivot_definitions total = 39, max code = PIV-313, only 2 codes match ^PIV-3. There is no PIV-340..353 row. They are proposed/candidate pivots, defined in prior specs but never instantiated — correctly so, because instantiating a pivot under AX-PROCESS would imply the axis is canon (it is not).

Status: CANDIDATE / canon-gated. Display-ready as proposals only.

• They cannot become official pivot_definitions rows until AX-PROCESS axis is ratified (PROC-OWN-02).
• This is consistent with axis_registry.AX-PROCESS.status = CANDIDATE.

Layer mapping for display (each candidate maps to)

Dimension	Source
source class	wf_process_candidate_member.source_key (host_crontab / fs_dot_bin / fs_scripts / docker / kb)
process type	wf_process_candidate.process_type
evidence level	process_axis_ai_review.review_state (PASS / NEEDS_MORE_EVIDENCE) + v_workflow_residual_evidence_hardening_v3
owner status	wf_process_candidate.owner_status (all UNASSIGNED)
canon status	wf_process_candidate.canon_gate_status (CANDIDATE_STAGE)
remediation status	v_workflow_orphan_remediation_v2.residual_state

What is safe now

• Render PIV-340..353 as candidate pivots in the RP candidate-surface (v_ax_process_candidate_assignment_surface), clearly labelled candidate, never official.
• Do not insert them into pivot_definitions (that is canon, owner-gated).

RP candidate surface: display-ready. No new pivot rows written (correct — canon-gated).