micro--go-micro
Codex
b5025bf8e2
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
38 行
2.1 KiB
Markdown
38 行
2.1 KiB
Markdown
# 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](../../ROADMAP.md) 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.
|
|
|
|
## Now (ranked)
|
|
|
|
1. **Agent observability spans** (#3182) — export `RunInfo` as OpenTelemetry spans
|
|
for agent runs, model calls, tool calls, delegation, and failures. Roadmap →
|
|
*Next* agent observability; now the registry readiness gap (#2956), durable
|
|
resume, streaming, and provider conformance work have shipped, the biggest
|
|
remaining seam is production inspectability across the services → agents →
|
|
workflows runtime.
|
|
2. **Execution lifecycle hooks & metadata** (#2980) — before/after-tool, retry,
|
|
and failure hooks; first check overlap with the shipped run-timeline /
|
|
OpenTelemetry work and scope to what's not already covered. Roadmap → *Next*
|
|
resilience/operability, but ranked after observability so new hooks attach to
|
|
the same run story instead of creating another seam.
|
|
|
|
_Seeded by Claude Code from the roadmap + open issues; thereafter maintained by the
|
|
architecture-review pass._
|