docs(priorities): refresh architect adoption queue

2026-07-01 21:41:39 +00:00
1 changed files with 1 additions and 1 deletions
@@ -21,7 +21,7 @@ changes, architectural rewrites. Those go to the human.

 ## Work queue (ranked)

-1. **Add a “Debugging your agent” guide focused on the dev workflow** ([#3564](https://github.com/micro/go-micro/issues/3564)) — the inner loop is scaffold → run → chat → inspect → deploy. Document how to see tool calls, run history, provider failures, guardrail refusals, and flow handoffs before adding more depth that users cannot diagnose.
+1. **Make the 0→hero path runnable from the docs** ([#3598](https://github.com/micro/go-micro/issues/3598)) — the debugging guide shipped, so the next highest adoption gap is wayfinding across install, first agent, examples, chat/inspect, and deploy dry-run. Keep this first because the current strategic goal is developer adoption: a new user should be able to walk scaffold → run → chat → inspect → deploy without guessing which guide comes next, and the docs should point at the CI-backed harness that proves it.
 2. **Finalize the universe notify step after an agent-backed timeout** ([#3589](https://github.com/micro/go-micro/issues/3589)) — recent live-provider CI exposed a real services → agents → workflows seam: an agent-backed notify side effect can complete while the client observes a timeout, leaving pending flow state and late duplicate notifications. Keep this high because it protects the 0→hero/reliability contract, but leave the adoption guide first so the queue does not drift back to only internal hardening.
 3. **Prevent duplicate tool side effects in the plan/delegate harness** ([#3559](https://github.com/micro/go-micro/issues/3559)) — correctness still matters where it protects real user trust. Plan/delegate is central to the services → agents lifecycle, and duplicate side effects undermine the “agent as dependable service” story.
 4. **Expose `fallback_echo` during A2A streaming fallback conformance** ([#3560](https://github.com/micro/go-micro/issues/3560)) — keep interop conformance trustworthy without letting it dominate the adoption queue. This is scoped, testable, and protects the A2A promise developers see in the README and site.