The workflow, end to end

Visitors and crawlers are being served an old copy of this page on supremefencingdenver.com

STALE_CACHE_SERVED is on 17.5% of all scans. This page is the chain for one real site: 8 of 10 steps on record. Every step is a link to the record that proves it; nothing on this page is a description.

JSON: /api/workflow · the three most common findings · generated 2026-10-07 16:48 UTC

1. 1

   Problem detected ✓ on record

   STALE_CACHE_SERVED on /, severity 2 — the copy served to us was built 1 hour 18 min ago

   the record before (A 87, 2026-09-02 01:26 UTC) · the finding explained · machine record

2. 2

   Exact evidence shown not yet

   evidence bundle · verification

   this record predates the artifact store (sealed manifests from 2026-09-20): the bytes it measured were not retained, so the finding cannot be re-located in them; its own evidence fields and the signed record are what remain

3. 3

   Fix recommended ✓ on record

   the generated fix (fixStaleCache) · the remediation plan

4. 4

   Impact projected ✓ on record

   projected grade with this fix (/api/impact) · what-if

   the grade formula rerun with this fix's rows cleared, computed from the before record, not measured

5. 5

   Implementation recorded ✓ on record

   Cloudflare HTML cache rule edge_ttl override 14400 to 1800 s (the origin sends max-age=1800), then purge_everything after a Varnish purge — declared by VSNARY (site owner) on 2026-09-02

   Held in the receipt’s declared_fix, inside the signed body.

6. 6

   Site rescanned ✓ on record

   the record after (A 87, 2026-09-02 01:33 UTC) · before vs after, field by field

7. 7

   Corroborated by a second observer ✓ on record

   every identity was served a copy under an hour old (max Age 2241 s): the fix holds from a second network

   the signed observation (gha-azure-1, 2026-10-07 13:55 UTC) · corroboration · observer registry

   identity	status	age_seconds	cache_status	fresh
   anon	200	1984	HIT	true
   gptbot	200	1984	HIT	true
   claudebot	200	1984	HIT	true
   oaisearch	200	1984	HIT	true
   claudesearch	200	2241	HIT	true
   perplexity	200	2241	HIT	true
   googlebot	200	1984	HIT	true
   browser	200	1	HIT	true
   control	200	1984	HIT	true
   bingbot	200	1	HIT	true
   applebot	200	2241	HIT	true
   amazonbot	200	2241	HIT	true
   bytespider	200	2241	HIT	true
   metaexternal	200	1984	HIT	true
   ccbot	200	1984	HIT	true

8. 8

   Signed remediation receipt ✓ on record

   rc1:1ed3c9cfc57e90b9c7ec… · download · verifies on this observer · node crawlcheck-verify.mjs receipt.json

9. 9

   Regression watch ✓ on record

   157 readings on 25 days since the fix; the finding has not come back · twice a day

   the certificate (recomputed daily) · newest record (2026-10-07, A) · every measured day (Evidence)

10. 10

    Business outcome tracked not yet

    computed on the owner's first read of /api/outcomes

    what the connected sources counted after the fix (owner)

Ten steps, each a link to the record that proves it. done:true means the record exists and says what the step claims; a step that is not done says what is missing. Nothing here is asserted without a record behind it.