Repository navigation
[PR] docs: add snapshot rendering doctrine to AGENTS/MESSAGE-IDENTITY/SESSION-IDENTITY (follow-up to #3756) | docs: 快照渲染教义补进 AGENTS/MESSAGE-IDENTITY/SESSION-IDENTITY(#3756 跟进) - #3763
Merged
Conversation
…-IDENTITY (#3756) The identity architecture moved through three eras (content-hash join → order-centric reconcile → snapshot render) but the docs still described only the first two. Record the third where agents and contributors read: - AGENTS.md: Key Design Decision 13 (three-era ladder, engine self-owned coverage, degrade-never-guess, observation/render separation) + pointer from the native-stable-identifiers guardrail. - MESSAGE-IDENTITY.md (+zh): new section 'The snapshot render engine' — identity ladder final form (sessionid → seq → signature fallback), what it structurally kills (#3752/#3751), Future direction updated (hashes stay the LEDGER join; seq is the render join). - SESSION-IDENTITY.md (+zh): the session id becomes the whole message identity for the outbound prefix; adoption ladder stays as fallback.
Contributor
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.4448-pr.3763.3592969This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr3763.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Contributor
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.587-master.1ee7d11 # this exact build
npm install -g billion-context@master # always the newest merged build
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(ai: zhipuai-lb/glm-5.3)
消息身份架构已走过三段(content-hash join → order-centric reconcile → 快照渲染),但文档还停在第二段——快照机制、客户端身份从 hash 到顺序再到只认 sessionid 的演进,AGENTS.md 与身份文档都没跟上。本 PR 只改文档,补齐第三段。
改动
不改的