docs: remove agent-hierarchy guardrail from VISION roadmap

Agent-created agents (durable roster entries with provenance) are now
planned work, so the blanket VISION.md guardrail against agent-hierarchy
frameworks no longer reflects direction. The adjacent guardrail against
heavy duplicative orchestration layers stays.
This commit is contained in:
Peter Steinberger
2026-08-16 12:33:12 -07:00
parent 0d9b22ad2d
commit e40bd56dfd
-1
View File
@@ -131,7 +131,6 @@ It is widely known, fast to iterate in, and easy to read, modify, and extend.
- Commercial service integrations that do not clearly fit the model-provider category
- Wrapper channels around already supported channels without a clear capability or security gap
- MCP work that duplicates existing MCP, ACPX, plugin, or ClawHub paths without a clear product or security gap
- Agent-hierarchy frameworks (manager-of-managers / nested planner trees) as a default architecture
- Heavy orchestration layers that duplicate existing agent and tool infrastructure
This list is a roadmap guardrail, not a law of physics.