03 — Trigger Axis Audit (Terminal 2) 2026-06-04

Live evidence (read-only)

Source: v_ax_trigger_canon_gate_summary, v_trigger_universe_census (grouped), v_rp_trigger_visibility_gap, axis_registry, v_ax_process_trigger_crosscheck.

Canon-gate summary

Metric	Live	Status
trigger_universe_db	525	OPERATIONAL
trigger_universe_host	77	ADAPTER_PENDING (crontab49/cron.d6/systemd-app4/OS18)
triggers_enabled	476	OPERATIONAL
process_relevant_classes	6	OWNER_GATED
process_relevant_triggers	117	OWNER_GATED
officially_owned	0 / 117	BLOCKED_OWNER
stale_disabled	27	OWNER_REVIEW
unclassified	8	TRIAGE
AX-TRIGGER in axis_registry	0 (absent)	BLOCKED_OWNER
canon_gate_verdict	TRIGGER_CANON_BLOCKED_OWNER_ONLY	BLOCKED_OWNER

Independent census recomputation (v_trigger_universe_census GROUP BY source)

source	triggers	enabled
pg_trigger	408	381
event_type_registry	52	30
dot_tools	57	57
job_queue	8	8
DB total	525	476

Cross-axis class breakdown (v_ax_process_trigger_crosscheck): db_dml 408 (INFRA_NO_PROCESS) + event_type 52 + dot_cron 42 + job_queue 8 + dot_dual 6 + dot_event 5 + dot_on-deploy 4 = 525. Process-relevant = 525 − 408 = 117. All officially_owned = 0. Independently reproduces Terminal 1.

Challenge checks

• Is AX-TRIGGER faked into the registry? No. axis_registry contains exactly 2 rows (AX-PROCESS, AX-TOPIC), both CANDIDATE. AX-TRIGGER is absent — axis_registry_row = 0.
• Are triggers falsely marked RP-visible? No. v_rp_trigger_visibility_gap reports every class NOT_VISIBLE_IN_ANY_RP_AXIS — RP-visible triggers = 0 until canon. Trigger-owner gap = 117.
• Do the trigger views exist? Yes — 7+ live views: v_trigger_universe_census, v_ax_trigger_surface, v_ax_trigger_canon_gate_summary, v_ax_trigger_owner_gate, v_rp_trigger_visibility_gap, v_trigger_process_relation_candidates, v_trigger_orphan_stale_detector.

Verdict

TRIGGER AXIS — CORROBORATED. Census 525 DB + 77 host, 117 process-relevant, 0 owned, AX-TRIGGER NOT canonized (not faked). Status = BLOCKED_AUTHORITY / TRIGGER_CANON_BLOCKED_OWNER_ONLY. Matches Terminal 1.