09 — Next Macro Decision (Workstream H)

Decision rule application

Macro §11: "if observation substrate applied and simulated path works but true dry-run not ready → choose wrapper patch."

• Substrate applied: yes.
• Simulated path works: yes (doc 03).
• True dry-run ready: no — WRAPPER_NEEDED (doc 04: no DOT runner, no plan mode, no fixture). → Choose the wrapper patch.

Primary next macro: DOT_EXECUTION_WRAPPER_CORRELATION_PATCH (option 5)

Build the safe DOT execution wrapper that the DOT_KG_EXPLAIN pair needs:

1. Mint process_run_id + correlation_id; write process_run_observation header (evidence_type=DRY_RUN, source_system=dot_runtime, status=started).
2. For producer then verifier: write process_component_observation rows; invoke the DOT in an asserted plan/verify-only mode (abort if any command would write KG/business data); capture input/output/evidence refs.
3. Emit process.* events carrying the correlation_id (may stay draft until activation).
4. Guarantee birth_registry + KG edges unchanged; route output to a temp/test namespace; verify cleanup.
5. On success, the pair becomes dry_run_observed (still NOT verified — a DRY_RUN proves wiring, not the process). A subsequent REAL_RUN is what flips it to real_run_observed/verified_candidate.

Parallel (non-blocking) tracks

• PROCESS_DISCOVERY_V3_UI_DEPLOY (option 2) — operator deploys the doc-07 routes/badges so RP shows runtime status. Pure visibility; no engine.
• DOT_KG_OWNER_AND_EVENT_ACTIVATION_PREP (option 3) — register a KG owner (clears owner_missing) and scope-activate the 7 process.* events (clears event_missing). Owner-gated.
• PROCESS_REGISTRATION_CANDIDATE_PREP_FOR_JOB_CUT (option 4) — job:cut is already verified_candidate + correlation; only owner_missing blocks birth. Prep its registration packet.

Not chosen

• Option 1 (TRUE_DRY_RUN) — blocked: wrapper must exist first.
• Approval-only paths — forbidden by §11.

Exact blocker for full dot:kg verification

A REAL_RUN (or owner-approved DRY_RUN) of a KG pair logged with a shared process_run_id + process.* events activated + a registered KG owner + owner admission of process birth. No engineering blocker remains for the discovery/observation layer itself.