06 — Trigger Axis (AX-TRIGGER) & Cross-check

What was built (additive, birth-free, 1,174,004 == 1,174,004)

7 read-only views: v_trigger_universe_census, v_trigger_host_unmanaged_census, v_trigger_process_relation_candidates, v_trigger_orphan_stale_detector, v_ax_trigger_surface, v_ax_process_trigger_crosscheck, v_rp_trigger_visibility_gap. No tables, no triggers, no canon.

Trigger universe (live numbers)

DB-introspectable = 525 (476 enabled):

Class	Members	Enabled	Disabled
db_dml_trigger	408	381	27
event_type	52	30	22
dot_cron	42	42	0
job_queue	8	8	0
dot_dual	6	6	0
dot_event	5	5	0
dot_on-deploy	4	4	0

Host-unmanaged (not enumerable from PG, needs adapter) = 77 (crontab 49, /etc/cron.d 6, systemd app-timers 4, OS timers 18).

Cross-check findings (the point of the axis)

• total triggers: 525 DB + 77 host = 602
• mapped to process (process-relevant): 117 (dot/event/job) — but officially owned = 0
• no-process: 408 DB DML triggers (INFRA_NO_PROCESS) — the hidden activation layer
• multi-process: 0 one-trigger-many-process, 12 many-trigger-one-process (fan-in)
• stale/orphan: 27 disabled DB triggers
• owner-missing: all 525 (governance_object_ownership = 0)
• RP visibility: 0 (AX-TRIGGER is CANDIDATE, unregistered)

Status

Trigger axis design + first safe read-only surface = LIVE. No trigger canon/birth performed — canonising AX-TRIGGER follows the same owner gate as AX-PROCESS (future macro, needs authority). The UI overview endpoint already consumes v_ax_process_trigger_crosscheck (tolerant if absent).