You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We keep one issue per PR and avoid unrelated refactors.
We include tests/docs required by each issue acceptance signals.
We use squash merge and link each PR back to this tracking issue.
Suggested prompt:
"Implement EntityProcess/agentv issue #. First read CLAUDE.md in repo root. Create a feature branch, implement only this issue, add/update tests and docs, push, and open a PR that closes #. Keep changes scoped and avoid unrelated refactors."
SOURCE OF TRUTH FOR ORCHESTRATOR HANDOFF
This issue body is the canonical execution plan for this roadmap.
0) Execution Philosophy
1) Architecture Boundary
Core runtime (allowed/required)
Docs/examples only (non-core)
External-first (tooling/plugin/post-processing)
If we implement an external-first item inside
agentv, we keep it as optional utility/report tooling and avoid runtime/schema coupling.2) Current Implementation Status (snapshot)
3) Delivery Tracks
Track A: AgentV core/docs
Track B: External analytics/plugin
4) Dependency Graph
5) Parallel Waves (default)
Wave 1 (parallel)
Wave 2 (parallel, once Wave 1 PRs are open)
Wave 3
Wave 4
6) Merge Order (low-conflict default)
7) Subagent Contract
CLAUDE.mdinagentvfirst.main).Suggested prompt:
"Implement EntityProcess/agentv issue #. First read CLAUDE.md in repo root. Create a feature branch, implement only this issue, add/update tests and docs, push, and open a PR that closes #. Keep changes scoped and avoid unrelated refactors."
8) Completion Criteria