Answer lineage and cascade purge (CSOURCE): how it works and when to use it
Answer lineage and cascade purge (CSOURCE), ties answers to their source so that when a document changes, every answer built on it can be purged in one move. Here's how Crowkis does it and why it matters for cost and safety.
Every reworded repeat of a question you've already answered is a full-price model call. Answer lineage and cascade purge (CSOURCE) is how Crowkis ties answers to their source so that when a document changes, every answer built on it can be purged in one move.
How it works
Crowkis ties answers to their source so that when a document changes, every answer built on it can be purged in one move. It runs inside one Redis-compatible engine, so it composes with semantic caching, agent memory, and the other intelligence layers instead of being a separate service you wire together.
CSOURCE PURGE pricing-doc-v3
Why it matters
Repetitive LLM workloads are where the money is, and semantic caching can cut costs up to 60-70% on repetitive workloads. Answer lineage and cascade purge (CSOURCE) is part of what makes that reuse safe rather than reckless, the difference between a cache you trust in production and one you audit after every incident. Drop it in over RESP, gRPC, REST, or MCP, no rewrite required.
Infrastructure earns the critical path one boring, verifiable feature at a time.