Every finding quotes the reviewed content. This page is the pipeline, the evidence rules, and what a run does not see. The pre-deploy report documents this site as it stood before those findings were fixed. The previous version of this site has its own archived report; its receipts live inside it.
Headless Chromium loads each page, same-origin and bounded, respecting robots.txt during discovery. It keeps the rendered DOM and a behavior log: network requests, storage writes, console errors. Single-page apps are read after JavaScript runs. Source mode skips the crawl and reads a repo instead.
Exact-match passes run first: crawl errors, placeholder hrefs, draft remnants, head-metadata gaps, duplicate titles. No model involved.
Four AI reviewers, each holding one lens: cold stranger (first visit, thirty seconds of patience), skeptical buyer (assumes shilling until shown otherwise), detail nitpicker (pre-launch sweep), register keeper (every sentence must be for the visitor). Each lens reads independently. Agreement is recorded, not assumed.
A separate pass re-reads every candidate against the cited content and tries to refute it. Misquoted, overreaching, or fine-in-context candidates die. Confirmed findings get corrected line numbers, a severity check against fixed anchors, and a fix note for a coding agent. The runner then mechanically re-finds every receipt; a finding whose receipt cannot be re-found is dropped.
Canonical markdown: stable SG-NNN IDs, verbatim receipts with paths and line numbers, fix scopes, a rollup by failure class. HTML is rendered from that markdown, with copy-for-agent buttons.
Seen: rendered pages in a real browser; network requests and their payloads; storage writes; console errors; source, when you point SlopGuard at a repo.
Not seen: anything behind a login; form submissions, purchases, or any interaction beyond navigation; external facts, which are flagged for you to check rather than asserted.
A free self-serve scan at /scan/ is kept about 24 hours, then deleted. A queue run, or a run we perform ourselves, is kept as history so runs can be compared; that history stays private unless you publish it, is never sold or used for training, and is deleted on request.
SlopGuard is scored against a plain “review my site” chat prompt on identical targets: confirmed-finding precision and trust-killer recall. If receipt-verified findings do not clearly beat a free chat prompt, SlopGuard has no reason to exist.
Round 1 · 2026-08-09, this domain’s previous site. A real ChatGPT session with browsing quoted the site accurately and caught the copy’s repetitive cadence. It surfaced none of the five verified trust-killers in the archived report, praised the affiliate disclosure that run proved false on the page where it sits, and reviewed a different company’s website on its first attempt. The session transcript is not published, so treat this round as our account, not a receipt. Round 2 runs on the queue’s first external site.
This Hexento surface gets a SlopGuard run before it ships. The 2026-08-09 rebuild run found 22 verified defects, 6 of them embarrassing; the report is public and those findings were fixed before that ship. A rerun on the fixed pages found 14 residual findings, none trust-killers; that report is public too. The 2026-08-13 pass on these rebuilt intake pages found 21 more verified defects, one trust-killer among them; that report is public and the findings were fixed before this ship. Each report documents the site as it stood when its run ran. If we skip our own tool, the tool dies.