KB-5F31

IU Core Controlled Route — 04 Route + master-gate activation + disable runbook

3 min read Revision 1
dieu44iu-core-mvpcontrolled-routemaster-gatedry-rundisable-runbookv0.62026-05-21

IU Core Controlled Route — 04 Activation + disable runbook

Durable production mutations applied

  1. Outbound route enabled in dry-run live: UPDATE iu_outbound_route SET enabled=true, dry_run=true WHERE route_code='iu.version_applied.workflow'. The CHECK (enabled=false OR dry_run=true) is satisfied.
  2. Master gate opened: INSERT INTO dot_config (key,value,description) VALUES ('iu_core.routes_master_enabled','true', …)fn_iu_core_routes_enabled() now returns true.

The inbound route iu_sql.iu_sql_link.insert was deliberately left enabled=false, dry_run=true — the macro approved enabling the outbound route only. The inbound path was exercised solely in rolled-back probes.

Architecture note — what the dry-run flag does and does not gate

fn_iu_outbound_on_version / fn_iu_emit_event are gated only by the master gate + a registered event type. They do not consult iu_outbound_route — the route row is declarative metadata for a future route worker. So with the gate open, an organic unit_version insert (version_seq > 1) writes a real event_outbox row regardless of the route's dry_run flag. dry_run=true is the instruction a future route worker reads to decline downstream delivery. Writing to event_outbox is enqueueing, not delivery — and event_outbox has no consumer (doc 06), so no downstream delivery occurs.

The inbound path does honour dry_run: fn_iu_sql_link_inbound_capture writes iu_route_attempt with status='dry_run' vs 'pending' from the route row, into iu-core's own table.

Disable runbook — proven (doc 05, probes D + E)

Layer Action Effect Proven
L1 fastest UPDATE dot_config SET value='false' WHERE key='iu_core.routes_master_enabled' every iu-core trigger fn instantly no-ops Probe D
L2 UPDATE iu_outbound_route SET enabled=false … (per route_code) route declared disabled Probe E
L3 thorough runtime/rollback/030DROP TRIGGER trg_iu_out_version / trg_iu_sql_in_iu_sql_link nothing fires regardless of gate Probe E

DROP TRIGGER fires the log-only evt_trigger_guard_drop event trigger (emits [TRIGGER-GUARD] DROPPED WARNING, never raises) — confirmed.

End state

Gate open · outbound route enabled=true, dry_run=true · inbound route enabled=false, dry_run=true · triggers attached · 0 durable iu-core event/attempt rows.

Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/v0.6-iu-core-controlled-route-mastergate-structure-observability-open-goal/04-route-mastergate-activation-and-disable-runbook.md