Trigger Axis (AX-TRIGGER) — Operating Manual

2026-06-04. Companion content. AX-TRIGGER is CANDIDATE (not yet in axis_registry).

What AX-TRIGGER is

The axis of activation sources — everything that fires work. It is the natural complement to AX-PROCESS (what runs) and is being prepared as a first-class managed axis.

Universe (live)

• 525 DB triggers (476 enabled): pg_trigger db_dml 408, event_type 52, dot_cron 42, job_queue 8, dot_dual 6, dot_event 5, dot_on-deploy 4.
• 77 host triggers (adapter-pending): crontab 49, cron.d 6, systemd-app 4, OS 18.
• 117 process-relevant across 6 classes, 0 officially owned. db_dml (408) = INFRA_NO_PROCESS.

Detector classes (v_trigger_orphan_stale_detector)

DB_TRIGGER_NO_PROCESS 381 · DOT_SCHEDULED_CHECK_OWNER 57 · EVENT_ACTIVE_CHECK_PROCESS 30 · STALE_DISABLED_DB_TRIGGER 27 · EVENT_INACTIVE 22 · UNCLASSIFIED 8.

Read-only surfaces (new this run)

• v_ax_trigger_canon_gate_summary — verdict TRIGGER_CANON_BLOCKED_OWNER_ONLY.
• v_ax_trigger_owner_gate — per-class owner action.
• v_trigger_remediation_queue — dispositions by detector status.
• v_trigger_process_relation_action_queue — confirm trigger→process relations.
• v_ax_trigger_canon_prep_spec — the axis_registry row an owner would create.

Canon path (owner/president; not faked)

TRIG-OWN-01 assign AX-TRIGGER owner → TRIG-OWN-02 INSERT axis_registry(AX-TRIGGER) → TRIG-OWN-03 confirm 69 trigger→process relations → TRIG-OWN-04 retire 27 stale-disabled triggers.

Risk note

381 enabled DB triggers fire on DML with no governed process owner. Low individual risk (infra), but the audit surface should be classified (CLASSIFY_INFRA_OR_PROMOTE).