Priorities

The ranked work queue for the autonomous improvement loop. The architecture-review pass (the architect) owns this file: each run it turns the roadmap plus an internal scan (gaps in the services → agents → workflows lifecycle, API coherence, drift, tech debt, test and DX friction) into a single ordered list — highest-value first — and links each item to a tracking issue. The hourly continuous-improvement pass works the top item whose issue is still open. So the architect decides what, and the increment loop builds it.

Reading / editing. An item is done when its linked issue closes (the increment that builds it adds Closes #<issue>). Roadmap phase (Now → Next → Later) is the primary ordering; internal findings are interleaved by value, not kept in a separate list. The human can reorder this list — or the issues — at any time to redirect the loop; direction always wins.

Off-limits to the loop (the architect proposes these as notes, never as queue items the loop can auto-merge): brand/positioning copy, breaking public-API changes, architectural rewrites. Those go to the human.

Work queue (ranked)

1. Verify the install script and first-run CLI smoke path (#3630) — the CI-verified 0→hero reference app shipped, so the highest adoption gap moves earlier in the funnel: a new developer must be able to install the CLI, see the expected first-run commands, and trust that micro new, preflight, run/chat/inspect boundaries, and the no-secret on-ramp still work from a fresh binary. Keep this first because the current strategic goal is developer adoption, and install/first-run friction blocks every services → agents → workflows success story before the deeper harness can matter.
2. Make plan/delegate live-provider conformance avoid duplicate task side effects (#3626) — the latest live-provider scan found the atlascloud plan/delegate scenario creating duplicate tasks and missing the delegated notification. This is the highest open Now-phase trust gap because plan/delegate is the core bridge from agent reasoning to service side effects; developers cannot rely on the 0→hero lifecycle if a model can replay tool calls and leave the handoff pending.
3. Expose fallback_echo during A2A streaming fallback conformance (#3560) — this remains the next scoped Now-phase interop/conformance gap: it protects the A2A streaming promise developers see in the README and site by ensuring the non-native streaming fallback path still receives the tool surface, without letting protocol depth outrank the on-ramp or side-effect safety.
4. Propagate agent run cancellation and deadlines through model and tool calls (#3544) — the highest-value remaining Now-phase resilience gap is predictable failure semantics across agent runs, model calls, tool calls, plan/delegate, and flow handoffs. Tool retries and live-provider deadline tuning are in place; the lifecycle still needs cancellation/deadline propagation so work fails safely instead of becoming opaque loops.
5. Emit OpenTelemetry spans for agent run timelines (#3525) — recent work made runs inspectable, correlated trace metadata through scheduled dispatch, verified restart resume, added opt-in tool retries, hardened provider conformance, and fixed provider-emitted text tool calls. The next Next-phase step is to turn that RunInfo foundation into standard OTel spans for agent runs, model calls, tool calls, checkpoint/resume, cancellation/deadlines, and failures.
6. Add an AP2 mandate layer over A2A and x402 (#3552) — this is a forward interop investment, not a Now-phase blocker: Go Micro already has A2A agents and x402 paid tools, so a small signed-mandate foundation can keep agent payments aligned with the open-protocol story without pulling the queue away from adoption, resilience, or observability. Keep it additive and opt-in while the AP2/FIDO work settles.

Seeded by Claude Code from the roadmap + open issues; thereafter maintained by the architecture-review pass.