延续层：智能为何需要承载信息的架构基础（注：这个翻译保持了原标题的隐喻性和学术感。"Continuity Layer"译为"延续层"既体现了层级概念，又突出了信息传递的持续性。"Architecture for What It Carries Forward"意译为"承载信息的架构基础"，通过"承载"对应"Carries Forward"的动态意象，用"基础"强化"Architecture"的结构性含义。整体译文在保持学术严谨性的同时，通过四字格"架构基础"和"延续层"的术语化处理，符合中文科技论文的标题风格。）

摘要

人工智能领域最核心的架构问题并非模型规模，而是缺乏承载模型认知成果的延续层。会话会终止，上下文窗口会饱和，记忆接口返回的扁平化事实迫使模型每次读取都需重新解构。这导致智能体在单次会话中表现卓越，却无法实现跨时间维度的记忆延续。本立场文件指出：解决这一问题的连续性层级，正是该领域尚未构建但影响最深远的底层设施，而其工程实践已公开启动。相关特性的正式评估框架ATANT基准（arXiv:2604.06710）已独立发布，包含对250篇故事集的评测结果；姊妹篇论文（arXiv:2604.10981）则将该框架与现有记忆、长上下文及智能体记忆基准进行对比。本文首次将连续性定义为具备七大特征的系统属性，区别于记忆与检索功能；提出通过写时分解与读时重构建的存储原语（解构轨迹收敛记忆）来实现该属性；将工程架构映射至神学中的虚己模式与符号学中的阿尔法-欧米伽范式，并论证这种映射具有结构一致性而非隐喻性；规划从外部SDK到硬件节点再到长期人机基础设施的四层发展路径；阐释当前制约模型层的物理极限如何使连续性层变得至关重要；最后论证治理架构（以物理机制而非政策条款实现隐私保护，创始人通过不可协商的特别股权坚守架构承诺）与产品本体不可分割。

English

The most important architectural problem in AI is not the size of the model but the absence of a layer that carries forward what the model has come to understand. Sessions end. Context windows fill. Memory APIs return flat facts that the model has to reinterpret from scratch on every read. The result is intelligence that is powerful per session and amnesiac across time. This position paper argues that the layer which fixes this, the continuity layer, is the most consequential piece of infrastructure the field has not yet built, and that the engineering work to build it has begun in public. The formal evaluation framework for the property described here is the ATANT benchmark (arXiv:2604.06710), published separately with evaluation results on a 250-story corpus; a companion paper (arXiv:2604.10981) positions this framework against existing memory, long-context, and agentic-memory benchmarks. The paper defines continuity as a system property with seven required characteristics, distinct from memory and from retrieval; describes a storage primitive (Decomposed Trace Convergence Memory) whose write-time decomposition and read-time reconstruction produce that property; maps the engineering architecture to the theological pattern of kenosis and the symbolic pattern of Alpha and Omega, and argues this mapping is structural rather than metaphorical; proposes a four-layer development arc from external SDK to hardware node to long-horizon human infrastructure; examines why the physics limits now constraining the model layer make the continuity layer newly consequential; and argues that the governance architecture (privacy implemented as physics rather than policy, founder-controlled class shares on non-negotiable architectural commitments) is inseparable from the product itself.

The Continuity Layer: Why Intelligence Needs an Architecture for What It Carries Forward

摘要

Support