Pins, attested figures, receipts, and gaps.
avonlake.city publishes reviewed public-record pages. Derived figures are calculated at build time, checked against a pinned figure file, and refused when they drift; attested figures are human-pinned and labeled. Claims carry receipts; missing public links are marked rather than dropped.
Site reading doctrine, then case evidence bands.
Site-wide, six reading registers frame how claims are kept apart — what residents asked for, what officials said, what council voted, authorized vs paid, what happened, and what we can’t show. They are editorial doctrine shared with About, not six separate database tables. On the ALERG case file, the evidence bands are four independent registers (mentions, votes, declared recusals, and stated unknowns), each assembled separately so co-occurrence is not treated as connection.
A changed number fails the build.
Public figures are derived from the local archive at build time and compared to a pinned figure file. Any difference raises before HTML is written. Updating a pin is a reviewed rebuild, not a silent overwrite at publish time.
Two kinds of public figure, labeled.
Derived figures come from the database bundle — deed counts, roll-call coverage, declared-recusal counts, corpus group totals. The pin checker regenerates them and refuses drift. Attested figures (for example the planned TIF purchase display or brownfield grant display) are human-pinned, rendered verbatim, and never rewritten by an automatic pin refresh. Where a page shows attested money or acreage, it marks Attested next to those figures so a reader can see which numbers a person locked and which the pipeline measured.
“No public link” is part of the record.
Where a matched document carries a reviewed public URL, the site links it. Where it does not, the receipt list keeps the document title and marks No public link instead of dropping the row. Source-group landing pages follow the same rule: a reviewed upstream landing renders a link; an intentional gap renders an honest marker. Hiding the gap would invent coverage the archive does not have.
Measurement windows are named out loud.
Each derived figure prints with the snapshot date it was measured against — for example the corpus scan date or the votes materialization date on the case file. A page that says “verified 2026-08-01” is naming that measurement window, not claiming the upstream agency stopped changing afterward.
Point at the document the claim disputes.
Corrections are 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. When a derived figure is wrong, the archive or derivation is corrected and the site is rebuilt against the pin; when an attested figure is wrong, the human-pinned value is edited and reviewed. A dedicated corrections mailbox is not published yet; until one is, cite the receipt URL in any report so the disputed document is unambiguous.
Named boundaries.
- No owner names, contact fields, or parcel valuations in the build data — a privacy gate refuses those keys before render. Aggregate pages and reviewed case tables may still show public identifiers that are already on the open record (for example seed parcel numbers).
- No private review queues, internal dashboards, or unpublished conflict registers.
- No donor names or contact details and no unverified personal ties presented as findings.
- No allegations. Co-occurrence of names in the record is never presented as a connection.
- Deferred work (for example campaign-finance joins on the ALERG file) stays listed as a gap until it is gated and receipted.
See also About the project · Source catalog · ALERG case file.