Glossary
Evidence & handoff
Every actionable claim should point at inspectable evidence. Tickets are remediation-shaped views of findings.
Finding
A check result with severity, title, why/interpretation, confidence, and evidence payloads.
Severities: fail (UI Critical), warn (UI Warnings), info.
Confidence tiers: DETERMINISTIC · HIGH · MEDIUM · LOW — how strongly the harness trusts the observation.
On the report Alerts · Evidence
Evidence
Provenance payload: URL, timestamp, source, selector, snippet, headers, JSON, agent/rule fields when relevant.
If a claim cannot point back to evidence, it is not treated as trustworthy.
Evidence panes expose raw / snippet / json for inspection.
On the report Evidence section
Developer handoff tickets
Remediation tickets derived from non-info findings (fail → P0, warn → P2).
Tickets carry expected state, check id, and acceptance framing so engineering can act without re-deriving the diagnosis.
On the report Developer handoff
Measurement contract version
Schema/version tag for the report (currently 1.0.0). Bump when report meaning changes.
Compare runs only within the same contract version when tracking score deltas.
On the report Run details · Contract