3 Commits

Include renames

Author	SHA1	Message	Date
Logan CusanoandClaude Sonnet 5	241a15b8da	transcript_correction: reject a correction that changes a ten-code (#162) ... correct()'s prompt says "Do NOT expand ten-codes" and "NEVER add information", but nothing checked the model's output against its own rules -- raw["corrected"] was accepted verbatim past a non-empty/changed check, and the "changed" field it returns was logged for audit and never validated. Caught live: the same call's raw vs corrected transcript showed "10-7" rewritten to "10-13" in one place and "10-4" in another, plus a bare "7" expanded into "ShotSpotter" -- alongside genuinely good fixes (Holmes Street and 4th and Rowe -> Home Street and Forest Ave, from this system's own vocabulary). A wrong 10-13 standing in for a real 10-7 reads exactly as trustworthy as a correct transcript, which is worse than leaving the raw mishearing in place. _code_tokens() extracts every ten-code/signal-shaped token from the original and corrected text/segments; any change to that set discards the correction and falls back to raw. Checked independently for the joined text and for segments, consistent with the existing all-or-nothing segment-alignment rule. Does not catch a wrong word swapped for another equally plausible non-code word -- that class still depends entirely on the model following its own prompt. Filed server-26#161 for the broader STT/audio quality initiative this belongs alongside. Verified: 426 pass, 0 fail (4 new tests). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-20 21:51:41 -04:00
Logan CusanoandClaude Opus 5	964343c819	area_context v2 + Maps place verification (server-26#36, #37) ... #36 — the correction pass shipped in 58efdbd was right, its reference-data shape was not. One shape now, at both scopes, every field nullable: area_context: { municipality?, county?, state?, center?, radius_km?, resolved_from?, resolved_at?, local_knowledge?: [{term, meaning}] } `state` closes the ambiguity that made "Ossining" a national guess. `local_knowledge` replaces roads[]/landmarks[], which could not hold intersections, schools or nicknames and carried no meanings — `11-X-ray` is useless alone, `11-X-ray — MTA PD patrol unit` is what a corrector can act on. Pre-#36 roads[]/landmarks[] are read forward as bare terms so nothing an operator already entered is lost. Nullability is the mechanism: which scope gets filled is the operator's declaration of how homogeneous the system is. One town — fill it once at system level. Statewide — leave it blank and fill each talkgroup. The backend owns the derived anchor. PUT /systems/{id} merges config.talkgroups[] against what is stored instead of writing the client's blob verbatim, which would have erased the anchor and the pending queue — the same defect as the ten_codes wipe. #37 — Maps as a verifier, not as prompt stuffing. The corrector emits its location nouns; each is geocoded against the talkgroup's anchor, and on a miss we look for a sound-alike that does resolve there, correct to it, and propose {term, meaning} to that talkgroup. Cost scales with location nouns, not calls. No anchor means SKIP. An area too wide to discriminate stores no anchor at all, because a statewide radius would confirm anything inside it — verification that passes everything is worse than none, since it reads as a check in the data. Also re-anchors _geocode_location, which rejected results >40km from the NODE (server-26#6). An antenna is not a jurisdiction; distance-from-node was always a stand-in for the anchor and is now only the fallback. The induction loop proposes at talkgroup level and never promotes. Blast radius: a wrong term on a channel misleads that channel, the same term system-wide misleads one 400km away on a statewide system. 38 new tests; 240 pass. Frontend typechecks clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-23 16:43:59 -04:00
Logan CusanoandClaude Opus 5	58efdbd6eb	Correct the transcript before anything reads it ... Correction existed, but as a line in intelligence.py's EXTRACTION_PROMPT -- which put it in the wrong place twice over. The same model call that extracted units, location and severity emitted the correction afterwards, so extraction reasoned over text already known to be wrong; and it sat behind correlation_enabled, so during a cost-controlled STT-only window nothing was ever corrected at all. That is the normal state during development. internal/transcript_correction.py is now its own pass, between the degenerate filter and the Firestore write. It receives an already-produced transcript plus a reference list, so unlike a Whisper prompt it has no series to extend -- the distinction that keeps vocabulary out of the recogniser's prompt, where an enumerated ten-code list once made it hallucinate ten-code runs. Reference data is merged from the talkgroup and the system, TALKGROUP FIRST. A system spanning several counties can have a talkgroup covering one municipality, and that municipality's streets must not be buried under a county-wide list. A single-municipality system is the degenerate case: populate the system level and every talkgroup inherits it. Area context is now SET -- municipality, county, roads, landmarks, on both scopes -- rather than guessed from talkgroup names, which is what vocabulary_learner did and which is close to useless across multiple counties. Segments are corrected too, not just the joined text. extract_scenes builds its prompt from numbered segments whenever there is more than one, so a correction that only fixed the transcript would have been discarded on exactly the multi-transmission calls carrying the most content. Alignment is enforced: an array of the wrong length or type is dropped whole, because scenes map back to transmissions by index and a shifted array would misattribute audio silently. Whisper is also retried once on degenerate output. Call e49ea32c produced a 56-word ten-code counting run on one attempt and ordinary speech on the next -- same clip, same temperature=0 -- so a hallucination is a coin-flip, and discarding on the first bad roll threw away a recoverable transcript. Two things found on the way: PUT /systems/{id} wiped ten_codes on every save. The systems form sends only {name, type, config}, and model_dump() wrote every omitted field as its default over the top. Now exclude_unset. area_context would have been the next victim, which is why it gets its own route alongside ten-codes rather than a field on that payload. Closes server-26#36. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-23 14:23:41 -04:00