Civicord · UK · Browse / Green Party / Chelmsley Wood / Shesh Sheshabhatter

Campaign site for Shesh Sheshabhatter (Green Party — Chelmsley Wood), scraped April 2025, audited September 2026.

Shesh Sheshabhatter

View evidencePropose a correctionIs this your record? Claim itReply if this is wrongMore change stories ↗See what you followQuery The Graph

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 — Shesh Sheshabhatter's recorded URLs returned successful HTTP responses at the 2026-09-07 audit. This does not establish that campaign content survived.

Green Party: 80% responding across the party · this candidate: responding.See the cohort ↗

Stood in Meriden and Solihull East — 2 of 2 sites responding (100%) · 0 unreachable · 0 redirected

E14001358 · West Midlands · England · 74,211 electorate · Halftone: more / larger paper dots = lower response rate.

View Meriden and Solihull East ↗Filtered ledger — 2 sites ↗

Also stood in: Chelmsley Wood

  1. Apr 2025scraped
  2. Sep 2026audited
  3. PendingSepolia

Propose a correction

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.

Review queue

Requests stored for this record. A request is not an edit.

    Is this your record?

    If you are Shesh Sheshabhatter 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.

    Websites

    Respondinghttps://linktr.ee/sheshsheshabhatter

    What changedHTTP response recorded; inspect the candidate-name signal below

    • HTTP result: Responding (HTTP 200) at the 2026-09-07 audit
    • Candidate-name signal: surname matched in the response body (heuristic only)

    Source evidence and excerpts

    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 ↗

    Scrape excerpts — April 2025 · 1 shown
    PageCharsOpening excerpt
    content_1.html236
    Shesh Seshabhatter
Links to all my social profiles. Show your support by following each of them.
Instagram
Instagram
X
X…
    Agent viewInspect the data and verify the recordGraph live

    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.

    1 Free ledger JSON

    /api/candidates/81847.json

    Static audit record — websites, status, ENS hint.

    2 WebMCP join

    Preferred agent tool — live Graph + ledger verdict.

    compare_onchain_to_ledger(id="81847")
-> { onchain, ledger, verdict[] }

    3 The Graph (live)

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

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

    Jurisdiction

    Reading…

    Reading the public record…

    Reading /api/… — the same static JSON an agent pays for.

    ↑↓ move · ↵ open · Esc close