How checks work
Governance checks share one parent Run and immutable per-artefact Results, but not every artefact uses the same parser, editor or scorer.
The check pipeline
- Fetch — HTTPS request to the expected file location
- Parse — content parsed per specification
- Assess — the artefact-specific evaluator records factual status and structured findings
- Score — the relevant fixed-text, Cookies observation, or Sitemap model computes a result where evidence allows
- Store — the immutable Result and current/last-good pointers are persisted under the parent Run
- Review — fixed text results may be opened in the durable Workbench; Sitemaps and Cookies use specialised surfaces
Check outcomes
| Status | Meaning |
|---|---|
| Present | A represented artefact was obtained and assessed; its score may still be low |
| Missing | The expected public artefact was not found |
| Blocked | Access was blocked, for example by a challenge/WAF |
| Error | Acquisition or assessment did not produce a usable current result |
A 404/missing result is not the same as a timeout, destination rejection, blocked response or other error. Flowpane does not convert every acquisition failure to score 0. Proposed changes are separate from this public observation pipeline.