Process × Trigger Cross-Check — Final Manual

Purpose

Surface where the two axes disagree: triggers with no governed process, processes with no trigger, ownerless objects on either side. The cross-check is the system's "nothing fires unaccounted for" guarantee.

Live cross-check (2026-06-05)

Source: v_ax_process_trigger_crosscheck (7 trigger classes) + v_process_trigger_actionability_ledger (severity-scored, 12 gaps).

gap	severity	count	owner
official RP missing	5	0/453	AX-PROCESS owner (president)
process-relevant triggers unowned	4	117	AX-TRIGGER owner
owner-gated runtime processes	4	11	AX-PROCESS owner
birth-ready candidates	3	6	AX-PROCESS owner + president
residual reconcile dot/bin	3	8	AX-PROCESS owner
job:cut ready	2	1	president (PROC-OWN-03)
db_dml infra triggers	2	408	review-only

How to use it

1. Sort the actionability ledger by severity desc.
2. Work top-down: official RP (needs president) → unowned triggers (needs AX-TRIGGER owner) → candidates/reconcile (owner drain).
3. Every row has recommended_owner + recommended_action. safe_now=false everywhere = each needs authority.

Guarantee

After both axes are owned and canon'd, the cross-check should show 0 unowned process-relevant triggers and every official process linked to its trigger(s). Today that target is owner-gated, not engineering-gated.