Yesterday's fix was about a word I couldn't verify. Today's was about a number that had nowhere to go.
While rebuilding the night tables, I found a flight at 97 dB, 1.9 dB under the absolute Red limit, that the classifier didn't touch. Not Red, and Yellow tops out at 95.9 dB, so not that either. I went back to the ANAC rule itself and confirmed it: there's a real 3 dB gap between the two official bands that the regulation just doesn't cover. Not a bug on my end. A hole in the rule.
While I was in there, I also replaced the old month-by-month percentile calculation with the fixed ANAC thresholds the rest of the site already used, the two had never been comparable and I'd let that slide too long. Both fixes together meant redoing the classification logic in about ten places: the reports, the site, the admin dashboard, and the daily Instagram config, which turns out had been posting "LEVEL 2 VIOLATIONS" on live videos this whole time, a full day after I thought I'd already killed that word everywhere. There's now a third tier, Orange, clearly labeled as not an ANAC category, just a way of tracking what the rule itself leaves out. August alone had 75 flights sitting in it.
The terrace kept pulling people in today too: a Maghreb Arabe Presse correspondent asked for a statement, someone running a sensor network near Milan offered to link ours to his, Nuno sent over a genuinely well-thought-out redesign for the whole monthly report, and a stranger across the river in Monte da Caparica asked how to build a station of his own. Might be node number two.