For an anchor rule explaining one model prediction, what do precision and coverage each mean?
answer
- two numbers, two different questions
- one is about correctness inside the rule
- the other is about how many rows qualify
- adding conditions moves them opposite ways
- pin every feature: precision one, coverage nil
basics
~20 sPrecision is the share of rows satisfying the rule that the model still labels the same way as the explained row; coverage is the share of the population that satisfies the rule at all. Higher precision usually buys narrower coverage.
solid answer
~50 sAn anchor is an IF-THEN rule over feature conditions, presented as a sufficient condition for the model's decision — for a resume screener, `IF years_experience < 2 AND no certification THEN reject, precision 0.96`. Precision is estimated by sampling rows that satisfy those two conditions while letting everything else vary, then measuring how often the model still rejects: 96% here. Coverage is the separate question of how many real applicants satisfy the conditions at all — if that is 4%, the rule genuinely explains this applicant but summarises almost nobody else. The search adds conditions until precision clears a chosen threshold, and every condition added narrows coverage, so the two trade off directly. Note also that precision is a probabilistic estimate from a finite sample, not a proof, and it is defined relative to the perturbation distribution you sampled from.
go deeper
Recall that an anchor is an IF-THEN rule attached to one prediction, and that it comes with two numbers: how reliably the decision holds inside the rule, and how many rows the rule applies to. Do not confuse the first with a classifier's precision against true labels.
Explain how precision is estimated by sampling rows that satisfy the conditions while other features vary, why greedy addition of conditions raises precision and lowers coverage, and why the all-features-pinned rule is the degenerate case that makes coverage mandatory.
Demonstrate judgment about when to show such a rule at all: a modest-precision anchor misleads, and a high-precision rule with negligible coverage supports no general claim. Note that precision inherits whatever realism the perturbation distribution has.
Decide where rule-shaped explanations belong in your review and appeals process. They read as commitments to a non-technical audience, so the threshold, the sampling budget and the wording around 'this decision would not change' are governance choices, not implementation details.
## What an anchor is A local linear surrogate answers 'how much did each feature push?'. An **anchor** answers a different question: 'what set of conditions, once true, is enough to pin this prediction down?' It is an IF-THEN rule over feature predicates, and its promise is scope: as long as these conditions hold, the model's output is essentially fixed, whatever the other features do. For a resume-screening model that rejected one applicant, an anchor might read: `IF years_experience < 2 AND certification = none THEN reject (precision 0.96, coverage 0.04)` That single line carries two very different numbers, and interviewers ask about them precisely because candidates blur them. ## Precision **Precision** is the probability that the model gives the same prediction as it gave the explained row, *among inputs that satisfy the rule*. It is estimated by sampling: hold the anchor's conditions fixed at the explained row's values, let every other feature vary according to a perturbation distribution, score each sampled row with the model, and count how often the prediction matches. Precision 0.96 means 96% of those sampled rows were also rejected. Two qualifications matter. First, it is **probabilistic, not absolute**. Precision is estimated from a finite sample, so the search cannot certify it exactly; the guarantee is of the form 'the returned rule's true precision is at least the threshold with high probability'. Efficient anchor search is usually framed as a bandit problem — spend sampling budget on candidate rules that might beat the threshold, prune the ones that clearly cannot — because that is how you get a confident answer without scoring every candidate exhaustively. Second, precision is **relative to the perturbation distribution**. The number describes how the model behaves on the rows you sampled. If that sampler produces combinations that never occur in the applicant pool, the 0.96 is a fact about synthetic inputs and may not transfer to real ones. ## Coverage **Coverage** is the probability that a randomly drawn input satisfies the rule's conditions at all. It says nothing about correctness; it says how *broad* the explanation is. Coverage 0.04 means the rule speaks for about four percent of applicants. The reason coverage is reported is that precision alone can always be maximised trivially. Take the degenerate anchor that pins every feature of the row to its exact observed value: no other row satisfies it, the perturbation sample is the row itself, and precision is 1.0 by construction. That rule explains nothing — it is just the input restated. Coverage is what exposes it: near zero. ## The tradeoff Anchor search is typically greedy: start from the empty rule, add the condition that most improves precision, stop when precision clears the threshold. Each added condition can only shrink the set of inputs that satisfy the rule, so **precision climbs and coverage falls monotonically as the rule grows**. Raising the threshold from 0.90 to 0.99 therefore does not just make the rule stricter — it usually makes it longer and narrower, and a longer rule is also harder for a human to act on. A useful reading of the pair: - **High precision, decent coverage** — a genuinely informative rule; it describes a whole region of the model's behaviour. - **High precision, tiny coverage** — an honest explanation of this one case, but no basis for any general statement about the model. - **Modest precision** — the rule is not a sufficient condition; the model flips inside it, and showing it as an explanation misleads. ## Anchors versus a linear local surrogate The forms answer different questions and fail differently. A linear surrogate gives graded, signed contributions but leaves its region of validity implicit — you must decide separately how far it reaches. An anchor states its region explicitly, as conditions, with a measured precision attached, which makes it easier to hand to a non-technical reviewer: 'while these two things are true, the decision does not change.' The cost is that anchors need a threshold, a perturbation distribution and a sampling budget, they only apply where crisp predicates exist, and they say nothing about magnitude — no sense of how *strongly* a condition mattered, only that it sufficed. ## What to say in an interview Define both numbers precisely, name the degenerate maximum-precision rule as the reason coverage is always reported alongside it, and note that the precision is a sampled estimate with a confidence attached rather than a guarantee about every possible input.
- What does an anchor with precision 1.0 and coverage near zero tell you?That the rule has degenerated into a restatement of the input. Pin enough features to their observed values and no other row satisfies the rule, so precision is trivially perfect while the explanation generalises to nobody. Coverage is reported specifically to expose this, and such a rule should not be presented as an explanation of the model's behaviour.
- How does an anchor differ from the coefficients of a linear local explanation?An anchor states an explicit region — while these conditions hold, the prediction stays put — and attaches a measured precision to that claim. A linear explanation gives signed magnitudes but leaves its region of validity implicit. Anchors are easier to hand a non-technical reviewer; they carry no sense of how strongly each condition mattered.
- Why is the precision described as a guarantee that holds with high probability rather than a certainty?Because precision is estimated from a finite sample of rows satisfying the rule, not computed over all possible inputs. The search returns a rule whose true precision is at least the threshold with a stated confidence, spending its sampling budget to separate promising candidates from clear failures rather than exhaustively evaluating every rule.
saying these in an interview costs you the question
- Confuses anchor precision with classifier precision on labels
- Reports precision without coverage
- Treats the precision threshold as an exact guarantee
- Thinks a longer rule is always a better explanation
- Ignores that precision depends on the perturbation distribution