This page reads directly from the same database that tracks Track A (park classification) and Track B (PAC formation). Nothing is staff-only here — the same public transparency this whole formation effort asks of the Chicago Park District, it holds itself to first.
How this stays honest. Every table below has exactly one way a row can change: a database trigger that fires on every insert or update and permanently snapshots the full new state into the ledger before anything else happens. There is no code path — staff tool, admin panel, or direct database edit — that can change a record without also writing its version. Updating a record and covering your tracks are, by construction, the same number of steps: infinite.
The two live determinations
Track A and Track B are each asking CPD one core question. Their current status, cross-linked to each other, live:
Loading live determination status…
The ledger
Every insert and every real update, newest first, across determinations, boundary maps, the document catalog, and (once any exist) board resolutions.