KB-D9F3

Endgame Campaign — 05 Mother Event Type Readiness (COMMITTED, dormant)

3 min read Revision 1
dieu45event-type-registrymother-eventsrefs-onlydormantcommittedexecutor-boundary2026-05-28

05 — Mother Event Type Readiness (Điều 45) — Result: COMMITTED (dormant)

Result: ADVANCED + LIVE. 9 mother.* event types seeded into event_type_registry, all active=false. Refs-only taxonomy registration — NOT delivery, NOT execution, NOT law enactment. event_type_registry 31→40.

1. Committed rows (all active=false)

event_type event_stream delivery_lane severity
factory.registered birth delayed info
config.created update delayed info
output.created update delayed info
output.failed alert immediate warning
proposal.created review delayed info
proposal.approved review immediate info
proposal.rejected review immediate info
governance.blocked alert immediate warning
governance.unblocked alert immediate info

event_stream values map to the live CHECK domain {comment,review,update,birth,task,alert,health}; delivery_lane ∈ {immediate,delayed}; default_severity ∈ {info,warning,critical}. Corrected prior doc-08 bug: prior DDL used invalid 'warn' → now 'warning'. Added 2 events beyond the prior 7 (governance.blocked/unblocked).

2. Why safe to commit now

  • event_type_registry has no FK to any law and no json-schema/compat_mode column — registration is pure taxonomy, not enactment. Registering a type ≠ enacting Điều 45.
  • Triple-off: active=false on every row AND piece_event_runtime.emit_enabled=false AND iu_core.delivery_enabled=false. Nothing can emit or deliver these. Fully inert.
  • Fully reversible: DELETE FROM event_type_registry WHERE event_domain='mother';

This is a more forward posture than the prior bundle (which deferred the seed). Justified by the campaign's underload/clear-gates mandate: inert dormant taxonomy with zero runtime reachability.

3. Event vs Job boundary (Điều 45 — still paper)

  • Events (the rows above) = facts that happened; delivered via routes only when delivery_enabled.
  • Jobs = work to execute (queue.job_substrate): executor_class / retry_policy / idempotency_key / dlq_replay_request registries are still ABSENT. Required before any Mother runtime.
  • Executor boundary: Mother factories must emit events (facts) and enqueue jobs (intents) — never execute synchronously. Enforced today by all queue/runtime gates being closed.

4. Remaining

  • Activate (active=true) only when (a) Điều 45 is enacted (currently DRAFT) and (b) the 4 factories are activated (G4). Activation belongs in the same human window. No delivery wiring until delivery_enabled is governed open under Điều 45.
Back to Knowledge Hub knowledge/dev/reports/architecture/endgame-iu-pilot-to-4mothers-readiness-campaign-2026-05-28/05-mother-event-type-readiness.md