Civicord · UK · Browse / Liberal Democrats / Nottinghamshire Police / David Watts
Campaign site for David Watts (Liberal Democrats — Nottinghamshire Police), scraped April 2025, audited September 2026.
Snapshot audit, not a current availability check. HTTP success and surname matches do not prove campaign content survived. On-chain fields are on Sepolia testnet; full content is not stored on-chain.
URLs responding — David Watts's recorded URLs returned successful HTTP responses at the 2026-09-07 audit. This does not establish that campaign content survived.
Liberal Democrats: 70% responding across the party · this candidate: responding.See the cohort ↗
Stood in Newark — 2 of 4 sites responding (50%) · 2 unreachable · 1 redirected
Also stood in: Nottinghamshire Police, Stapleford & Broxtowe Central
April site-wide text vs the 2026-09-21 homepage fetch of http://davidwatts.org.uk: 0 sentences still present, 1 no longer found, 8 new. These are candidates for review, not proof a sentence was withdrawn.The April text covers the whole scraped site; the later text is one homepage fetch. A sentence can be missing from that homepage and still exist on another page. A missing sentence is not matched to a replacement.
This page uses frames but your browser does not support them.
Gap: no replacement sentence is matched. The April text covers the whole scraped site; the later text is one homepage fetch. A sentence can be missing from that homepage and still exist on another page.
If a URL, name, or sentence on this record is wrong, send a sourced request. It is queued for a person to review. It does not change the audit, the April scrape, the sentence comparison, or the Sepolia record.What is verified, and what is not.
Requests stored for this record. A request is not an edit.
If you are David Watts or work on their campaign, you can claim this record. Say how a reviewer could verify it — a campaign-domain email, a link on the live site, or your Democracy Club profile. A claim is queued for a person to check; it grants no edit access and changes nothing until verified.
What changedHTTP response recorded; inspect the candidate-name signal below
These are short excerpts from the April 2025 scrape, not the later wording and not complete archived pages. Original filenames identify the stored extracts. Browse the Campaign Lab source dataset ↗
| Page | Chars | Opening excerpt |
|---|---|---|
| content_1.html | 61 | This page uses frames but your browser does not support them.… |
The audit ledger above is a static snapshot. The buttons below run live queries against The Graph and the ledger JSON — only when you click them. Nothing fetches automatically and nothing here is mocked.
/api/candidates/2132.jsonStatic audit record — websites, status, ENS hint.
Preferred agent tool — live Graph + ledger verdict.
compare_onchain_to_ledger(id="2132")
-> { onchain, ledger, verdict[] }On-chain p2132.civicord.eth via/api/graph (Studio proxy) — person id, not seat slug.
{
candidate(id: "2132") {
id ensName status url personName textRecordCount
registeredAt registeredAtBlock owner
}
_meta { block { number } hasIndexingErrors }
}Live queries run on demand; a failure is shown honestly, never replaced with a cached response. Verify independently: ENS ·resolver ·Subgraph Studio ·/api/graph ·openapi.yaml ·source