10 — Next Macro Decision (Workstream I)

10.1 Decision rule (from the macro)

• if runtime observation substrate is ready/apply-ready → choose dry-run/apply;
• if inventory blind spot remains → choose inventory fix;
• if dry-run impossible → choose runtime observation apply first;
• do not choose approval-only.

10.2 State after this macro

• Inventory blind spot: fixed live (doc 03) → option 3 not needed.
• Runtime observation substrate: apply-ready, rehearsed birth-free (doc 04) → apply is the gating first step.
• Dry-run wrapper: designed (doc 06), needs the substrate applied + one KG pair chosen.

10.3 Chosen next macro

PROCESS_DISCOVERY_RUNTIME_OBSERVATION_APPLY_AND_DRY_RUN (option 1).

Scope:

1. Operator applies 02_observation_substrate.sql (the two ledger tables) — rehearsed birth-free, reversible.
2. Implement the DOT dry-run wrapper (doc 06 §6.3) for one KG producer/verifier pair.
3. Run it in plan/verify mode (no business mutation), writing observation rows with a shared correlation_id and emitting process.* events.
4. Watch v_process_discovery_correlation_gaps close and verified_candidates admit the pair (real run) — or record it as a dry-run wiring proof.

10.4 Why this and not the others

• Option 2 (DOT_KG dry-run with correlation) is a subset of option 1 but presumes the substrate is already applied — folding the apply step in (option 1) avoids a stall.
• Option 3 (inventory fix + UI deploy) — the inventory fix is already live; only the UI deploy remains, which is operator-gated and parallelisable, not the critical path.
• Option 4 (registration candidate prep) would be approval-only for KG (still runtime_missing); the decision rule forbids approval-only. job:cut is registration-ready, but registering it does not advance the binding constraint (DOT runtime).
• Option 5 (D1/D2 expansion) is content work, parallel, not the blocker.

10.5 Parallel (owner/operator, non-blocking)

• RP_UI_PROCESS_DISCOVERY_V2_DEPLOY (adopt *_v2 views + the 6 routes; operator Nuxt rebuild).
• DOT_KG_OWNER_REGISTRATION (register KG owner in governance_registry §37 — unblocks owner_missing).
• DOT_KG_PROCESS_REGISTRATION_CANDIDATE_PREP for job:cut (the one verified candidate) if the owner wants a first born process.