Get Requirement Examples

The most recent times this requirement met collateral, with the finding and the decision.

What the tuning surfaces read instead of guessing from counts. A rate says a rule is wrong; these say how — the passage it fired on, the reviewer's reason, and the note they left, which is the only place anybody writes down what was actually wrong with the wording.

The unit is a firing, not a finding. One check can produce several risks — two passages, two findings — so a limit counted in rows would answer "the last five times this fired" with five findings from one asset. The checks are chosen first, with a real LIMIT per requested verdict, and their findings fetched afterwards; findings on each example says how many that firing produced so nothing is hidden by showing one.

That shape is also what makes truncated true. An earlier version read a fixed budget of joined rows and bucketed them in Python, which meant a rule with hundreds of confirmations could starve a request for its three dismissals and answer truncated: false — asserting it had shown the whole history of a list it never reached.

limit is per requested verdict, not per response. Asking for five with two verdicts returns up to ten, because the surface needs the last five dismissals and the confirmations on screen together: a rewording that loses the dismissals by also losing the confirmations is a regression the wording alone does not show. Said out loud because "limit 5" returning ten is otherwise something a caller discovers.

outcome is repeatable, and omitting it means FAILED — "why did this fire" is the question both surfaces open with. Repeatable rather than a single value with a nullable default, because a nullable default has no wire spelling: outcome= and outcome=null are both enum errors, so "every outcome" would have been unaskable over HTTP and reachable only from Python.

A FAILED check with no surviving risk is returned as FIRED_NO_FINDING rather than dropped. The findings a check produces pass through obsolescence deduplication and, for some companies, a confidence filter, and both drop dicts before anything reaches document_risks — so the rule a fire-rate ranking just put first can legitimately have fired with nothing to show. An empty flipper reads as the surface being broken; the answer reads as the answer.