017-general-runtime-optimization
General runtime batching, duplicate suppression, and caches
Lifecycle approvedImplementation in-progressVerification unknownQualification unknown
A separately reviewable amendment to runtime execution for general runtime-planned batching, concurrent duplicate suppression, bounded memory caches, and opt-in persistent caches. Optimized execution must be judgment equivalent to independent uncached execution, isolate authorized scopes, preserve each waiter's deadline and cancellation, attribute one charge and every liability exactly once, invalidate on correction, revocation and erasure, and record every shared-call or cache effect. Existing adapter-scoped batching remains a special case, not evidence that this general contract is implemented or qualified.
Read the full pinned specification ↗Relationships
depends on
Claimed units
- extends
{ "nature": "amending", "spec": "002-decision-contract-and-pure-core", "unit": { "kind": "directory", "path": "crates/rustev-contract/" } } - extends
{ "nature": "amending", "spec": "002-decision-contract-and-pure-core", "unit": { "kind": "directory", "path": "crates/rustev-core/" } } - extends
{ "nature": "amending", "spec": "003-runtime-execution-and-evidence", "unit": { "kind": "directory", "path": "crates/rustev-runtime/" } } - extends
{ "nature": "additive", "spec": "004-evaluation-and-replay", "unit": { "kind": "directory", "path": "crates/rustev-eval/" } } - extends
{ "nature": "additive", "spec": "001-boundaries-and-authority", "unit": { "kind": "file", "path": "Makefile" } }
Source headings
- 017: General runtime batching, duplicate suppression, and caches
- 1. Purpose
- 2. Territory and compatibility
- 3. Behavior
- 3.1 Equivalence and plan identity
- 3.2 Complete request equivalence
- 3.3 Runtime-planned batching
- 3.4 Concurrent duplicate suppression
- 3.5 Budgets, cost and liability
- 3.6 Memory and persistent caches
- 3.7 Invalidation, erasure and races
- 3.8 Evidence, replay and evaluation
- 4. Out of scope
- 5. Observable negative cases
- Acceptance
- Verification
- Implementation record
- Questions settled by R-34
Frozen anchors
No frozen anchors declared.