# Speaker roster — Vigo County Oversight Board, 2026-02-02 Resolved against the transcript for [[Ledger/Meetings/2026-02-02-vigo-county-oversight-board.md]]. 20 of the diarization labels carried enough speech to attempt resolution; 34 sparse labels (of 54 total) were pre-merged into `` by the transcript provider and are out of scope for this roster. No agenda was available for this meeting, so this roster relies on transcript-internal evidence plus the prior roster resolved for this same body (`Ledger/Meetings/2026-06-25-vigo-county-oversight-board.speakers.md`). ## Notes for the highlight stage - **The chair is never named**, exactly as in the 2026-06-25 meeting for this body. `speaker_5` (opens the meeting, entertains and closes the minutes motion) and `speaker_189` (invites and directs public comment) are merged as one person on identical presiding-officer function — the two labels never overlap in time and no other label performs either function. Stays `role_only`. - **The superintendent is "Dr. Hensel," `probable`**, reusing the spelling the 2026-06-25 roster for this body settled on. This transcript's own ASR renders the name four different ways ("Hemswell," "Hemsall," "Himsel," "Himsell") and never cleanly self-identifies or is directly addressed by name early on; the grade rests on the same pattern as before — introducing and handing off to Gibraltar's "Jim," then giving the district-level options analysis in first person plural. `speaker_13` and `speaker_69` merge on repeated mid-sentence diarization splits during the option-by- option savings walkthrough. - **"Jim" (Gibraltar Design) splits into three labels this time** (`speaker_22`/`25`/`17`), consistent with the prior meeting's finding that the Gibraltar team fragments across several diarization clusters. `22`/`25` merge on clean mid-sentence splits during the technical presentation; `17`'s later brief financial confirmations during the Q&A are consistent with the same role and are not contradicted by any other label, but carry no direct textual splice, so the merge is kept at the same `probable` grade rather than promoted. - **Two board members carry a probable first name via a single naming event each, both independently corroborated by the 2026-06-25 roster for this body**: "Mark" (`speaker_36`, named in the third person by a fellow board member — a board member named Mark also seconds a motion in the prior meeting) and "Heather" (`speaker_75`, directly addressed by Dr. Hensel — a board member named Heather also makes a motion in the prior meeting). Neither reaches `confirmed`; both are real, evidenced best guesses per §12b and should render as probable names with `confidence: flagged` in any highlight that uses them. - **"Rick Burger," `confirmed`** — a public commenter who self-identifies by full name and states he is also a sitting Vigo County School Corp. board member, speaking today as a taxpayer. - **A second public commenter, "Marques" (`speaker_193`/`210`), is `probable`** on the chair's direct address alone ("Mr. Marques, come on up.") — no self-identification recovers a spelling, so this is the chair's best rendering of the name, not a verified one. - **A short staff cluster (`speaker_213`/`216`/`208`) answers a budget- percentage question from the floor** but is never named; kept `role_only` rather than guessed as "Donna" (mentioned by a board member earlier in the meeting as the likely source of payroll figures) because no textual link ties this cluster to that name. - **`speaker_200` is a single ambiguous interjection** ("I used to be taller") with no textual continuity to any other label. Left unresolved rather than merged on a guess. - **No vote, accusation, or characterization of a third party is attributed to any `probable` name in this roster.** "Dr. Hensel," "Jim," "Mark," "Heather," and "Marques" are all probable-only; none casts a vote or characterizes a third party in the quoted material, so all may carry the probable name in highlight prose per §12b with `confidence: flagged`. No voice-match data exists for this meeting; all `basis`/`attribution_basis` entries are textual.