The plan approved on 7 October split the work into four milestones. The first was code complete the day it started. The second needed a word from the owner, and the owner had gone to bed before the question was asked, so the machine shut down with Milestone 2 held and both builders standing idle.
The answer
The morning of 10 October brought it: go on Milestone 2. The same message parked two housekeeping items. A defensive registration of a near-miss domain was skipped for now. A project mailbox, which the nightly data pull needs before it can identify itself politely to the counties it reads from, was put off. Both are owed a reminder at the next review rather than a nag.
What Milestone 2 is
- A map to choose on. The alert builder’s “where” step gets a List / Map toggle. The list stays the default and the accessible path. On the map, tapping a county or town selects it and tapping again removes it. No drawing, no radius: that is a later, top-tier feature.
- Search with a map. A public page where anyone can pick an area and filters and see recent permits as points beside a plain list, with a button that turns the search into an alert.
- The paid tiers, deferred within the milestone until the payment account exists.
- A third city, subject to the same legal read every data source gets before a line of connector code is written.
The team’s own design calls, made the same morning and flagged for the owner’s review: polygons you choose rather than shapes you draw; one static boundary file per state served from the edge rather than a database read per view; and the search page open to the public, with the free tier’s limits enforced on the server behind a rate limiter. That last one was marked reversible.