source · 7ae2c
1.50 s → 0.75 s
01
Retry-After: .35
X-Relay-Checkpoint: 0007CodexQoderCursorOpenCodeWorkBuddy
Product modules
六个模块，一条工程状态主线。Six modules, one engineering-state spine.
模块是理解产品的方式，Capability Registry 是代码里真正负责开关能力的机制。它们不是六套独立数据库，也不要求拆成六个 Python 包。Modules are the product model; the Capability Registry is the runtime switchboard. They are not six independent databases and do not require six Python packages.
01Core
Continuum
记住工作Remember the work
它解决：工程做到哪里了？It answers: where did the engineering work stop?
Task、Session、Note、Checkpoint、Handoff、Resume；StateStore 使用 SQLite WAL；任务与源码身份绑定，Portable Memory 会重检依赖。Task, Session, Note, Checkpoint, Handoff and Resume; StateStore runs on SQLite WAL; task state is source-bound and portable memory rechecks dependencies.
记住工程进度，而不是记住聊天记录。Remember engineering progress, not chat history.
02Core
Context Engine
选择上下文Select context
它解决：下一位 Agent 到底该看到什么？It answers: what should the next agent actually see?
从候选记忆中读取 freshness、authority 与预算信号；BM25 做确定性排序；组装 bounded context packet，并保留原始 archive 引用。Reads freshness, authority and budget signals from candidate memory; uses deterministic BM25 ranking; assembles a bounded context packet while preserving archive references.
选择最需要的上下文，而不是把历史全部塞回模型。Select the context that matters instead of replaying all history.
03Core
Veritas
保留依据Preserve why it is true
它解决：为什么这条记忆现在还值得相信？It answers: why is this memory still trustworthy now?
Git / Truth / Policy / Memory 指纹、Source Identity、Evidence Hash、事件链、Receipt Chain 与 Qualification 共同约束“当前事实”。Git, Truth, Policy and Memory fingerprints, Source Identity, evidence hashes, event chains, receipt chains and qualification bound what counts as current truth.
不仅保留结论，还保留结论为什么成立。Keep not only the conclusion, but why it holds.
04Optional
Decision Plane
约束决策Bound decisions
它解决：模糊问题由谁决定，模型又能决定到哪里？It answers: who decides ambiguous cases, and where does model authority stop?
Gate 0、确定性策略、Adaptive Router v3、Model Intelligence、硬规则与 Decision Receipt 先构造可选集合，再决定是否需要语义判断。Gate 0, deterministic policy, Adaptive Router v3, Model Intelligence, hard rules and decision receipts construct the eligible set before any semantic judgment is requested.
模型可以判断，但模型没有最终权力。Models may judge; code retains final authority.
05Gateway
MCP / Host Gateway
连接宿主Connect hosts
它解决：怎么跨 Codex、Cursor 等宿主继续工作？It answers: how can the same project continue across Codex, Cursor and other hosts?
本地 MCP/stdio、16 类结构化操作、Host Registry、配置渲染器与 BYOH Adapter Manifest；MCP 工具面会跟随有效 Capability 动态收缩。Local MCP/stdio, 16 structured operations, Host Registry, config renderers and BYOH manifests; the MCP tool surface shrinks dynamically with active capabilities.
一个核心状态层，接入多个 Coding Agent。One state core, multiple coding-agent hosts.
06Optional provider
Jev
语义顾问Semantic advisor
它解决：哪些窄问题值得交给模型做语义判断？It answers: which narrow questions deserve semantic judgment?
只接收 typed bounded state，用于 stale conflict、恢复归档、上下文重排、Handoff 模式或闭集路由选择；SDK 与 API Key 都是可选依赖。Receives typed bounded state for stale conflicts, archive restore, reranking, handoff mode or closed-set routing; the SDK and API key are optional dependencies.
把 LLM 从执行者降级成有边界的语义顾问。Turn the LLM from executor into a bounded semantic advisor.
模块 ≠ 独立服务。Modules ≠ separate services. 当前最稳妥的方向是继续保持一个 ContextCord 包与一个 StateStore，把依赖关系做显式、把可选能力真正关闭，而不是为了“模块化”拆出六套状态和六个发布包。The right next step is one ContextCord distribution and one StateStore with explicit dependency boundaries and truly optional capabilities—not six state stores or six packages.
查看源码职责映射（9 组内部实现）Inspect the source-level responsibility map (9 internal groups)
Composable runtime
产品按模块理解，运行时按 Capability 组合。Understand modules; compose runtime capabilities.
源码已经具备 Capability Registry、依赖闭包、动态 MCP 工具面和可选 Jev Provider；Continuum Handoff 现在默认 deterministic，Decision Plane / Jev 只作为惰性增强。The source already has a Capability Registry, dependency closure, a dynamic MCP surface and an optional Jev provider; Continuum handoff now defaults to deterministic execution, with Decision Plane / Jev as lazy enhancements.
现在已经做到Already decoupled
12 个 runtime capabilities 共用唯一注册表，另有 research 为 dev-only；MCP 只暴露当前 effective tools；Jev 是 .[jev] 可选依赖；Model Intelligence 作为只读 prior 可以独立失败。Twelve runtime capabilities share one registry, with research kept dev-only; MCP exposes only effective tools; Jev is an optional .[jev] extra; Model Intelligence can fail independently as a read-only prior.
minimal·continuity·decision·full·custom
依赖反转已完成Dependency inversion completed
handoff.py 不再顶层 import DecisionFabric；continuity preset 只需要 continuity + memory，Decision Plane / Jev 通过惰性策略作为可选增强。handoff.py no longer imports DecisionFabric at module load; the continuity preset needs only continuity + memory, while Decision Plane / Jev remain lazy enhancements.
查看模块依赖与重构计划See module dependencies and refactor plan01
02
03
python -m pip install -e . contextcord doctor contextcord feature list contextcord provider jev status contextcord model-intelligence status contextcord resume --assist # MCP stdio server contextcord mcp