Unverified50% confidenceDecision RuleExact time
Atomic Agent's current rule: no change operations may be executed during the planner's entire turn, all MCP tools are treated as change operations, the Worker is responsible for writing files, and the planner may only read files, run read-only checks, and re-delegate tasks.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/12/2026
First Seen
Valid until: 1/10/2027
Sources
Related Entities
Related Claims
UnverifiedAtomic Agent chose to attach a rejection message ('you are responsible for planning, the Worker is responsible for writing') to the tool call's returned result rather than dynamically removing the write tool, in order to protect the local planning model's KV cache and avoid cache invalidation caused by a change in the prompt prefix.74% similarUnverifiedAtomic Agent once allowed Workers to return tasks to the planner via needs_orchestrator, and this exception channel was exploited by the planner for 13 writes in testing; in one run, 4 of 6 tasks took this path.67% similarUnverifiedResponsibilities should be separated between the Agent (responsible for proposing, with no sending or credential modification) and the Executor (responsible for acting, only running proposals marked as approved and atomically checking status).66% similarVerifiedIn Agent mode, the AI has the ability to read and write files, execute terminal commands, capture errors and automatically retry, and can complete the full closed loop of reading projects, analyzing problems, modifying files, and executing verification.66% similarUnverifiedThe agent invokes the Credo inspection standards configured by the project itself, rather than a generic rule set.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1010243API
curl https://kongchang.com/api/v1/knowledge/claims/1010243MCP
get_claim(id=1010243)