Codex
ca744ff7fd
2.6 KiB
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)
- Ensure AtlasCloud plan-delegate harness persists plan (#4665) — The zero-to-hero chat/inspect race is fixed, so the highest-value active gap is the live AtlasCloud plan/delegate conformance failure where the conductor completed side effects without persisting the built-in plan. Keep this first because plan/delegate is core to the services → agents → workflows story, and a red live harness weakens both developer trust and the roadmap's cross-provider hardening goal.
- Add scheduled cross-provider agent conformance (#4649) — Once the active AtlasCloud plan/delegate failure is closed, the Now roadmap still calls for battle-testing the same agent scenario across providers. Verify tool-calling, multi-step turns, plan/delegate, and guardrails on the live-provider matrix behind key-gated scheduled CI, without slowing the local harness.
- Harden agent provider failure resilience (#4650) — The next reliability seam is making timeouts, cancellation, rate limits, retry/backoff, and inspectable failure metadata predictable through the agent loop. Keep this scoped to existing behavior and tests; surface any breaking API or default changes as human review notes instead of queue work.
Seeded by Claude Code from the roadmap + open issues; thereafter maintained by the architecture-review pass.