Trigger Axis (AX-TRIGGER) — Final Operating Manual

What it is

AX-TRIGGER is the governance axis over what fires processes: DB triggers, dot crons, event types, job queue entries, and host schedulers. It is not yet in axis_registry (correctly — no owner, no canon). Engineering surfaces are complete and read-only.

Current operating state (2026-06-05)

• Trigger universe: 525 DB (476 enabled) + 77 host (crontab 49 / cron.d 6 / systemd-app 4 / OS 18).
• Process-relevant triggers: 117, officially owned: 0.
• Stale-disabled: 27 (retire) · unclassified: 8 (triage).
• Verdict: TRIGGER_CANON_BLOCKED_OWNER_ONLY.

Trigger classes

class	n	relevance
db_dml_trigger	408	INFRA_NO_PROCESS (review-only)
dot_cron	42	PROCESS_RELEVANT
event_type	52	PROCESS_RELEVANT
job_queue	8	PROCESS_RELEVANT
dot_dual / dot_event / dot_on-deploy	6 / 5 / 4	PROCESS_RELEVANT

Key surfaces (read-only, live)

• v_trigger_universe_census · v_ax_trigger_canon_gate_summary · v_ax_trigger_canon_prep_spec · v_ax_trigger_owner_gate · v_ax_trigger_surface · v_rp_trigger_visibility_gap · v_ax_process_trigger_crosscheck.

Canon path (after owner)

See playbook 07: assign AX-TRIGGER owner (Dieu-39) → insert axis_registry row → map 117 process-relevant triggers to wf_process_candidate → triage 8 / retire 27 → RP visibility.

What operators must NOT do

Do not insert AX-TRIGGER into axis_registry without owner + president canon. Do not force db_dml triggers (408) into processes — they are infrastructure, review-only.