Every date on the book, soonest first: scheduled BOR hearings from the county case records, plus each parcel's effective filing window. A firm override always beats the county's published date, and every entry says which one it is.
Every county's math is different — Ohio runs a statutory 35% ratio with Board-outcome calibration, Pennsylvania runs per-county common level ratios that move annually, Illinois runs township multipliers. The rules are data, visible here, and editable with a name attached: an edit is recorded with full provenance and applied at the next onboarding build, never silently mid-cycle.
data/valuations.json not found yet.
out/cases/*.html not found yet.
Every Board of Revision case across the watch-list, from the county's own case system. The decided outcomes here ARE the calibration pool behind Module B's first-pass values. Filed paperwork opens in-app.
Drop an appraisal, complaint, decision letter, or evidence packet. The same deterministic extractor that processed the county's BOR paperwork reads it locally — nothing leaves the machine. The system proposes a parcel; nothing attaches until you confirm, and nothing touches the book until an analyst approves.
The learning loop: approved decision letters extend the per-bucket calibration pools. Extensions are recorded immediately; the book's first-pass values only move through the explicit, named recompute below.
Every uploaded document with the fields it produced and where each field came from.
The split happens the moment the book enters: each client+parcel pair is separated into an opaque reference and a key. The tool keeps only parcels and references. The key linking references back to clients exists once, in the response handed to you below — download it, it is yours, it is never stored. Not a promise not to look: there is nothing on the tool's side that can name a client.
What the monitor ingests: parcel, county, reference. No names, because none were kept.
The audit trail: county scans and detected changes, firm uploads, parcel confirmations, and analyst approvals, newest first. A read-only view over the underlying records — nothing here can be edited, which is the point.
Detection without notification is a change nobody saw. Phase 2 delivers the alert layer, entirely inside the firm's network: a daily digest per domain owner (deadlines to Julie's queue, national-group changes to Brendan's), urgency tiers keyed to the days remaining on each window, and an escalation rule when a watched parcel's value moves inside an open filing window. Every alert links back to this History feed — the alert is a pointer to the record, never a copy of the data.