D0 架构:构建知道何时不交易的 AI 代理 ✍ Donut🕐 2026-04-16📦 11.7 KB 🟢 已读 𝕏 文章列表 文章探讨了在金融市场中构建 AI 交易代理的挑战,指出单纯提升模型智能度不足以保证安全,关键在于架构设计。作者提出了“受限自主性”的概念,并详细介绍了 D0 架构的四个核心层次:验证状态、类型化边界、约束层和闭环进化,旨在确保代理在处理真实资本时的安全性与有效性。 AI交易智能体架构设计风险控制D0LLM金融科技系统安全 # How We Built a Trading Agent That Knows When Not to Trade **作者**: Donut **日期**: 2026-04-15T14:06:19.000Z **来源**: [https://x.com/DonutAI/status/2044417037238460766](https://x.com/DonutAI/status/2044417037238460766) ---  Why the next wave of AI trading won’t be won by the bot that sounds smartest, but by the system that knows when the model is wrong, uncertain, or not allowed to act. Everyone is racing to build smarter agents. In markets, that misses the point. The hard part is not getting an AI to generate a trade strategy, explain a chart, or sound convincing in a Telegram group. The hard part starts one step later, when the model has already made up its mind and now wants to touch real capital in a market that is adversarial, always moving, and completely indifferent to whether your architecture looked impressive in a demo. That is where most AI agent design breaks and that is exactly where D0 begins. A lot of people in AI still talk as if better models will automatically produce better autonomous systems. That is true in some low-stakes environments. If your coding copilot makes a bad suggestion, you reject it. If your writing assistant gets the tone wrong, you edit it. If your chatbot hallucinates, maybe you laugh, maybe you retry. Trading is different. In markets, mistakes do not sit politely in a chat window waiting for a human to clean them up. They become positions, losses, missed exits, liquidation risk, slippage, and a trail of bad decisions that the market happily compounds for you in real time. That is why markets are such a clean stress test for AI agents. They force you to separate what looks intelligent from what is actually safe, useful, and deployable. Financial markets run 24/7. They are noisy, hostile, fragmented, and full of false signals. They punish latency, ambiguity, and overconfidence. If an AI agent can operate well in that environment, it is because the entire system around the model was built to survive contact with reality. ## Not All Agents Are Created Equal This leads to a hot take that more people in AI should say out loud: most “autonomous agents” should never be allowed to trade. Now, say it again. Not because the models are dumb. In fact, the problem is almost the opposite. Frontier models are getting more capable, more persuasive, and more operationally useful. They can absorb more context, reason over more variables, and produce cleaner decisions than ever before. But that increase in capability does not automatically increase safety. In markets, smarter can also mean more dangerous. A stronger model with direct access to execution can simply make larger mistakes, faster, with better-written explanations. The industry tends to think about model progress in terms of what an agent can now do. We think the better frame for high-stakes systems is the tension between scope, fidelity, and containment. Scope is how much the agent is able to do. Fidelity is how closely the system tracks what the user actually meant. Containment is how tightly the system bounds damage when the model is wrong, compromised, or uncertain. Better models usually expand scope. They often improve fidelity too. But containment does not improve on the same curve, because containment is not just an intelligence problem. It is a systems problem, a security problem, and in player vs player domains it becomes an incentive problem too. That distinction matters. A model can understand a user’s intent better than last year’s model and still make a catastrophic decision because the world-facing layer gave it too much freedom. A model can produce a brilliant trading thesis and still fail if the execution path is ambiguous, under-specified, or insufficiently bounded. A model can even be directionally right and still lose money because it was allowed to size incorrectly, act on stale state, or ignore hidden risk limits. In other words, once an agent crosses from cognition into actuation, the bottleneck changes to what exactly is allowed to happen after the model reasons?” That is the core idea behind constrained autonomy. We do not see constraints as a weaker form of autonomy. In high-stakes systems, constraints are what make autonomy real. A useful agent is not one that is free to do anything. It is one that can think flexibly while remaining mechanically bounded when it comes time to act. The model should be free where flexibility creates value and constrained where freedom creates blow-up risk. That split sounds obvious once you say it plainly, but most agent design still treats the model as both the brain and the final authority. That works fine until the action surface becomes expensive. ## The D0 Architecture D0 is built around the belief that the real edge in agentic trading will come from architecture, not just model quality. The public version of that architecture compresses into four layers: verified state, typed boundary, constraint layer, and closed-loop evolution. Each layer exists because the one thing you cannot afford in financial markets is soft ambiguity pretending to be intelligence. Verified state means the model is not reasoning from vibes, stale chat context, or a giant memory blob pretending to be ground truth. It is reasoning from structured facts about the world right now: market state, balances, positions, recent execution outcomes, delegation level, and system risk state. This matters more than most people realize. Traders already know that a small mismatch in state can destroy an otherwise solid decision. AI builders should learn the same lesson that a model that reasons beautifully on bad state is not intelligent in practice.  The D0 Architecture The typed boundary is where a lot of so-called autonomous systems quietly fail. Natural language is great for planning, explanation, hypothesis generation but it is a terrible execution interface. A model can think in language, but the system should not execute in language. If the model wants to express a trade, that intent should be translated into a typed action with explicit fields like asset, side, size, leverage, stop loss, take profit, and execution metadata. The moment real capital is involved, free-form output stops being elegant and starts being a bug. Traders understand this instinctively. You would never want an exchange API to interpret your vibes. The same should be true for agent execution. Then comes the constraint layer, constraints cannot live only inside the model. If they do, they are not really constraints. They are preferences. Real constraints live outside the reasoning path, where they can validate, refuse, suspend, or reroute actions before those actions hit the market. This is where policy becomes real. This is where risk logic matters more than rhetoric. And this is where the system earns the right to be trusted. In a high-stakes environment, a good architecture is one that remains safe even when the model is wrong. The last layer is closed-loop evolution. In the real world, what matters is not what the model intended. What matters is what actually happened. Did the order fill? At what price? Under what volatility regime? What did the market do next? What changed in portfolio state? How should that update the system’s future behavior? If verified outcomes do not flow back into the next cycle, the agent is not really learning from reality. It is just reenacting the same reasoning theater on top of a changing market. Underneath those four layers sit two design choices that matter a lot. The first is path separation. Research can be probabilistic and degradable. An LLM can summarize, weigh weak evidence, and say it needs more data. That is acceptable on the research path because a bad summary degrades analysis quality, not capital. Execution is different. Anything that can move money needs to be typed, validated, and independently verifiable. The second is role separation. The model plans. Infrastructure normalizes. The constraint layer adjudicates. The executor executes. The recorder captures what happened. This separation is what allows the system to improve as models improve without turning every model gain into a larger blast radius. ## This Is Where Intelligence Stops Being Enough This is also where we think the next real debate in AI should be. For the last two years, the center of gravity has been reasoning quality, agent loops, and tool use. All of that matters. But the next wave of real-world agents will be defined less by whether they can complete a benchmark and more by whether they can operate inside hard boundaries without becoming useless. That is the actual design challenge. Not maximum autonomy but create useful autonomy, with limited tool access, and controlled execution. Not a model that always says something impressive. A system that knows what it is allowed to do, what it must verify, and when it should refuse. For traders, this matters because the future interface to markets will not be another dashboard with more indicators crammed onto the screen. It will be an agent layer that monitors, reasons, filters, proposes, and, under the right constraints, acts. But that future only works if the architecture is built for trust from day one. Nobody serious wants an AI that sounds like a genius and trades like a gambler. The product has to make money management, risk control, and execution discipline feel native, not bolted on after the demo. For AI enthusiasts, the lesson is broader than trading. Markets simply expose the truth faster. Once an AI system can trigger irreversible consequences, the old mental model of “just give it more intelligence” stops being enough. Autonomy becomes a systems question. The interesting frontier is no longer model-only. It is the interface between reasoning and the world. That interface is where real product differentiation will come from, and it is where most of the field is still underbuilt. Our view is simple: the winners in agentic trading will not be the teams that ship the flashiest agent first. They will be the teams that build agents people are actually willing to trust with live capital. That means verified state instead of synthetic confidence. Typed actions instead of natural-language execution. Hard constraints instead of polite model instructions. Real feedback loops instead of static demos. In short, it means building autonomy that can survive reality. That is the bet behind D0. It’s not just a chatbot that talks about markets and it’s not a copilot that leaves all the hard parts to the user. D0 is a personal agentic trading system built for the financial internet as it actually is: fast, noisy, hostile, and unforgiving. If that sounds like the direction you’ve been waiting for, join the D0 waitlist. Also, check out: getdonut.ai for more information If you want to read more about Constrained Autonomy, check out our tech technical blog on the matter by our Chief Scientist @trorooro : https://getdonut.ai/blog/constrained-autonomy/ ## 相关链接 - [Donut](https://x.com/DonutAI) - [@DonutAI](https://x.com/DonutAI) - [103K](https://x.com/DonutAI/status/2044417037238460766/analytics) - [join the D0 waitlist.](https://forms.donutbrowser.ai/d0) - [getdonut.ai](https://getdonut.ai/) - [@trorooro](https://x.com/@trorooro) - [https://getdonut.ai/blog/constrained-autonomy/](https://getdonut.ai/blog/constrained-autonomy/) - [Upgrade to Premium](https://x.com/i/premium_sign_up) - [10:06 PM · Apr 15, 2026](https://x.com/DonutAI/status/2044417037238460766) - [103.2K Views](https://x.com/DonutAI/status/2044417037238460766/analytics) - [View quotes](https://x.com/DonutAI/status/2044417037238460766/quotes) --- *导出时间: 2026/4/16 15:51:24*
系 系统工程:构建有效的智能体软件 文章提出构建智能体软件应采用系统工程思维,而非仅优化局部组件。作者提出了软件工程的五个关键层面:代理工程、数据工程、安全工程、接口工程和基础设施工程。文章通过开源项目 Dash 演示了如何将 RBAC、数据隔离和多接口集成等原则应用于实际开发中,强调智能体本质仍是软件,需遵循经典的系统设计原则。 技术 › Agent ✍ Ashpreet Bedi🕐 2026-04-08 智能体系统工程架构设计数据工程安全工程DevOpsLLM最佳实践
技 技能链:将智能体技能重新定义为情境行动 本文探讨了智能体系统中技能实现的局限性,指出技能不应是静态提示,而应是动态的情境行为。作者介绍了在 Slate 系统中通过引入“线程”和“分叉”机制,实现了上下文隔离的自动化技能调用,并提出了“编排技能”的概念,即通过组合其他技能来完成复杂任务链。 技术 › Skill ✍ akira🕐 2026-04-02 AgentLLM智能体SkillSlate技能链架构设计上下文管理自动化多智能体
R Run Your Harness Outside of the Sandbox (Why and How) 本文探讨了2026年以来关于Agent运行位置的争论,指出行业趋势是将Agent运行在沙箱之外。作者详细解释了沙箱内运行的三个主要问题:爆炸半径、信任边界和沙箱的间歇性运行,并提出了将沙箱作为工具暴露的正确架构,最后提供了基于Vercel AI SDK的实现示例和生产环境中的挑战。 技术 › Agent ✍ Nathan Flurry🕐 2026-07-28 Agent沙箱架构设计DevOps后端LLM安全性生产环境Vercel AI SDK状态管理
何 何为“掌控你的智能” 文章探讨了企业如何在通用 AI 基础上构建差异化优势。作者指出,未来五年公司需掌控智能的运作方式、管理与复利,而非仅依赖现成模型。掌控智能包括控制 Agent 系统(模型、调度逻辑、上下文)、掌控质量与风险,以及通过反馈循环积累智能,从而实现业务的深度集成与持续优化。 技术 › Agent ✍ Harrison Chase🕐 2026-07-26 AI企业应用智能体架构设计LangChain商业策略模型掌控上下文管理反馈循环
K Kimi K3 + 图工程:降低85%成本并提升18%准确率 文章介绍了通过结合 Kimi K3 模型与图工程构建 AI 系统的方法。相比传统 RAG,该架构利用知识图谱存储实体关系,能处理复杂推理,实现成本降低85%和准确率提升18%。文章引用微软 GraphRAG 等研究,详细阐述了如何从零开始构建该系统。 技术 › LLM ✍ Noisy🕐 2026-07-23 Kimi K3图工程GraphRAG知识图谱RAG架构设计LLM成本优化
H How to master graph engineering 本课程教授如何构建 AI 智能体图,涵盖图的基本概念、关键模式(如菱形模式)、停止规则及人工审批环节。包含三个实战案例:深度研究台、SEO 内容生成器和市场推广套件,旨在提升业务效率并控制成本。 技术 › Agent ✍ Machina🕐 2026-07-23 AgentGraphLLMClaudeWorkflow工程化自动化架构设计效率实战
3 3 Years of Graph Engineering with LangGraph 文章回顾了 LangGraph 三年来的发展,探讨了将智能体系统建模为图(Graph)的实践与价值。作者分析了何时使用图结构以平衡确定性与自主性,并指出生产级智能体通常需要循环和动态转换。最后,文章强调图工程并非全新概念,但随着节点的进化,现在的图更多是在编排智能体而非单一的 LLM 调用。 技术 › Agent ✍ Sydney Runkle🕐 2026-07-22 LangGraphGraph EngineeringAgentLLM架构设计循环确定性工作流
6 60个AI黑话,一次性翻译成人类语言 文章将60个AI行业专业术语进行了通俗易懂的翻译和解释,涵盖基础概念、训练调优、推理交互、工具扩展、评估安全及前沿趋势六个方面,帮助读者快速理解AI技术地图。 技术 › LLM ✍ 概率鹿梦|AI Wealth Edge🕐 2026-07-22 AI术语大模型智能体AgentLLM科普翻译基础知识
G Graph Engineering 101: When a Loop Isn’t Enough 文章探讨了AI Agent从简单的ReAct循环向图工程架构的演进。循环模式在处理复杂、多步骤及需人工介入的任务时存在状态持久化、错误处理和分支逻辑的局限性。图工程通过显式的节点、边和状态管理,解决了并发、暂停恢复及复杂流程控制问题,为构建更健壮的Agent系统提供了架构基础。 技术 › Agent ✍ Alex Prompter🕐 2026-07-22 AgentGraph EngineeringReActLangGraph架构设计状态管理LLM
彻 彻底告别Loop Engineering:一文读懂 Graph Engineering 本文介绍了AI Agent工程从Prompt到Loop再到Graph的演进。Graph Engineering通过图结构重新规划任务关系,实现并行处理、明确依赖、隔离失败,从而解决线性流程在复杂任务中效率低、易失控的问题。 技术 › Agent ✍ AI超元域🕐 2026-07-21 Graph EngineeringAgentLLM架构设计Claude Code工作流并行处理Dynamic Workflows
L Let's build Claude Code's harness (step-by-step) 本文深入解析了Claude Code的“harness”架构,解释了为何简单的模型调用不足以构建可靠的代码代理。作者通过CrewAI框架逐步重建了包括核心循环、工具管理、规划机制在内的关键组件,揭示了通过工程化手段弥补模型差距的方法。 技术 › Claude Code ✍ Akshay🕐 2026-07-16 Claude CodeAgentCrewAIHarness Engineering代码代理工具调用LLM工程实践架构设计Context Engineering
还 还在用原始对话框?教你用 Obsidian Canvas 与 Agent 协作 本文探讨了传统线性对话框在处理复杂 AI 任务时的局限性,提出了基于 Obsidian Canvas 的非线性协作模式。文章结合学术研究(如 Sensecape、CanvasConvo)和商业产品(如 Copilot Pages、Cursor),展示了如何利用 Canvas 画布作为持久化工作台,让 Agent 理解项目结构而非仅保存聊天记录。作者还介绍了 Obsidian 社区中的 Canvas LLM 和 Cannoli 插件,并总结了如何通过定义颜色、空间和连线规则,实现人与 Agent 在知识库层面的高效协同。 技术 › Agent ✍ 阿哲Phil🕐 2026-07-13 ObsidianCanvas协作模式工作流提效人机交互知识管理LLM智能体