11 · process.* Event Activation Packet (2026-06-05)

7 process.* event types exist in event_type_registry, all active=false (0/7). Activation is carried by PROC-OWN-05 (event_activation, handler fn_pa_handler_activate_event_type, BLOCKED_NO_PRESIDENT_VOTE, needs axis owner first).

The 7 event types (live, all inactive)

1. process.run.started
2. process.step.started
3. process.step.completed
4. process.run.completed
5. process.run.failed
6. process.correlation.missing
7. process.evidence.missing

Exact activation order

(precondition) PROC-OWN-01 + PROC-OWN-02 (axis owner + ACTIVE) + ≥1 official process (PROC-OWN-03 job:cut)
PROC-OWN-05 approve ->
  1. process.run.started      (entry)
  2. process.step.started
  3. process.step.completed
  4. process.run.completed     (happy path closure)
  5. process.run.failed        (failure closure)
  6. process.correlation.missing  (guard)
  7. process.evidence.missing     (guard)

Guards (6,7) activate last so they don't fire before lifecycle events exist.

Payload contract

Each event payload: {process_code, run_id, correlation_id, step_code?, evidence_ref?, ts}. Emitted only when piece_event_runtime.emit_enabled=true (currently false) AND the event type active=true. Double-gated.

Dependency on first official process

Events are meaningless without a process to emit them. Activation requires ≥1 official process (job:cut) first. Until then, packet only.

Rollback

Set each event_type_registry.active=false; set emit_enabled=false. Fully reversible (no births; event types pre-exist).

Performed this run

None — packet only. emit_enabled=false; 0/7 active.

Faked: NONE.