Uh oh!
There was an error while loading. Please reload this page.
docs(dig-node): reconcile the two cache-method families in the control contract - #6
Merged
Conversation
…l contract Add SPEC §7.9 documenting that the node exposes cache operations under TWO method families by design: the OPEN node-engine-native `cache.*` (getConfig/setCapBytes/ clear/listCached/removeCached/fetchAndCache — no token, also the in-process FFI names the DIG Browser chrome://settings handler calls) and the token-gated `control.cache.*` operator aliases (get/setCap/clear). Records the name mapping (control.cache.get↔cache.getConfig, setCap↔setCapBytes, clear↔clear), states both are permanent/backwards-compatible (neither renamed), and gives consumer guidance (token holder → control.cache.*; sandboxed/FFI consumer → cache.*). Also states the full catalogue defined by this SPEC is authoritative, consumers implement subsets without diverging names, and dig-rpc-types is the eventual shared home. Closes the #130 naming-reconciliation gap flagged in the cross-repo consistency audit (three hand-mirrored control lists + two cache families). Docs-only.
Uh oh!
There was an error while loading. Please reload this page.
MichaelTaylor3d added a commit
that referenced
this pull request
Jul 10, 2026
…l contract (#6) Add SPEC §7.9 documenting that the node exposes cache operations under TWO method families by design: the OPEN node-engine-native `cache.*` (getConfig/setCapBytes/ clear/listCached/removeCached/fetchAndCache — no token, also the in-process FFI names the DIG Browser chrome://settings handler calls) and the token-gated `control.cache.*` operator aliases (get/setCap/clear). Records the name mapping (control.cache.get↔cache.getConfig, setCap↔setCapBytes, clear↔clear), states both are permanent/backwards-compatible (neither renamed), and gives consumer guidance (token holder → control.cache.*; sandboxed/FFI consumer → cache.*). Also states the full catalogue defined by this SPEC is authoritative, consumers implement subsets without diverging names, and dig-rpc-types is the eventual shared home. Closes the #130 naming-reconciliation gap flagged in the cross-repo consistency audit (three hand-mirrored control lists + two cache families). Docs-only. Co-Authored-By: Claude <noreply@anthropic.com>
MichaelTaylor3d added a commit
that referenced
this pull request
Jul 10, 2026
…l contract (#6) Add SPEC §7.9 documenting that the node exposes cache operations under TWO method families by design: the OPEN node-engine-native `cache.*` (getConfig/setCapBytes/ clear/listCached/removeCached/fetchAndCache — no token, also the in-process FFI names the DIG Browser chrome://settings handler calls) and the token-gated `control.cache.*` operator aliases (get/setCap/clear). Records the name mapping (control.cache.get↔cache.getConfig, setCap↔setCapBytes, clear↔clear), states both are permanent/backwards-compatible (neither renamed), and gives consumer guidance (token holder → control.cache.*; sandboxed/FFI consumer → cache.*). Also states the full catalogue defined by this SPEC is authoritative, consumers implement subsets without diverging names, and dig-rpc-types is the eventual shared home. Closes the #130 naming-reconciliation gap flagged in the cross-repo consistency audit (three hand-mirrored control lists + two cache families). Docs-only. Co-Authored-By: Claude <noreply@anthropic.com>
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 freeto 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.
What
Follow-up to #5 (the #130 canonical control contract). Adds SPEC §7.9 reconciling the two cache-method families the node exposes, per the cross-repo consistency audit.
Why
The audit flagged that dig-node exposes TWO cache families — the open
cache.*(getConfig/setCapBytes/…) and the token-gatedcontrol.cache.*(get/setCap/clear) — with no explicit reconciliation in the canonical control-interface doc. This documents the dual surface so consumers know which to use.Changes (docs-only)
control.cache.get↔cache.getConfig,control.cache.setCap↔cache.setCapBytes,control.cache.clear↔cache.clear), that both are permanent/backwards-compatible (neither renamed), consumer guidance (token holder →control.cache.*; sandboxed/FFI consumer →cache.*), and that the SPEC's full catalogue is authoritative (consumers implement subsets without diverging names;dig-rpc-typesis the eventual shared home).Version
0.5.0 → 0.5.1(patch, docs-only; no code/API/behavior change).Verified
Docs + version only; no Rust source touched. CI gates (fmt/clippy/test/coverage/build) run on the workspace unchanged from the green #5 merge.
Refs #130.