Criteria leak
criteria-leakThe node can see the acceptance criteria its own output will be judged against.
Where it sits
1 level deep- isolation-breach
- criteria-leak
Each term is a kind of the one before it. A rule written about any term in this chain also applies to criteria-leak.
No term is narrower than criteria-leak.
What it costs
declared or inferredA blueprint starts at a clean 4, loses the weight of every marker present, and the result is clamped into 1–4. criteria-leak is charged once for the whole blueprint no matter how many nodes carry it. The explanation still lists every node that established it.
criteria-leak is one of the three markers the analyzer derives from the graph itself. It can fire on a blueprint whose cards never mention it. A card that declares it and a graph that implies it are the same marker, charged once. The finding records which way round it was established.
The number lives in the engine's configuration and not in this vocabulary. A recalibration touches one file, so every blueprint is charged the same way. Nothing records which calibration an evaluation was made under, so move a weight and two evaluations stop being comparable.
Who uses it
0 cards · 0 blueprintsNo card in the registry names criteria-leak yet. None names anything narrower. A term with no takers is not a broken term.