KB-658D

08 — Event Activation Packet

2 min read Revision 1

08 — Event Activation Packet

View: v_rp_event_activation_packet (over v_rp_event_emit_readiness).

The 7 process.* event types — all inactive

activation_order event_type active emit_enabled dry_run_only no_go_until_authority
1 process.correlation.missing false false true true
2 process.evidence.missing false false true true
3 process.run.completed false false true true
4 process.run.failed false false true true
5 process.run.started false false true true
6 process.step.completed false false true true
7 process.step.started false false true true

All have a defined payload contract in event_type_registry.

Activation path & order

  1. President approve-votes PROC-OWN-05 → handler fn_pa_handler_activate_event_type → UPDATE event_type_registry SET active=true (7 rows). Depends on PROC-OWN-02 (axis canon).
  2. Operator flips piece_event_runtime.emit_enabled = true (currently false; dry_run_only=true).

event_outbox implications

Once emit_enabled flips, event_outbox begins receiving process.* rows on the defined delivery lanes. Until then, the runtime is dry-run-only and emits nothing.

No-go & rollback

  • no_go: events activated while no_go_until_authority = true (i.e., before president vote + operator emit flip).
  • rollback: set active=false (7 rows) + emit_enabled=false → drains the outbox path. Fully reversible.

Dry-run / preview

The runtime is already in dry-run-only mode; the activation packet previews the exact 7-row UPDATE and the emit flip without performing either. Do not activate events.

Back to Knowledge Hub knowledge/dev/reports/architecture/rp-governance-birth-synthetic-axis-registration-final-readiness-2026-06-05/08-event-activation-packet.md