How the record is read.
avonlake.city is a resident-built public-record project for Avon Lake, Ohio. It collects public documents — budgets, council minutes, deeds, filings, environmental reports — into one archive, reads them with software, and publishes what the record documents. Every figure on the site derives from that archive through publication gates and is pinned against silent change; every claim carries a receipt and a stated limitation.
Kept separate on purpose.
What residents asked for
The stated needs and requests on the public record — not our summary of them.
What officials said
Public positions and commitments, quoted, with the meeting or release they came from.
What council voted
Ordinances, resolutions, and roll-calls — who voted how, and who was excused.
Authorized ≠ paid
Authorization, contract, payment, reimbursement, and delivery stay separate states.
What actually happened
What has been built, removed, or delivered — measured against what was promised.
What we can't show
The gaps, truncations, and undeclared ties are part of the record too — so we name them.
For pins, attested labels, gap markers, and snapshot dates, see How to read this site.
Documented facts, with their receipts.
Figures on this site are generated from the archive at build time and recorded in a pinned figure file; a build fails rather than silently changing a published number. Where a record carries a public upstream URL, the site links it; where it doesn't, the site names the document and marks the missing link as a gap. The source catalog lists every source with its record count, last run, and snapshot freshness — including failures.
Named limits.
- No per-property values, owner names, or other resident-level detail — public figures are aggregates only, enforced by a privacy gate at build time.
- No allegations. The site states what documents contain and preserves uncertainty; co-occurrence of names in the record is never presented as a connection.
- No undocumented claims. If a figure can't carry a receipt and a limitation, it doesn't go on a page.
- Weak or ungated evidence stays unpublished — a named gap is honest; an inflated count is not.
Point at the document the claim disputes.
Corrections are always welcome. Every material claim is written to carry a receipt, so a correction can name the page, the figure, and the upstream document it disputes. A dedicated corrections mailbox is not published yet; until one is, cite the receipt URL when reporting an error. Figure pins, attested vs derived figures, and gap markers are explained on How to read this site.
Resident-built, unaffiliated.
Not affiliated with, endorsed by, or operated by the City of Avon Lake or any named party. This project states documented facts drawn from reviewed public records and preserves their limits and gaps. It surfaces what the record contains; it does not allege wrongdoing.