AX-TRIGGER Canon Playbook

Goal: bring AX-TRIGGER into axis_registry and own the 117 process-relevant triggers — after a true owner/president (Dieu-39) decision.

Preconditions (live)

• AX-TRIGGER NOT in axis_registry (correct). 525 DB + 77 host triggers; 117 process-relevant; 0 owned.

Step-by-step

1. Assign AX-TRIGGER owner (governance, Dieu-39 ratification) → governance_object_ownership(AX-TRIGGER, <owner>).
2. Insert axis_registry row per v_ax_trigger_canon_prep_spec: node_source=trigger census; node_filter=db+host classes; relation_source=trigger→process candidate map; lifecycle_field=enabled; status=CANDIDATE.
3. President canon → status CANDIDATE→ACTIVE.
4. Map relations: 117 process-relevant triggers → wf_process_candidate. db_dml 408 stay INFRA_NO_PROCESS.
5. Owner queue (v_ax_trigger_owner_gate): own the 117; triage 8 unclassified; retire 27 stale-disabled.
6. Host adapters (engineering, not authority): finish crontab/cron.d/systemd/OS mapping for the 77 host triggers via the universal scanner (timer live, next 04:10).

Verification

SELECT * FROM v_ax_trigger_canon_gate_summary; — watch axis_registry_row (0→1) and canon_gate_verdict.

Do NOT

Fake an axis_registry row; force db_dml triggers into processes; retire triggers without owner review.