Skip to content

docs: MESSAGE-IDENTITY — content hashes as the cross-turn join key (#1496) - #1506

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-27_message-identity-doc
Sep 27, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-09-27_message-identity-doc

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

What & why

Closes #1496 (documentation direction).

Adds MESSAGE-IDENTITY.md + MESSAGE-IDENTITY.zh-CN.md, the message-granularity sibling of SESSION-IDENTITY.md, settling the #1496 question: message identity stays content-derived; ingress-assigned ids do not replace the hash.

Key points recorded:

Changes

  • MESSAGE-IDENTITY.md (new)
  • MESSAGE-IDENTITY.zh-CN.md (new)
  • README.md / README.zh-CN.md: one cross-reference line each, next to the existing SESSION-IDENTITY pointer

Behavior changes

None — docs only.

Tests

None (docs only).

Config surface

None.

…1496)

Design record settling #1496 at message granularity, sibling to
SESSION-IDENTITY: the question is the join key (mNNNNN auto-increment
already exists), content bytes are the only all-host all-lane stable
key, failure-mode asymmetry (misattribution vs non-recognition), the
#242 partial round-trip channel and why it is not identity, tags as
derived views, and the lastPassIds echo-discrimination fix direction.
@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-09-27_message-identity-doc (9e48858)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.1434-pr.1506.5c2b0b8

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr1506.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

文档已落地,PR #1509:#1509

交付物(与 issue 规格一致)

  • MESSAGE-IDENTITY.md(新,187 行)— 英文设计记录
  • MESSAGE-IDENTITY.zh-CN.md(新,156 行)— 中文镜像
  • README.md / README.zh-CN.md:各一行交叉引用,紧挨既有 SESSION-IDENTITY 指针(zh README 按该文件主流惯例链向 .zh-CN 版本)

纯文档:4 files,+346/−0,零代码、零配置、零行为变更。单 commit,rebase 到当前 master(516f987)后推送。

Issue 七个要点全部落进文档,且逐条对过当前代码

写之前把文档里每个代码级断言都在 master 上核了一遍(不是照抄 issue 描述):

文档论点 核实锚点
mNNNNN 账本 = 会话内自增、永不复用;hash 是每轮 join AGENTS.md §2 kernel contract(assignRefsNode cursor = highestUsedIndex+1);byRaw 消费点 src/server.ts、src/fork-adoption.ts、src/preflight.ts、src/decompress-shared.ts、src/image-compress.ts
hash 兼作变更探测器 src/session.ts foldCoverage / detectUnannouncedHistoryRewrite / REWRITE_MIN_INCOMING_TOTAL(server.ts 四处调用);fork adoption 确认是 #629(src/fork-adoption.ts)
Responses id 命名空间(#242/#1475) devlog/2026-08-25_responses-id-length(66>64 字符、Codex Desktop rollout 回传、每轮 400);src/loop/adapter-responses.ts sanitizeResponsesInputIds + RESPONSES_ITEM_ID_MAX = 64,healing 确实只限 msg-proxy-* 前缀
tag 是派生视图(#206/#14/#673/#1039) src/loop/tag-echo-filter.ts 头注(INVARIANT #1039:参数 byte-exact,只剥散文)
strict-echo 是唯一上游强制内容往返(#684,#762/#1479/#1482) src/strict-echo.ts(isStrictReasoningEcho / normalizeStrictEchoReasoning)+ server.ts reasoning-pair-violated;#762 在 src/loop/core.ts 确为 strict-echo origin;#1482 已合入 master(merge commit「responses-strict-echo」),引用成立
失败模式不对称(#1307 163/163) #1307 在 src/plugin.ts 确为同 session key 侧请求短数组场景

一个写作细节:EN 文档里唯一一处字面渲染 tag 示例经字节级核查完整落盘(显示层会吞 acp 标记,磁盘内容无损)。

说明


中文摘要:按 issue 规格写完 MESSAGE-IDENTITY 双语文档并开 PR #1509(纯文档 +346 行,所有代码级论断已对当前 master 逐一核实),等待人工合并。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[design review] 消息身份层:content-hash 是否可被显式自增 id 取代?请复核

1 participant