Explain copy-on-write tails and shared prefix trunks - #27
Closed
FujitsuPolycom wants to merge 1 commit into
Closed
Conversation
Describe immutable row tails, authenticated page deltas, cross-root row-trunk coalescing, and SparkCache CUDA restore and placement ownership in the interactive explorer. Add README discoverability and a GPU-free HTML contract, and refresh deployment source digests because the test is part of the deployable SparkCache tree. Compatibility: documentation and regression coverage only. CacheIdentity wire values, digest salts, 256-token geometry, stored formats, and runtime behavior are unchanged. Cache namespace impact: none. Validation: 750 SparkCache tests passed with 7 skipped; 108 deployment tests passed with 1 skipped; Ruff passed; desktop 1440x900 and mobile 390x844 browser checks passed with no horizontal overflow or console errors.
Owner
Author
FujitsuPolycom
deleted the
codex/sparkcache-prefix-explainer-tail-trunks
branch
August 31, 2026 02:09
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
1 participant
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.
Result
The interactive prefix-reuse explorer describes SparkCache as implemented: 256-token logical boundaries, longest all-rank selection, bounded row aliases, immutable row-tail publication, authenticated opaque-page deltas, cross-root row-trunk coalescing, bounded shared GPU-prefix leases, and SparkCache CUDA restore and placement ownership.
The README links the explorer. A GPU-free HTML contract verifies internal identifiers, ARIA targets, local links, interactive scenarios, concurrency controls, canonical status vocabulary, required present-state claims, and rejection of obsolete terminology.
Status and limits
Compatibility
CacheIdentity wire values, digest salts, 256-token geometry, stored formats, and runtime behavior are unchanged. Cache namespace impact: none. The explorer documents the already distinct tail-cow-v1 identities.
Adding sparkcache/test_prefix_explainer.py changes the deployable source-tree digest to 335296b16304ef9b13d4e3b5b68dce41d332dcd2abce8df2ae2a25451471a06a. The GLM-5.2 and DeepSeek-V4 deployment profiles carry that exact source identity.
Validation
Stack
This draft targets codex/sparkcache-cuda-restore-terminology, the head of draft PR #26.