KB-18D8

07 Trigger Source Coverage

2 min read Revision 1

07 — Trigger Source Coverage (v_rp_trigger_source_coverage_v2)

11 trigger classes: 7 DB + 4 HOST. Universe = 525 DB triggers + 77 host triggers = 602. Every class reports rp_status = NOT_VISIBLE_IN_ANY_RP_AXIS because AX-TRIGGER is a CANDIDATE (unregistered). RP-visible triggers = 0 — and that zero is honest (see doc 12), not a coverage hole.

DB layer (525)

class triggers enabled ui_label
db_dml_trigger 408 381 DB_ONLY
event_type 52 30 EVENT_MIXED_ACTIVE_30_OF_52
dot_cron 42 42 DB_ONLY
job_queue 8 8 DB_ONLY
dot_dual 6 6 DB_ONLY
dot_event 5 5 DB_ONLY
dot_on-deploy 4 4 DB_ONLY

HOST layer (77)

class triggers ui_label
host_crontab 49 HOST_PARTIAL_NOT_ENUMERABLE_IN_DB
systemd_os_timer 18 HOST_PARTIAL_NOT_ENUMERABLE_IN_DB
etc_cron_d 6 HOST_PARTIAL_NOT_ENUMERABLE_IN_DB
systemd_app_timer 4 HOST_PARTIAL_NOT_ENUMERABLE_IN_DB

UI labels required

DB_ONLY (DB-enumerable, RP-invisible), EVENT_MIXED (active subset shown explicitly: 30 of 52), HOST_PARTIAL (host-only, not in DB universe). The UI must show "602 triggers exist; 0 RP-visible until AX-TRIGGER canon" — never "0 triggers".

Back to Knowledge Hub knowledge/dev/reports/architecture/rp-adapter-automation-reality-no-blind-spot-closeout-2026-06-05/07-trigger-source-coverage.md