Repository navigation
docs(D-DRF-1): immutable DR64 focus leases, foreign-cache amortization and sparse writeback - #1756
AdaWorldAPI wants to merge 5 commits into
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
…-foreign-cache-20261024
… board rows DECISION 2026-10-24, recorded in the plan (§5), the zero-copy law and the warden card: the cache is a cost-justified exception, scoped to foreign-key reads across several ontologies reused by many thoughts and feeding learning into live-generated ONNX. It is disposable, keyed by the full witness, and lapses where DRF-P2 does not measure a whole-run win. Also: INTEGRATION_PLANS entry, STATUS_BOARD D-DRF rows, board entry, #1755 marked merged, main merged in. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01G22yT6htkcdyXsihxxXdrg
…(A1–A3) The foreign-key cache exception's basis is: only dirty rows are written back; most accesses (expected 70-90%) are reads served from the versioned cache; many learning steps need only the Boolean relationship maps, not values. Each is now a measured quantity in DRF-P2 with its denominator. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01G22yT6htkcdyXsihxxXdrg
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
D-DRF-1: immutable DR64 focus → leased foreign cache → amortized dirty-row writeback
Status: DRAFT REFERENCE ONLY. This PR makes the operator's clarified architecture citable before any coding-agent prompt or EXO-50 handoff. It adds two research/preregistration Markdown files, and no Rust, ABI, wire, runtime, storage or CI code.
The gap this closes
Files
Explicit relationship to existing work
Acceptance and exclusions
Review request: confirm operator semantics and admission/ownership boundaries, especially dataset+branch versioning, compaction seals, scoped pre-fold gathers and alias-safe dirty-row reductions. Those should be settled from this PR before any code is commissioned.