Repository navigation
[PR] timestamps: show when each message arrived and when a folded span covers - #5183
Closed
ranxianglei wants to merge 4 commits into
Closed
ranxianglei wants to merge 4 commits into
ranxianglei wants to merge 4 commits into
Conversation
The model gets spatial anchoring (message refs) but no temporal signal: folded spans read as if they happened 'now', and a days-old plan competes with a minutes-old instruction with nothing telling them apart (#4313). - kernel: timeSnapshot — first-seen wall-clock frozen once per message ref at mint (assign-refs node), same discipline as tokenSnapshot. The freeze is unconditional; RENDERING is gated by Config.renderTimestamps (default off, byte-stable with every pre-#4313 wire). - kernel: with the flag on, every rendered ref tag carries at="YYYY-MM-DD HH:mm" (UTC, minute precision) and each rendered summary carrier ends with the covered span's arrival-time range, [folded 2026-10-22 06:14 → 2026-10-22 18:03 UTC] (single point when the range collapses). History without a frozen time renders UNMARKED — never guessed at (the issue's adopted option B for legacy history). - kernel: time retention is wider than the tokenSnapshot live-ref prune — folded messages keep their times (footers read them); entries are dropped only when neither live nor claimed by any block. The field is ABSENCE-PRESERVING everywhere (fresh states, sync clone, hydration) so pre-#4313 persisted states load to their pinned digests; the unified store round-trips it via kstate_json (COMPRESSION_STATE_FIELDS appendix) and the #4599 ledger-alignment remap moves it with the refs. - host: compress.timestamps (config file + Web UI quick toggle, en/zh) maps to kernel renderTimestamps; CONFIGURATION.md / CONFIGURATION.zh-CN document it incl. the one-time prefix-cache flush on enable. - storage-render goldens regenerated (state gains timeSnapshot entries; values are canonicalized to __TS__ so only presence changes). verif subset exception added for the assign-refs Date.now freeze (same class as the block createdAt stamp). - kernel 0.0.170 → 0.0.171. Tests: kernel/tests/issue4313-timestamps.test.ts (format, off-default byte-stability, frozen-time stability across renders, unmarked legacy history, freeze+retention, footer on/off); compress-settings mapping; storage-state-fields mechanism updated for the optional appendix.
Contributor
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.7160-pr.5183.96b1ceaThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr5183.tgz
npm install -g packageInstall instructions are refreshed on each push. |
…rnel lock (CI docs-sync/lock-sync)
Owner
Author
|
重复 #5236 |
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.
Fixes #4313.
kernel-change: state gains
timeSnapshot+ rendering flag (per the issue's owner-discussed design)Implements the design already converged in the issue (storage-layer analysis by ework, option B for legacy history adopted, kuviki's range footer adopted). Declaring here as the PR-level kernel-change record.
config surface
New field
compress.timestamps(boolean, default unset = off):applyCompressSettings)Config.renderTimestampsWhat it does (in plain words)
The model gets spatial anchoring (message refs) but no temporal signal: a folded span reads as if it happened "now", and a days-old plan competes with a minutes-old instruction with nothing telling them apart. With the flag on:
<acp tokens="506" type="text" at="2026-10-22 06:14">m00026</acp>(UTC, minute precision, human-readable — no epoch arithmetic)[folded 2026-10-22 06:14 → 2026-10-22 18:03 UTC]How it works
tokenSnapshot— refs are minted exactly once per identity, so this is the message's arrival time. Unconditional (even while rendering is off): enabling mid-session yields real arrival times for everything seen since deployment, never "now" stamps.at— never guessed at (option B, adopted in the issue).kstate_json(COMPRESSION_STATE_FIELDS appendix) and the CI Control Center: Centralized CI Failure Handling & Status Sync (Comment all CI issues here; do not open new issues) | CI 总控: CI 失败集中处理与状态同步(所有 CI 问题在此评论, 勿开新 issue) #4599 ledger-alignment remap carries it with the refs.Tests & goldens
timeSnapshot(values canonicalize to__TS__, so only presence changes); corpus pins stay green thanks to absence-preserving hydration.Date.nowfreeze (same class as the existing blockcreatedAtstamp).