10 — process.* Event Activation Package (2026-06-04)

Confirmed live

event_type_registry process.* events = 7 total / 0 active: process.correlation.missing, process.evidence.missing, process.run.completed, process.run.failed, process.run.started, process.step.completed, process.step.started — all active=false.

Activation order

1. process.run.started → 2. process.step.started → 3. process.step.completed → 4. process.run.completed → 5. process.run.failed → 6. process.evidence.missing → 7. process.correlation.missing. (lifecycle events first, then exception/observability events.)

Relation to first official process

Activate after job:cut is official (PROC-OWN-03) so the first emitted events correspond to a real owned process — avoids orphan events with no official process subject.

Payload contract

Each event payload: {process_definition_code, process_run_id, correlation_id, step?, evidence_ref, status, ts}. Sourced from process_run_observation / process_component_observation.

Activation / rollback

• Activate: PROC-OWN-05 → UPDATE event_type_registry SET active=true WHERE event_type LIKE 'process.%' (7 rows).
• Rollback: UPDATE … SET active=false — fully reversible (events are not births).

Status

BLOCKED_AUTHORITY — activation path exact; requires president vote (PROC-OWN-05) after axis canon. No event activated.