09 — Next Macro Decision (Workstream H)

Decision rule applied

• "if no runner exists, choose wrapper implementation."
• "if wrapper is staged and fixture ready, choose true dry-run one pair."

The observation/correlation half of the wrapper is now LIVE and proven. The blocking gap is the DOT runner (the component that performs the agent_api call in an asserted plan/verify-only, no-mutation mode) and a fixture. Neither exists. So per the rule, the true-dry-run macro cannot run yet.

Chosen next macro: #2 DOT_EXECUTION_WRAPPER_IMPLEMENTATION

(specifically: the DOT-invoking runner + plan/verify-only mode + KG fixture)

Scope

1. Build a runner that invokes DOT_KG_EXPLAIN via agent_api in an asserted plan/verify-only mode (no universal_edges/KG write), gated by process_dot_runtime.execute_enabled (flip to true only under owner/operator control) and fn_assert_safe_for_dot_action().
2. Wire the fixture from doc 05 (input + expected output, output routed to temp namespace/evidence_ref).
3. On a successful no-mutation plan-mode run, call the LIVE fn_process_run_observe/fn_process_component_observe with evidence_type='DRY_RUN', source_system='dot_exec_wrapper', correlation prefix DRYRUN:.
4. Prove KG edges + birth_registry unchanged; define cleanup.

Then → #1 DOT_KG_TRUE_DRY_RUN_ONE_PAIR

Once the runner + fixture exist, the doc-05 package runs unchanged to produce the first true DRY_RUN observation → dot:kg advances simulated_observed → dry_run_observed (still NOT verified).

Parallel tracks (non-blocking)

• #3 PROCESS_DISCOVERY_WRAPPER_UI_DEPLOY — deploy the 3 routes over v_process_dot_wrapper_status (operator-gated Nuxt rebuild).
• #4 DOT_KG_OWNER_AND_EVENT_ACTIVATION_PREP — owner registration for dot:kg + process.* activation packet (doc 06).

NOT chosen

Approval-only macros excluded by rule. #5 PROCESS_REGISTRATION_CANDIDATE_PREP_FOR_JOB_CUT deferred — job:cut is already the lone verified candidate; its blocker is owner birth admission, not engineering.