A living, cited, forkable model of the rules and money that touch a home in Pingree Grove. Built for the people who live here first, and for the staff and officials who run it. Every study leaves a public dataset behind.
A single lot in Pingree Grove sits under six layers of authority at once. This series maps them, publishes the map, and then follows the money and the decisions that flow through them. Read it on the flat page below, walk it in the Grove sim, or fork the raw data.
The full Rules Stack corpus, the stacked regimes and every cited rule that governs a home here, published as a versioned, hashed, CSV and JSON download. A v1 curated slice, not an exhaustive codification.
Why it is useful. A resident can see every layer that governs their lot in one file. Staff and officials get a machine-readable map of their own authority stack. Anyone can fork it.
The property-tax bill split across the taxing bodies that share it: county, township, village, fire and library districts, the school district, the community college, the forest preserve, and the SSAs. Sourced from the Kane County Clerk tax computation report and the Comptroller Warehouse.
Why it is useful. The single most-asked resident question, answered with cited figures. Officials get a clean levy-share benchmark against neighboring bodies.
A structured, searchable log of the ordinances and resolutions the Village Board adopts: what changed, when, and the source document. Fed by the standing monthly records request in the FOIA log below.
Why it is useful. What did they decide about X, without reading every packet. Staff get a clean adopted-actions index.
Building and occupancy permits over time: type, area, and timeline. Requested in native machine-readable format under Illinois FOIA, de-identified before publishing.
Why it is useful. What is being built near me, and how fast is the village growing. Staff and officials get a permit-trend series they can plan against.
The full Rules Stack corpus, published as a versioned, hashed download. Every rule keeps its citation and a link to the source of record. This is a v1 curated slice, not an exhaustive codification of village law, and it grows as the corpus does.
Lawrence, J. (2026). Pingree Grove Studies: the rulebook, as open data (v0.1.0). jakelawrence.xyz/research/pingree-grove.
The sourcing, in the open. Every records request this series files is published here with its Illinois five business day clock (5 ILCS 140). Nothing here transmits a request: the log tracks the queue, and sending stays a human act. Right now every request is drafted, awaiting a send.
All ordinances and resolutions adopted since 2026-01-01, with adoption date and subject, in native electronic format. Standing monthly request.
The self-updating-corpus request from the roadmap FOIA kit (5 ILCS 140). Drafted and published openly; awaiting a human to send. Feeds the board-decisions thread.
The following GIS layers as shapefile or GeoJSON with attribute tables: zoning, parcels, corporate boundary, SSA boundaries, floodplain. Include the layer metadata / data dictionary.
Non-commercial request. Parcels and footprints are already in /grove/map from the open portal; this asks for the layers not on the open portal.
All building and occupancy permit records issued 2023-01-01 to date, including parcel ID, address, permit type, status, and dates, in native machine-readable format (CSV or XLSX).
Non-commercial request for existing records in native electronic format (5 ILCS 140/6). Feeds the development-pulse thread. Drafted, not yet sent.
Public records only. Nothing here is private data about a resident. Thread 1 re-publishes the existing, cited corpus behind /rules; it does not add facts, it makes the facts already on the page downloadable.
A curated slice, not a codification. The corpus is a v1 selection of the rules that matter most to daily life here, each linked to its source. It is not the complete village code, and the conflict layer stays conservative: it names sources rather than declaring a rule unenforceable, except on the two confirmed, human-verified state and federal overrides.
Planned threads carry no invented numbers. The money, board, and development threads are registered above but ship figures only once they are sourced from the real documents named in their provenance. Until then they hold a plan, not a result.
Recompute it, or it is not true. The counts on this page re-derive from the download, live in your browser and in the test suite. If they ever disagree, the build fails.
I design and ship AI tools, full-stack apps, and data pipelines — end to end, to production. Tell me the problem in a sentence; I'll give you an honest read on fit within a day.
Work with me →