02 — Process Axis Audit (Terminal 2) 2026-06-04

Live evidence (read-only)

Source: v_ax_process_rp_visibility_after_candidate_stage, axis_assignment, axis_registry, v_process_discovery_verified_candidates_v3, v_workflow_residual_evidence_hardening_v4.

Metric	Live	Note
universe_total_entrypoints	453	373 DB defs + 80 host-unmanaged
db_managed_definitions	373	AX-PROCESS official RP owner-gated
official_ax_process_rp_assigned	0 / 453	NO axis_assignment written
axis_assignment rows	25 — ALL AX-TOPIC, ZERO AX-PROCESS	confirms no fake official RP
AX-PROCESS in axis_registry	status = CANDIDATE	not yet canon
host_orphan_objects_triaged	143 / 143	every orphan dispositioned
host_candidate_visible	69 / 143	mapped to candidate/component
host_not_process	40 / 143	explicitly not a process
host_owner_gated	11 / 143	docker runtime — owner decides
host_needs_review	23 / 143	reconcile / evidence needed
candidate_clusters_populated	17 / 143	anti-explosion
new_process_candidates	6 / 19	genuinely new managed-process candidates
residual (v_workflow_residual_evidence_hardening_v4)	23 rows	overlaps host_needs_review
job:cut verified	verified_candidate, 8 members, VERIFIED_PENDING_OWNER, owner_missing=true, real_run 0	sole verified candidate

Challenge checks

• Is official RP faked? No. axis_assignment GROUP BY axis_code returns ONLY AX-TOPIC=25. There is zero AX-PROCESS assignment. Official AX-PROCESS RP = 0/453 is genuine, not hidden.
• Is AX-PROCESS quietly canonized? No. axis_registry row for AX-PROCESS is CANDIDATE.
• Is job:cut overstated? No. It is the sole row in verified_candidates_v3, gated VERIFIED_PENDING_OWNER with owner_missing=true and 0 real runs — READY_OWNER, not done.

Verdict

PROCESS AXIS — CORROBORATED. Engineering surfaces complete and honest; official RP 0/453 is real (no fake assignment, no fake canon). Status = BLOCKED_OWNER / CANON_BLOCKED_OWNER_ONLY. Matches Terminal 1.