A Civic Legibility Audit · Columbia County, NYVol. I · Kinderhook Node · Pilot Edition
The Kinderhook Field Report
What the machines currently see when they look for the village — and what they don't.
Conducted by Harmonic Systems · Data read live from columbiacountytourism.org
Editor's Note
The web that's arriving is not only read by humans. Language models, search assistants, and agentic tools increasingly answer questions like "where can I get fresh produce in the Hudson Valley this Saturday?" — and they can only recommend what they can structurally read. A village whose institutions publish only prose will be invisible to that layer of the internet, no matter how much prose they write.
This is a civic legibility audit of Kinderhook, New York. It reads what machines currently see when they look for the village, notes what they miss, and publishes the schema.org markup that would close the gap. The concrete case we keep returning to is the Kinderhook Farmers Market — seasonal, volunteer-run, no standalone website — the exact kind of civic institution the new web is worst at discovering, and the one this project is built to make findable.
A Finding
Reading…
§ I · Ontology
How the county categorizes itself
/wp/v2/{taxonomy}
Before writing our own schema we read theirs. CCT publishes four taxonomies via REST. Each card below shows the full term list, county-wide, with any Kinderhook entries highlighted in cinnabar. The Kinderhook match count is what every later section filters against — if a taxonomy has zero Kinderhook terms, the village is invisible to that surface of the site.
Fetching taxonomies…
§ II · The CCT Footprint
Everything the county machine-readably knows
/wp/v2/search?search=kinderhook
Columbia County Tourism's full published index of Kinderhook, across every content type it exposes to search. This is the overview; the next four sections drill into each type in turn.
Querying…
§ III · Events
What happens in the village
/tribe/events/v1/events
Upcoming events at Kinderhook venues, read live from The Events Calendar. Each appears below as it would if a machine were asking the county what is scheduled here.
Fetching events…
§ IV · Event Venues
Places that host things
/tribe/events/v1/venues
A precise, narrow category: places in Kinderhook the county's event system currently recognizes as hosting events. Not the same as "places in Kinderhook" or even "businesses that could host an event" — a venue only appears here if something is scheduled in it.
Fetching event venues…
§ V · Editorial Record
What the county has said about us
/wp/v2/posts?categories=…
Articles tagged with this village by the tourism board's editors. A decade of travel writing, already categorized by place — an under-used affective layer.
Fetching posts…
§ VI · Independent Coverage
What journalists outside the establishment have written
schema/coverage/*.json
Hand-curated. Independent reporting on Kinderhook from publications outside the tourism board's orbit. Each entry is a citation, not a republication — readers click through to the original; the publishers get the traffic. The list grows by editorial decision, not by scrape.
Loading corpus…
§ VII · CCT Businesses
Everywhere CCT points in the village
/business/{slug}/ × 594
The biggest single drill-down: the county's full business directory, fetched page-by-page at build time from the Yoast sitemap, then filtered to our village by address. This is what CCT tells the world about Kinderhook when it lists businesses.
Loading snapshot…
§ VIII · Diagnostic
What the machines cannot see
(derived)
The county's data model has shape. This is what we found missing from the public surface — the specific gaps that make Kinderhook less legible than it could be.
§ IX · Cross-references
What the wider commons already knows
wikidata · overpass
Before we write new identifiers, we look for existing ones. Wikidata carries structured civic knowledge; OpenStreetMap carries the ground truth of named places. Both are authorities we can link to with sameAs.
Wikidata
query.wikidata.org/sparql
Querying…
OpenStreetMap
overpass-api.de
Querying…
§ X · Curated Places
What we have written
schema/places/*.json
The hand-kept corpus. Each entry is a JSON file under schema/places/, edited as a file, versioned in public, and loaded by this page at read-time. The county's data plus the commons' data plus these make a legible village.
Loading corpus…
§ XI · Historic Layer
Kinderhook as deep time already knows it
wikidata · wikipedia · loc
Before the URL slug, the village. Structured historical knowledge the commons has already written down, snapshotted at build time: NRHP listings, notable residents, Wikipedia summaries of the canonical sites, and two centuries of newspaper mentions.
Loading snapshots…
§ XII · Proposed Schema
What we would publish instead
schema.org · JSON-LD
Given what's already there, and the village-local judgement we add, here is the JSON-LD that would make the Kinderhook Farmers' Market correctly addressable by language models, assistants, and the next generation of discovery tools.
Awaiting data…
Every item above could carry one of these blocks. The taxonomy is the county's; the disambiguation and local judgement is ours. The machines stop guessing.
What We Ask
Five concrete things that, if implemented by the parties named, would close the largest legibility gaps in this report.