resident.on-demand-knowledge
Not yet measured
This is a planned measured rule (SPEC §8). It is currently tier heuristic with no committed eval. It reports nothing and gates nothing until its battery passes the recomputed admission test. Running that battery costs API spend and requires explicit approval; it is out of scope for this build. The tier flips to enforced / measured only when the evidence is committed to evals/rules/resident.on-demand-knowledge/ and verified in CI.
Claim
Reference knowledge (archaeology, mechanisms, postmortems) rides resident when its operational residue is one line plus an on-demand file.
Rationale
The flagship candidate (SPEC §10 case study). Detector + committed eval land at M5; until the admission test passes, this rule reports nothing and gates nothing.
Fix
Keep one routing line resident; move the knowledge to a path-scoped rule or topic file.
chaff explain resident.on-demand-knowledge: same registry, offline, from the CLI.