Rendered from docs/obligations/0063-an-anchor-that-resolves-inside-a-declared-exclusion.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

An anchor that resolves inside a declared exclusion has no stated outcome

Context

Spec 1 fixes three outcomes for an anchor: resolved, unresolved, and withheld. A corpus exclusion states that a path is not corpus content, which is neither a defect nor a withholding. Q17 rules on the withheld case and not on this one.

Obligation

Either spec 1 admits a fourth outcome, or an exclusion is a fact about the census alone and an anchor never sees it.

Discharge

The engine reports the hit, because the file is there and write-time impact detection reads the file rather than the corpus. It names the exclusion beside the hit, so that no reader learns that a document governs something this corpus says it does not hold.