ContextCord
架构图Atlas
ContextCord Docs · Module model

从工程状态到验证结果。From engineering state to verified outcomes.

了解六个模块如何共享项目状态、选择上下文并验证结果。按宿主和工作流配置能力，然后查看模块依赖与可复现评测。See how six modules share project state, select context and verify results. Configure capabilities for your host and workflow, then explore dependencies and reproducible evaluations.

ContextCord
shared kernel
ContinuumContext EngineVeritasDecision PlaneGatewayJev · optional
01 · Product modules

六个模块，一条工程接续链。Six modules. One engineering workflow.

从任务接续到验证结果，六个模块共享项目状态与证据；能力配置让你选择当前工作流需要的部分。From task continuity to verified outcomes, six modules share project state and evidence. Capability profiles let you choose the pieces your workflow needs.

01 · Remember the work

Continuum

Core

它解决：工程做到哪里了？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.

Capabilities
continuity · memory · handoff · closeout
Source
continuity.py · store.py · memory.py · handoff.py · closeout.py
Value
记住工程进度，而不是记住聊天记录。Remember engineering progress, not chat history.
02 · Select context

Context Engine

Core

它解决：下一位 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.

Capabilities
memory (selection subsystem)
Source
context.py · bm25.py · memory.py · handoff.py
Value
选择最需要的上下文，而不是把历史全部塞回模型。Select the context that matters instead of replaying all history.
03 · Preserve why it is true

Veritas

Core

它解决：为什么这条记忆现在还值得相信？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.

Capabilities
core · evidence
Source
identity.py · truth.py · evidence.py · receipt.py · qualification.py
Value
不仅保留结论，还保留结论为什么成立。Keep not only the conclusion, but why it holds.
04 · Bound decisions

Decision Plane

Optional

它解决：模糊问题由谁决定，模型又能决定到哪里？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.

Capabilities
decision · router · model_intelligence
Source
decision_fabric.py · router.py · model_intelligence.py · policy.py
Value
模型可以判断，但模型没有最终权力。Models may judge; code retains final authority.
05 · Connect hosts

MCP / Host Gateway

Gateway

它解决：怎么跨 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.

Capabilities
mcp · hosts
Source
mcp.py · service.py · host_registry.py · host_configs.py
Value
一个核心状态层，接入多个 Coding Agent。One state core, multiple coding-agent hosts.
06 · Semantic advisor

Jev

Optional provider

它解决：哪些窄问题值得交给模型做语义判断？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.

Capabilities
jev / optional extra .[jev]
Source
jev_provider.py · decision_fabric.py
Value
用类型化语义判断解决关键工程选择。Resolve key engineering choices with typed semantic judgment.
02 · Runtime modularity

能力配置让运行时边界保持清晰。Capability profiles keep runtime boundaries clear.

Continuum、Decision Plane、Jev 与 Host Gateway 通过同一 Capability Registry 组合；Handoff 默认使用确定性 BM25 选择，并可按需启用语义重排。Continuum, Decision Plane, Jev and the Host Gateway compose through one Capability Registry. Handoff uses deterministic BM25 selection by default, with semantic reranking available when needed.

核心边界Core boundaries

  • 12 个 runtime capabilities 共用注册表，并通过 requires 声明能力依赖。Twelve runtime capabilities share one registry with explicit dependency closure; research remains dev-only.
  • MCP Tool Catalog 根据 effective capabilities 动态收缩；关闭能力不会暴露 Tool。The MCP tool catalog shrinks with effective capabilities; disabled features expose no tools.
  • Jev 是 .[jev] 可选依赖，Provider 状态检查不暴露 secret。Jev is an optional .[jev] extra and provider status inspection does not expose secrets.
  • Model Intelligence 是只读 advisory provider，失败不阻塞确定性 Router。Model Intelligence is a read-only advisory provider; failure does not block deterministic routing.

组合方式Composition

  • Continuity 与 Decision Plane 保持独立，Handoff 不要求启用语义决策模块。Continuity remains independent from the Decision Plane; Handoff does not require the semantic decision module.
  • continuity profile 聚焦工程接续；Decision Plane 可通过独立 profile 按需启用。The continuity profile focuses on engineering continuation; the Decision Plane can be enabled independently when needed.
  • Context Engine 与 Veritas 共享同一 Capability Registry 与 StateStore。Context Engine and Veritas share the same Capability Registry and StateStore.
  • 所有模块保持单一 Python distribution 与单一 StateStore。All modules remain within one Python distribution and one StateStore.
shared kernel (core / StateStore / config)
├── Veritas            ← evidence / identity / truth / receipts
├── Continuum          ← continuity / memory / handoff / closeout
│    └── Context Engine← bounded selection / BM25 / archive references
├── Decision Plane     ← decision / router / model_intelligence
│    └── Jev           ← optional semantic provider
└── MCP / Host Gateway ← mcp / hosts → exposes only enabled surfaces

Continuum ─────────> deterministic Handoff / bounded context
Decision Plane ────> routing / model intelligence
optional Jev ──────> semantic enhancement when enabled

能力配置同时控制依赖加载和 MCP 工具列表。启用所需模块后，各宿主共享同一份任务状态与证据。Capability profiles control dependency loading and the MCP tool list. Enable the modules you need and share task state and evidence across hosts.

03 · Capability profiles

用能力配置组合你的工作流。Compose your workflow with capability profiles.

使用 minimal、continuity、decision 或 full 快速开始；通过 custom 精确选择当前任务需要的能力。Start with minimal, continuity, decision or full; use custom to select exactly the capabilities your task needs.

minimalcore + evidence

最小可信内核。Smallest trusted kernel.

continuitycontinuity + memory + handoff + gateway…

continuity 只保留 continuity + memory + handoff + gateway；Decision Plane 为独立 profile。Continuity keeps continuity + memory + handoff + gateway; Decision Plane remains independent.

decisiondecision + router + model intelligence

可以从 CLI 单独使用；MCP 不自动开启。Usable from CLI independently; MCP is not implied.

full / customall / explicit enable-disable

完整体验或精确组合。Full experience or exact composition.

04 · Setup

从最小路径开始。Start with the smallest path.

先让 doctor 与 source identity 正常，再按需要启用 Decision Plane、Gateway 或 Jev。Get doctor and source identity healthy first, then enable Decision Plane, Gateway or Jev only when needed.

local setup
python -m pip install -e ".[dev]"
contextcord init --profile generic
contextcord doctor
contextcord feature list
contextcord resume --assist

# optional semantic provider
python -m pip install -e ".[jev]"
# set TYPESAFE_API_KEY locally
contextcord provider jev status
05 · Host Gateway

在熟悉的编程宿主中继续工作。Continue in the coding host you already use.

Codex、Cursor、Qoder、OpenCode、WorkBuddy 共享同一 MCP 应用边界；其它宿主通过 BYOH Adapter Manifest 接入。Codex, Cursor, Qoder, OpenCode and WorkBuddy share the same MCP application boundary; other hosts connect through BYOH adapter manifests.

Codex · Cursor · Qoder

宿主只翻译配置/调用边界；任务状态、策略、证据仍来自 ContextCord。Hosts translate configuration and call boundaries only; task state, policy and evidence remain in ContextCord.

OpenCode · WorkBuddy · BYOH

BYOH 配置连接宿主与 ContextCord，复用任务、决策和证据。BYOH configuration connects your host to ContextCord and reuses task state, decisions and evidence.

Evaluation

接续状态与有界语义判断。Continuity and bounded semantic judgment.

60 个任务规范派生的跨会话 replay 验证状态恢复、来源变化与对象完整性。Typed-decision evaluation 依据冻结 rubric 检查闭集语义判断；deterministic gate replay 验证代码拥有的执行边界。Sixty task-spec-derived cross-session replays measure state recovery, source drift and object integrity. Typed-decision evaluation checks closed-set semantic judgments against a frozen rubric; deterministic gate replay checks code-owned execution boundaries.

评测Measurement结果Result
任务规范派生的 continuity replaysTask-spec-derived continuity replays60
恢复的工程状态记录Recovered engineering-state records5,040
无损恢复的任务字段 / 笔记集合Lossless task-field / note-set recovery60/60 · 60/60
Handoff payloadHandoff payload217,067 B
Bounded-text baselineBounded-text baseline1,440,000 B
载荷缩减Payload reduction84.9%
依赖变化后进入 revalidation 的状态Dependency-bound states entering revalidation180
源码变化后选中的 stale notesStale notes selected after source drift0
拒绝的 tampered objectsTampered objects rejected60/60
与 frozen rubric 一致的 typed judgmentsTyped judgments matching the frozen rubric299/300 · 99.7%
Live batch observationsLive batch observations30
Typed decision API P95Typed decision API P95453 ms
Deterministic gate replay observed bypassesDeterministic gate replay observed bypasses0/300
查看可复现评测Open reproducible evaluations
06 · Evidence

外部先验、语义判断、真实结果分层记录。External priors, semantic judgment and real outcomes stay separate.

CodexRadar 等公开数据只进入 Model Intelligence；Jev 只产生 bounded semantic choice；只有真实 Host Execution + Verifier 才进入 Local Outcome。Public observations such as CodexRadar enter Model Intelligence only; Jev produces bounded semantic choices; only real host execution plus verifier results enter Local Outcome.

External prior ───────→ Model Intelligence ──┐
                                              ├→ Decision Plane → route receipt
Bounded decision state → optional Jev ────────┘

Effective route → Host execution → Verifier → Local Outcome Ledger
                                      │
                                      └→ Evidence / Receipt Chain / Qualification

完整架构仍在 Home 的 Archify Atlas：System / Router / Workflow / Sequence / Data Flow / Lifecycle 六类图随站点语言切换。The full architecture remains in Home’s Archify Atlas: System, Router, Workflow, Sequence, Data Flow and Lifecycle views follow the site language.

打开 Architecture AtlasOpen Architecture Atlas