process.* Events Activation Guide

7 event types exist, all inactive (0/7). Double-gated: an event fires only when its event_type_registry.active=true AND piece_event_runtime.emit_enabled=true (currently false).

The 7 (activation order)

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.

Guards (6,7) last.

Preconditions

PROC-OWN-01 + 02 (axis owner + ACTIVE) + ≥1 official process (job:cut via PROC-OWN-03). Then PROC-OWN-05 → fn_pa_handler_activate_event_type.

Payload contract

{process_code, run_id, correlation_id, step_code?, evidence_ref?, ts}.

Verify

SELECT event_type, active FROM event_type_registry WHERE event_type LIKE 'process.%'; — expect 7/7 active after PROC-OWN-05.

Rollback

Set active=false per type; emit_enabled=false. No births involved.

Do NOT

Activate before an official process exists; set emit_enabled=true while types are inactive.