项目文件夹

文件
Codex 866cb62f2d
Harness (E2E) / Harnesses (mock LLM) (push) Has been cancelled
Harness (E2E) / Provider harnesses (live LLM conformance) (push) Has been cancelled
Lint / golangci-lint (push) Has been cancelled
Run Tests / Unit Tests (push) Has been cancelled
Run Tests / Etcd Integration Tests (push) Has been cancelled
Update architect priorities for DX gaps
2026-06-28 19:35:18 +00:00

2.2 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.

Developer experience (ranked)

  1. CI-verify the deploy inner-loop contract (#3283) — the roadmap's hardening and agentic-depth items have shipped, so the highest-value remaining seam is the last step of the promised CLI lifecycle: scaffold → run → chat → inspect → deploy. micro deploy exists, but the 0→hero guard currently checks run/chat/flow and inspect boundaries, not the deploy handoff; a hermetic deploy contract keeps the operational harness story cohesive without needing a real remote host.
  2. Maintain a real-world 0-to-hero reference example (#3284) — after the deploy boundary is guarded, the next developer-experience gap is a living example that proves services, agents, flows, and interop compose into an actual system. This should double as documentation and CI smoke coverage so the lived story stays aligned with the README, website, and blog canon.

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