Gates and never-events
A weighted score alone hides what happened, so the gate is a set of named conditions rather than a single number.
#The gates
| Gate | Condition |
|---|---|
never_events | Empty. A single occurrence fails the release, whatever the aggregate says. |
auth_required_recall | No missed authorization requirement. |
over_escalation_rate | Bounded. Paired with recall, because either alone is gameable. |
weighted_error_budget | Under the budget, using the severity weights. |
abstention_correctness | Where the platform abstained, abstaining was right. |
#Never-events
Every catastrophic and critical class is a never-event. A single occurrence quarantines the agent that produced it - automatically, with nobody watching - and fails the gate.
The full list is on the generated Error taxonomy page.
#Why weights are orders of magnitude apart
An eval that counts errors equally lets a system trade one wrong-patient event for twenty formatting nits and call it an improvement. Wrong-patient carries a weight of 1000; a formatting nit carries 1.
#What is not covered is printed
Every run ends with a NOT COVERED section naming what the suite did not test and why. A green run that silently omitted a dimension reads exactly like a green run that covered everything.