12 — Next Macro Decision (Workstream K)

Decision rule application

• "If true dry-run succeeds → owner/event/registration or UI deploy" — pilot dry-run did not succeed (blocked).
• "If runner staged but dry-run not run → true dry-run" — applies to job:cut (runner exists), but job:cut is already verified and KG is the macro's pilot.
• "If agent_api contract missing → choose plan-only contract implementation" — this is the binding blocker for the KG pilot. ✅ MATCH.

Primary next macro

DOT_AGENT_API_PLAN_ONLY_CONTRACT_IMPLEMENTATION — define and wire a no-mutation, plan/verify-only invocation contract for DOT_KG_EXPLAIN (+ _VERIFY): an entrypoint that takes FIXTURE:dot:kg:explain:v1, writes only to DRYRUN-NS:dot:kg:explain, returns a structured output the verifier checks. This converts the staged runner + fixture into a real DRY_RUN and produces the first DRY_RUN row in the system.

Parallel (owner/operator, no rediscovery needed)

1. DOT_KG_TRUE_DRY_RUN_ONE_PAIR — once the contract lands, run the fixture and upgrade the observation to DRY_RUN (exact command + fixture already staged). (Or demonstrate the pattern via job:cut's existing iu-cutter dry-run runner as the template.)
2. PROCESS_DISCOVERY_V4_UI_DEPLOY — operator Nuxt rebuild over the live v4 views (doc 09).
3. PROCESS_REGISTRATION_CANDIDATE_PREP_FOR_JOB_CUT — owner registration in governance_registry (Điều 37); job:cut is READY-PENDING-OWNER.

Not chosen

• Tiny approval-only macro — excluded by rule.
• INFORMATION_PIECE_D1_D2_EXPANSION — dry-run is progressable (contract is a concrete next step), so content-only fallback is unnecessary.

Next macro selected without rediscovery; all inputs (runner, fixture, v4 views, blocker) are live and pinned.