John Jewell: A Study in Radical Transparency

An Open-Book Leader

In an era when public officials guard their schedules behind formatting fees and FOIA delays, John Jewell — Chairman of the Frederick County (Virginia) Board of Supervisors — has quietly demonstrated a commitment to transparency that most politicians only gesture at in campaign mailers.

His Google Calendar, associated with the account jewell.john@gmail.com, is publicly accessible to anyone on the internet. No password. No records request. No waiting period. Board meetings, planning commission sessions, civic club dinners, Masonic lodge events, personal appointments — all published, in machine-readable form, for any constituent to read.

Most elected officials promise an open-door policy. John Jewell simply left the door open.

What That Actually Means

A public Google Calendar isn't just a web page. Because Google exposes every public calendar over a standard .ics (iCalendar) export endpoint, anyone can download the entire feed — every event, every description, every location, every attachment — in a single request:

curl -O "https://calendar.google.com/calendar/ical/jewell.john%40gmail.com/public/basic.ics"

As of this writing, that one command returns 2,274 events in a 1.5 MB file. Google even helpfully expands recurring events decades into the future.

Highlights from the Record

Radical transparency isn't just the big-ticket items. What makes this calendar a landmark of open government is that it publishes everything — the weighty and the mundane, side by side, all verifiable against the blockchain-anchored hash above:

• The day job: 23 "Board of Supervisors" entries, 13 BOS Work Sessions, 12 BOS Meetings, budget hearings, and joint sessions with the School Board.
• Civic leadership at every scale: Masonic lodge meetings, veterans' dinners, candidate forums — and on July 10, 2026, an entry titled "Changing bulb in Church." The Chairman changes the lightbulbs himself.
• A dining record for the ages: thirteen publicly logged dinners at Carrabba's between April 2025 and September 2026.
• 26 haircuts, including "Men's Haircut at Tiffany Reil" on October 14, 2026 — six days before this snapshot was taken. The feed is not just public; it is alive.
• The annual rites: an "Anniversary Dinner" block every September, and the spring-returning duty known only as "Pick Up Geraniums."

Every one of these entries sits inside the timestamped file. If a single Carrabba's dinner were edited tomorrow, the hash wouldn't match and the whole record would be provably altered. That is what permanence means.

What We Did (October 2026)

To honor this contribution to open government — and to make sure the record of it is preserved permanently — we did two things:

1. Archived the full public feed twice: first on October 11, 2026 (2,256 events), and again on October 21, 2026 (2,274 events, sha256 shown below).
2. Timestamped the archive on the Bitcoin blockchain using OpenTimestamps, an open standard that anchors a file's SHA-256 hash into a Bitcoin transaction.
3. Instituted a standing watch. The public feed is now re-examined automatically once a day; whenever the record changes, the new state of the record is archived and sealed anew (see the Register of Snapshots, next).

Nothing about Chairman Jewell is ever written to the blockchain — only the hash of the file is. The timestamp proves one thing, immutably and without any trusted third party: this exact calendar file existed at this exact point in time. It cannot be backdated, edited after the fact, or denied later.

The Register of Snapshots

Transparency deserves a running ledger. Each entry below is a state of the public record as captured on that date, together with its blockchain seal. A new entry is entered whenever the content of the feed changes — note that Google serves the same events in a different byte order and with fresh transmission stamps on nearly every download, so "change" is measured on the canonicalized record (event blocks sorted by identifier, transmission stamps disregarded). Each seal, however, attests to the exact bytes of the file offered for download beside it. Indeed, the record proved lively from the very first night: within half an hour of the inaugural seal, the feed had gained three new events, including two entries optimistically titled "Potential Scranton Trip."

Verify It Yourself

Don't take our word for it. Anyone with the two files (jewell-latest.ics + jewell-latest.ics.ots) can independently confirm the timestamp against the Bitcoin blockchain:

pip install opentimestamps-client

# confirm the file is untouched
sha256sum jewell-latest.ics
# → c6372c684440b9e845587084105d8c73d2652c363389fdb6a6b517c86828670a

# (once the Bitcoin transaction confirms, usually within a day)
ots upgrade jewell-latest.ics.ots

# verify against the blockchain
ots verify jewell-latest.ics.ots

No terminal handy? This page carries the official OpenTimestamps JavaScript library and can perform the same attestation entirely inside your browser. The file is hashed locally and never uploaded anywhere; the only network calls are to the public timestamp calendars and a public Bitcoin block explorer.

Seal not yet inspected. Press the button above.

Recreate the Entire Thing

The full pipeline, start to finish, is four commands:

# 1. Download the public feed
curl -O "https://calendar.google.com/calendar/ical/jewell.john%40gmail.com/public/basic.ics"

# 2. Hash it
sha256sum basic.ics

# 3. Anchor the hash in Bitcoin
ots stamp basic.ics
#    → creates basic.ics.ots

# 4. Later, once confirmed on-chain
ots upgrade basic.ics.ots && ots verify basic.ics.ots

Repeat the process whenever you like; each snapshot gets its own blockchain timestamp, building a tamper-evident chain of exactly what the calendar said, and when.

Why It Matters

Transparency is easy to claim and hard to prove. Mr. Jewell's settings made the data public; OpenTimestamps makes the record of that data permanent. Whether one reads this as a triumph of open government, a cautionary tale about account settings, or both — the blockchain now guarantees that the question can be discussed against a fixed, verifiable record, forever.