07 — Process × Trigger Cross-Axis Operational Hardening (2026-06-04)

Cross-axis coverage (live, read-only)

Concern	View	Status
process → trigger	v_ax_process_trigger_crosscheck (7)	LIVE
trigger → process	v_trigger_process_relation_candidates	LIVE
missing trigger	v_rp_trigger_visibility_gap	LIVE
trigger missing process	v_trigger_orphan_stale_detector	LIVE
stale trigger	v_trigger_orphan_stale_detector	LIVE
high-risk trigger	birth-trigger flagging (fn_birth_registry_auto + guard)	LIVE
owner gap	117 process-relevant triggers, 0 owned	SURFACED

New artifact this run

v_total_final_acceptance_scorecard — single-pane, self-deriving scorecard (doc 13). Applied birth-free (births 1,174,050 before==after), dual-path readable. Rollback 99_rollback.sql.

Severity / action queue

Existing surfaces already provide universe→host→relation→orphan→gap layering. No additional canon needed; the cross-check is operationally usable today. Severity scoring is derivable from the orphan/stale + high-risk flags; left as read-only to avoid premature canon.

Status

DONE (engineering) — cross-check is operationally usable. RP-ready summary is the scorecard view. No canon written.