KB-11F8

13 — Next Macro Decision

2 min read Revision 1
dot-agent-apinext-macro2026-06-04

13 — Next Macro Decision (Workstream L)

Decision rule applied

Contract + dispatcher are staged and LIVE, but no agent_api endpoint exists → the rule "if dispatcher/contract staged but no endpoint, choose endpoint implementation" applies directly.

PRIMARY next macro

DOT_AGENT_API_PLAN_ONLY_ENDPOINT_IMPLEMENTATION — build the one missing piece: a real no-mutation agent_api invocation endpoint for DOT_KG_EXPLAIN(+_VERIFY) that consumes FIXTURE:dot:kg:explain:v1, writes only to DRYRUN-NS:dot:kg:explain, returns a verifier-checkable structured output, and is bound as dot_agent_api_contract.endpoint_ref. On success, flip the contract mode to DRY_RUN; then DOT_KG_TRUE_DRY_RUN_ONE_PAIR becomes a one-command run.

PARALLEL macros (no endpoint dependency)

  • PROCESS_DISCOVERY_V5_UI_DEPLOY — operator-gated Nuxt deploy of the 5 /process-discovery/* routes.
  • JOB_CUT_PROCESS_REGISTRATION_CANDIDATE_PREP — owner assignment → birth admission for the only verified candidate.
  • INFORMATION_PIECE_D1_D2_EXPANSION_ON_KG_DOT — content side; runner-free.

Not chosen

  • DOT_KG_TRUE_DRY_RUN_ONE_PAIR — blocked until endpoint exists.
  • Any tiny approval-only macro — excluded by macro rules.

The next macro can proceed with zero rediscovery: contract schema, dispatcher signature, fixture, and the exact endpoint contract are all recorded here.

Back to Knowledge Hub knowledge/dev/reports/architecture/dot-agent-api-contract-dispatcher-dryrun-ui-registration-2026-06-04/13-next-macro-decision.md