04 — AX-TRIGGER Canon Prep & Cross-Check (PHASE D)

Status: COMPLETE to safe frontier. AX-TRIGGER is CANDIDATE/canon-ready with an exact owner gate. No axis_registry / ownership / approval inserts (owner+president authority). Birth-free (1,174,029 before==after apply).

Host-census reconciliation (Phase A note resolved)

v_trigger_host_unmanaged_census returns 4 rows that are a roll-up by host_source; their trigger_count sums to 77: host_crontab 49 + etc_cron_d 6 + systemd_app_timer 4 + systemd_os_timer 18. → "4 vs 77" is rows-vs-sum, not a discrepancy. Confirmed via the view definition.

Trigger universe (verified live)

• DB 525 (enabled 476): db_dml 408 (381 en/27 disabled), event_type 52 (30 en/22 disabled), dot_cron 42, job_queue 8, dot_dual 6, dot_event 5, dot_on-deploy 4.
• Host 77 (adapter-pending; not DB-enumerable).
• Process-relevant 117 across 6 classes, officially_owned 0. db_dml 408 = INFRA_NO_PROCESS.
• 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 (= 525).
• Relation candidates 69, all MANY_TRIGGER_ONE_PROCESS / ENTRYPOINT.

AX-TRIGGER axis state

axis_registry holds only AX-TOPIC and AX-PROCESS (both CANDIDATE). AX-TRIGGER has no registry row. Formal canon requires an owner/president-gated INSERT + ownership assignment — not faked.

New surfaces (birth-free, read-only; rollback 99_rollback.sql)

1. v_ax_trigger_canon_gate_summary — mirror of the process canon gate. Verdict TRIGGER_CANON_BLOCKED_OWNER_ONLY; officially_owned 0/117; axis_registry_row 0/1.
2. v_ax_trigger_owner_gate — per class: 6 process-relevant → ASSIGN_AX_TRIGGER_CLASS_OWNER; db_dml (408) → CLASSIFY_INFRA_OR_PROMOTE; all BLOCKED_NO_AX_TRIGGER_OWNER.
3. v_trigger_remediation_queue — by detector status (525 total): 381 CLASSIFY_INFRA_OR_PROMOTE (OWNER_GATED_LOW) · 57 ASSIGN_OWNER_AND_LINK_PROCESS_CANDIDATE · 30 MAP_ACTIVE_EVENT_TO_PROCESS · 27 REVIEW_FOR_RETIREMENT · 22 REVIEW_ACTIVATION_NEED (SAFE_REVIEW) · 8 TRIAGE_CLASSIFY (SAFE_TRIAGE).
4. v_trigger_process_relation_action_queue — per candidate process, trigger_count + CONFIRM_TRIGGER_PROCESS_RELATION (owner-gated), from the 69 MANY_TRIGGER_ONE_PROCESS relations.
5. v_ax_trigger_canon_prep_spec — the exact axis_registry row an owner would INSERT for AX-TRIGGER (domain trigger_activation; node_source = the two census views; relation_source = relation candidates; proposed_status CANDIDATE; canon_note: owner/president authority only).

Owner decision path (documented, not inserted)

TRIG-OWN-01 assign AX-TRIGGER owner → TRIG-OWN-02 INSERT axis_registry(AX-TRIGGER) status canon → TRIG-OWN-03 confirm trigger→process relations (69) → TRIG-OWN-04 retire stale-disabled (27). Analogous to PROC-OWN; modelled as views, no approval_requests rows created (each is an unretirable birth + owner authority).

Exact blocker

AX-TRIGGER owner assignment + president canon of the axis_registry row. No engineering blocker.