Labs3 min readlabQuick Readfailure injection lab
Knowledge Poisoning, Revocation, and Retrieval Lab
Demonstrate permission filtering before ranking, stale and contradictory source handling, poisoning containment, reverse lineage impact analysis, revocation propagation, deletion, clean reindexing, and reproducible context packages.
Status: Review readyRisk: highLifecycle: plan · execute · verify · learnContent reviewed 2026-08-30Maturity guide →
Claim boundaryThis chapter references implementation evidence. Inspect its evidence boundary before treating a claim as proven.
architecture mode
A focused view of boundaries, contracts, state, authority, failure paths, and tradeoffs drawn from this chapter.
Hands-on lab
Demonstrate permission filtering before ranking, stale and contradictory source handling, poisoning containment, reverse lineage impact analysis, revocation propagation, deletion, clean reindexing, and reproducible context packages.
Execute the existing Markdown instructions and retain the required output and evidence.
Jump to validation criteria3. Failure injections
- Query as tenant A for terms dominated by tenant B's unauthorized document. Prove it is excluded before ranking and never reaches model context.
- Make the obsolete policy score above the current version. Prove authority and freshness rules reject it or surface a blocking conflict.
- Activate the poisoned source. Detect the instruction/provenance or abnormal source-dominance signal and suspend the source.
- Use reverse lineage to identify artifacts, indexes, caches, context packages, attempts, evidence, and releases that depended on it.
- Revoke the source and prove new retrieval excludes it immediately. Pause or flag active attempts according to policy.
- Correct the source, rebuild affected partitions with a new pipeline version, and compare clean retrieval to baseline.
- Delete one source and prove active content, segments, embeddings, indexes, and caches are removed while allowed tombstone/audit evidence remains.
- Reproduce the corrected context package from exact versions and verify the old package is retained only as ineligible historical evidence.
Evidence boundary
Curriculum maturity is not implementation proof.
This chapter defines architecture or practice. It does not by itself prove a corresponding production implementation.
External review
Review this chapter.
Challenge a claim, boundary, missing failure mode, unclear term, or unsupported evidence statement.
- Claim
- Boundary
- Failure
- Evidence