05 — AX-PROCESS Candidate Assignment Surface

Registries-Pivot can now list the full candidate universe under AX-PROCESS without any canon. Five RP-readable views were created (all CREATE OR REPLACE VIEW, no mutation):

view	purpose	rows
v_ax_process_candidate_universe	candidate list w/ full attributes	19
v_ax_process_candidate_assignment_surface	per-candidate AX-PROCESS assignment_state + official_axis_assignment=0	19
v_ax_process_rp_visibility_after_candidate_stage	entrypoint-level coverage math (long format)	10 metrics
v_ax_process_candidate_layer_nodes	RP node-contract shape (axis_code, node_id, node_kind=candidate, weight)	17
v_ax_process_candidate_substrate	object-level membership for drilldown	143

Assignment states distinguished (no fake canon)

assignment_surface.assignment_state maps rp_visibility →

• CANDIDATE (candidate-visible) · CANON (official — currently none) · OWNER_GATED (docker) · NOT_PROCESS (OS/noise/shared-lib) · NEEDS_REVIEW.

Crucially every row carries official_axis_assignment = 0: axis_assignment was NOT written. The 25 existing axis_assignment rows belong to other axes; AX-PROCESS official assignment remains 0. The candidate layer is a staging surface RP can render as "candidate" badges — it does not impersonate canon.

What RP gets

• A populated AX-PROCESS candidate node layer (17 nodes) it could previously not show (0 nodes).
• Drilldown to the 143 underlying objects.
• A clear visual distinction between candidate / owner-gated / not-process / needs-review / (future) official.