Process × Trigger Cross-Check Guide

2026-06-04. How the two axes relate and where the gaps are.

The relationship

Every governed process should have a known activation source (a trigger), and every process-relevant trigger should map to a governed process. Today neither side is owned, so the cross-check surfaces gaps, not violations.

Cross-axis surfaces (new this run)

• v_ax_process_trigger_drilldown — process → its triggers (12/19 candidates have triggers).
• v_ax_trigger_process_drilldown — trigger → its process (69 MANY_TRIGGER_ONE_PROCESS).
• v_rp_process_trigger_cross_axis_surface — unified feed (PROCESS 19/69 linked; TRIGGER_CLASS 7/525).
• v_rp_process_trigger_action_items — the gap list.

The 7 cross-axis dimensions and current counts

dimension	count	gate
process → triggers	12 candidates linked	—
trigger → processes	69 relations	—
process missing trigger	7	SAFE_REVIEW
trigger missing process	381	OWNER_GATED_LOW
high-risk trigger affecting process	381 (audit)	OWNER_GATED
trigger/process ownership gap	117 + 19	OWNER_GATED
trigger/process stale relation	27	OWNER_GATED

How to read it

Start from v_rp_process_trigger_action_items (sorted by qty). The big number (381) is infra DB triggers — low priority, classify in bulk. The high-value work is the 117 process-relevant triggers and the 19 unowned process candidates — both unblock the moment owners are assigned.