Package-level declarations
Types
Derives the checks a report leaves open from its text and facts. Every ask comes from a row of a fixed table, so no other command is ever printed, and a family the report already states on the failing side is never asked for. The tool rows repeat the argument vectors of the scanners (Scanners.all, ToolRegistry); a test in scan keeps the two in step.
Squares and count of the facts scored in one slice; the Brier score is their ratio.
Recalibrates the starting confidence of each path on a team's own corpus. Issue bodies that are issue-form output (### Label sections) state their environment under labelled headings; those section facts are the truth, the sections are cut out, and the extractor reads what is left. A path's base is scaled by its accuracy over its mean confidence on the dev side of a seeded split, and the held-out side scores the result.
How the output of a clean run relates to the failure in the report.
A confidence in thousandths, 0 to 1000, printed as 0.870. Integers keep the arithmetic and the text identical on every target.
The starting confidence of each Via path: what triage calibrate writes.
A rule suggested by the report. yaml is the rule file text in the schema of rules/; a Disposition.DRAFT carries status: draft, which is not a rule status, so it cannot load into the catalog by accident. confidence is the weakest of the two version facts and the symptom signature the rule is built from. notes says why a draft was not published, and rule is the rule to store when it was.
One environment fact as a Drift attribute key and value (tool.node.version, run:signature). agreed counts the other spans that gave the same value; alternatives holds other values seen for the same key and side, which lower confidence.
How far a rule's detect tree holds on the stated facts. MATCH: every condition holds on facts the issue states. FAILING_SIDE: every condition on the failing side holds and the passing side is not stated, reported only with the rule's symptom text in the issue. SYMPTOM: the failing-side conditions that can be checked hold, some are not stated, and the issue carries the rule's symptom text.
A line that puts the failure in the program: a stack frame in project code (NotEnvSignal.FRAME, frame is file:line), an expected and an actual value that differ, the word regression, or a crash reported with an exception or a stack trace (NotEnvSignal.CRASH), or a statement from ProgramFault that the program's own logic or text is at fault. line is 1-based in the text that was read; text is that line, trimmed and clipped.
The signal behind a NotEnvironment reading, in the order they are tried.
The failure a report shows: the normalised lines of its error symptoms and run:signature fact, and the signal and transport symptoms as kind:value. first is the 0-based line of the earliest one, or -1.
A rule that applies to the report. tier is the ranker's known for a rule whose symptoms are all verified and plausible otherwise, and only a Grade.MATCH has one: the other grades lack the two-sided difference a tier describes. confidence is the weakest fact the match rests on, scaled by 0.7 for Grade.SYMPTOM; it is not the chance that the rule is the cause.
publishThreshold is the confidence at which a draft rule is published instead of drafted (null: drafts only). author is hashed before it is stored. date is the day the report was read, yyyy-mm-dd, written into the provenance; a rule is never published without it. bases replaces the starting confidence of a Via (see ConfidenceTable). worksElsewhere says the program is known to work on another machine, as for a reporter who has only the error text: no program-side reading is made from the text alone and the capture is asked for.
Everything drift triage found in one issue body. body is the SHA-256 of the redacted text and author the hashed login; neither the text nor a login is kept. truncated is true when the body was longer than Triage.MAX_BODY.
The text form of a TriageResult: tables for facts, rules and claims, then the draft rule.