Reuse prior work without reusing the wrong authority.
Cache exact and semantically equivalent results, retain useful application memory, and reuse both only when the current request still matches the identity, tenant, resource, purpose, version, freshness, source, policy, and lifecycle conditions that made the prior artifact valid.
Treat reuse as an application decision
Artifact risk
Cached artifacts may contain tenant data, resource conclusions, retrieval results, classifications, summaries, or evidence valid only under earlier state.
Semantic match
Semantic similarity can propose a Reuse Candidate, but it does not establish authority, source state, policy, time, or output compatibility.
Eligibility decision
Reuse begins by proving that the prior artifact is still eligible to replace new work for this Execution Instance.
Put every reusable artifact behind a Reuse Safety Contract
A cache hit should mean semantically valid reuse, not merely key equality or vector similarity.
Reuse more than model responses where the contract permits
Make reuse outcomes explicit
REUSE, RECOMPUTE, REFRESH, REVALIDATE_AUTHORITY, VERIFY, DENY, and INVALIDATED tell the application why reuse did or did not proceed.
Invalidate on business change, not only elapsed time
Source, resource, permission, policy, taxonomy, classification, model version, Context Plan, contradictory evidence, or quarantine events can invalidate reuse.
Carry authority through reuse
A result created under valid authority yesterday does not create authority today. Current execution must still be eligible for the current resource, purpose, and consequence.
Explore Identity & SecurityRemembering something does not make it true
Memory informs the work, but persisted application state determines exact continuation and what the application may do next.
Give every memory item an explicit application meaning
A Memory Artifact can preserve proposition, source, semantic role, status, scope, classification, expiry, invalidation rules, permitted consumers, and provenance.
Map where reuse is safe, where memory is advisory, and where fresh work is required.
Use an architecture review to define Reuse Safety Contracts, cache identity, semantic reuse, invalidation, Memory Contracts, promotion gates, and Memory-to-Decision Lineage.