From e40bd56dfdd5a58b850fc005127b62c2fd57d94c Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Sun, 16 Aug 2026 12:33:12 -0700 Subject: [PATCH] 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. --- VISION.md | 1 - 1 file changed, 1 deletion(-) diff --git a/VISION.md b/VISION.md index 752f71a1cc19..890075593f71 100644 --- a/VISION.md +++ b/VISION.md @@ -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.