Deleted source content can survive in AI answer caches after the search index is clean. Track source dependencies and define how removal affects future cached responses, previews, and evidence links.
Cached answers are derived artifacts
An answer cache stores a generated result based on particular sources, versions, and user scope. A source deletion or withdrawal can change whether that result remains appropriate even if the query text is unchanged.
For a proposed cache record, retain minimal source dependencies, content version, permission context, and generation configuration. Use the supported invalidation or revalidation mechanism when a dependency is removed.
Do not assume a cache timeout provides immediate removal. It may only bound future reuse under defined conditions. State the actual propagation behaviour and monitor unresolved invalidations.
Trace a fictional withdrawn policy answer
An assistant answers an expense question from policy P-12 and caches the result. The owner withdraws P-12. A fresh search no longer returns it, but the same question still serves the cached answer.
The removal fixture should detect that second path and prevent the answer from appearing as current guidance. If historical answers are retained for approved review, label their evidence and access separately from the normal current-answer service.
| Derived path | Removal check |
|---|---|
| Query-result cache | Removed passages no longer eligible |
| Generated-answer cache | Dependency invalidated or re-evaluated |
| Source preview | Removed or safely qualified |
| Conversation continuation | Defined handling of prior context |
| Exported artifact | Known scope and control limits |
Use a unique synthetic source marker and inspect all supported cache layers. Absence from one ordinary query is not proof that every cached form disappeared.
Distinguish deletion from loss of access
A source can remain valid while one user loses permission. Cache policy must account for that scoped change without unnecessarily deleting legitimate shared evidence for everyone. Stable source and principal relationships make the distinction possible.
Dependency metadata and invalidation add operational cost. Query-only caches are simpler but can be unsafe for protected or rapidly changing content. Choose the smallest design that meets the actual freshness and access requirements, then test races with ongoing generation.
This cache-removal design is proposed. The voice integration case study describes related retrieval work without claiming these guarantees. Pair it with index removal propagation.
Deleted-cache FAQ
Does index deletion clear generated answers automatically?
Not necessarily. Inventory and verify each derived cache path.
Can already downloaded answers be recalled?
Generally not through cache invalidation. State the limit and govern external artifacts separately.
What proves future delivery is controlled?
Replay deletion while querying, generating, caching, and reopening evidence under the actual supported policy.