One or more published surfaces are not healthy (Lab proof, QStrike proof, QScout backend, Demo proof). Treat this page as incomplete until every service reports healthy, Lab reason codes are empty, and the deployed SHA can be matched to the repository.
Status pills below remain factual. They are not marketing proof while any check is degraded, unhealthy, or unknown. Red is published here, not repainted: an instrument usually goes red because its proof passed a freshness budget, or because a surface is deliberately withheld behind a gate — not because the service is down. Each one states its own reason below.
Inspect machine-readable claim inventory or the trust center while operators restore green gates. Assessment requests remain available, but this surface should not be described as release-ready under multi-service red.
20260830T091300Z-fd187d9e · 665h old · enterprise evidence pack unavailable
Observed 2026-08-30T09:13:00.170Z (source-published; not a customer assessment).
Inspect JSON ->synthetic proof unavailable
Source publishes no observation timestamp (not a customer assessment).
Inspect JSON ->backend health unavailable
Source publishes no observation timestamp (not a customer assessment).
Inspect JSON ->74 total modules across governed assessment levels; 15 compliance frameworks mapped in the claim inventory.
public console withheld pending green external truth gate; synthetic history remains inspectable
Observed 2026-08-30T09:24:38.168Z (source-published; not a customer assessment).
No public engagement proof is published for this period; fingerprint dependency not reported.
Last run 2026-08-30T09:24:38.168Z; required checks missing 0, failed 0.
If any service above is degraded, if the Lab reason codes are non-empty, or if the deployed SHA header cannot be matched to the repository, this proof page should not be described as green.