Civicord · UK · Browse / Lancaster and Wyre

Lancaster and Wyre · E14001318 · North West · England · 74,992 electorate

Lancaster and Wyre

Mostly responding — The rounded HTTP response rate at the audit was at least 66%. This does not establish that campaign content survived. 2 of 3 sites responding (67%) · 0 unreachable · 0 redirected

What happened here

  1. What was recorded

    The April 2025 scrape recorded 3 candidate websites for Lancaster and Wyre.

    • Cat Smith — Labour Party — https://www.catsmith.co.uk
    • Jack Lenox — Green Party — https://jacklenox.com
    • Matt Severn — Liberal Democrats — https://www.lancsmorelibdems.org.uk
  2. What the audit found

    On 7 September 2026 those URLs were requested again — 1 answered with the surname absent, 1 answered, 1 with another HTTP result. An HTTP success means the server answered. It does not establish that the campaign page survived.

    • Jack Lenox — https://jacklenox.com — Answered (HTTP 200).
    • Cat Smith — https://www.catsmith.co.uk — Audit result: HTTP error (HTTP 403).
    • Matt Severn — https://www.lancsmorelibdems.org.uk — Answered (HTTP 200). The surname was not in the response body. That asks for review; it does not prove the site was repurposed.
  3. What happened to the words

    A homepage fetch was compared with the April site text for 2 of the 3 candidates here. A sentence missing from that fetch is not matched to a replacement.

    • Jack Lenox — 9 sentences from the April text were not found on the homepage fetch of https://jacklenox.com. Example from the April text: “Contact Jack Fill out the form below to get in touch with me: This website is now archived – thank you to all who supported our campaign for the 2024 general…”
    • Matt Severn — 261 sentences from the April text were not found on the homepage fetch of https://www.lancsmorelibdems.org.uk. Example from the April text: “Examples of the way we may use your data include to: For more specific information about how we use your data for these activities, and the legal basis on…”
  4. Text overlap, where it was scored

    A separate Wayback comparison scored text overlap for some candidates. It kept the score and an archive URL.

    • Matt Severn — Substantial text difference from the compared archived page against the 19 April 2025 archive. 30% of April tokens were still found. Sentence text for this comparison is absent from the snapshot. · Open the archive

No replacement sentence is matched. A line that only appears on the later homepage is listed on its own. 1 candidate on this seat has no sentence comparison in the snapshot.

Lancaster and Wyre — 2 of 3 sites responding (67%) · 0 unreachable · 0 redirectedHalftone: more / larger paper dots = lower response rate.

Candidates in this seat

Respondingjacklenox.com

Jack Lenox · Green Party

  • HTTP 200
  • Candidate-name signal: surname matched in the response body (heuristic only)
Open filtered ledger — 3 sites ↗See what you followBrowse all 2,375 ↗UK overview ←

This link encodes the seat view · Press ⌘K to jump anywhere. This seat's hex is equal-weight (Automatic Knowledge v5, OGL) · How we checked →

Agent viewInspect the data and verify the record$0.002 / seat

Humans read this page for free. Agents pay per jurisdiction — this exact record is one metered call. Everything below is live; nothing here is mocked.

1 Free, same-origin

/api/constituencies/lancaster-and-wyre.json

Plain static JSON, CORS *, no key, 5-minute cache.

2 Metered via x402

https://civicord-aieyq.bazgateway.com/api/constituencies/lancaster-and-wyre

One jurisdiction = one charge. Expect 402, not an error.

3 MCP tool

Same call, as an agent would invoke it over MCP.

getConstituency(slug="lancaster-and-wyre")
-> { name: "Lancaster and Wyre", stats: { sites, live, livePct, ... }, candidates: [ ... ] }

4 The Graph (live)

On-chain p2618.civicord.eth via/api/graph (Studio proxy) — person id, not seat slug.

{
  candidate(id: "2618") {
    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

↑↓ move · ↵ open · Esc close