Sources · Provenance
376 harvested meeting records across 25 jurisdictions, 2024-01-04 through 2026-08-11. Every reading lists its sources in line, and every claim carries a citation chain back to the original document on the city’s own portal.
Source documents come from each city’s own portal. Some cities use municipal CMS platforms (CivicClerk, AgendaCenter); others publish PDFs directly under municipal subdirectories. The harvest pipeline reads where the city posts.
| Jurisdiction | Records | Portal | Platform |
|---|---|---|---|
| Clermont | 35 | docs.clermontfl.org | Laserfiche |
| Leesburg | 33 | leesburgflorida.gov | Direct HTML directory |
| Winter Park | 31 | ||
| Minneola | 29 | minneola.us | Direct HTML directory |
| Groveland | 24 | groveland-fl.gov | CivicEngage / AgendaCenter |
| Kissimmee | 19 | ||
| Mascotte | 18 | ||
| Winter Garden | 17 | ||
| Mount Dora | 16 | ||
| Eustis | 16 | ||
| Lake County (Unincorporated) | 15 | ||
| Apopka | 13 | ||
| Ocoee | 13 | ||
| Lake Wales | 13 | ||
| Orlando | 12 | ||
| Tavares | 12 | ||
| Haines City | 12 | ||
| Maitland | 11 | ||
| Sanford | 10 | ||
| Davenport | 9 | ||
| Montverde | 8 | ||
| Lake Mary | 5 | ||
| Winter Springs | 3 | ||
| Altamonte Springs | 1 | ||
| Oviedo | 1 |
| Type | What it carries |
|---|---|
| Agenda packets | The board’s pre-meeting bundle — agenda plus each item’s staff report and supporting attachments. The richest single artifact per meeting. |
| Meeting minutes | Post-meeting record of motions, votes, public comment, and staff discussion. The authoritative account of what happened. |
| Staff reports | The planning department’s analysis of each item — the code citations, the comp-plan alignment, the recommended disposition. Often where the structural argument lives. |
| Ordinances | Adopted code language. The legal regime that governs the next decisions. Read in chronology — when an ordinance changes, the planning environment changes. |
| Comprehensive plans | Long-range policy framework — future land use maps, transportation elements, capital improvement schedules. The ceiling and the floor for what cities will approve. |
| Supporting attachments | Site plans, traffic studies, utility capacity letters, public comment correspondence. The evidentiary fabric the board reads alongside the agenda. |
The harvest output is one file per meeting, with a stable frontmatter contract for jurisdiction, board, date, and items. The shape is what allows the lens projection to read across cities without losing per-city texture. The text is plain Markdown; the metadata is structured. Every file is committable, diffable, and version-controlled.
Validation is human. Before any place dossier or signal brief ships, the citation chain is walked end-to-end — back to the source PDF, back to the video recording where one exists. Items are checked for vote tally, public comment, and outcome. When a citation breaks (URL rot, document withdrawn), the dossier holds and is reviewed; when a citation refines (a staff report supersedes a prior version), the dossier moves with it.
The source trail at the bottom of every reading is the visible receipt. The provenance graph in the underlying content is the structural one — document types per reading, ordered, with dates and source IDs that resolve back to this page.
AI agents reading the observatory get the same provenance. Every MCP tool response includes the citation chain. Every projection preserves its sources. The discovery surface is /.well-known/mcp.json; the long-form ingest substrate is /llms-full.txt; the index is /llms.txt.
Read the methodology for how the substrate is read. See a place dossier for what the discipline produces.