Speaker roster — Vigo County Budget Committee, 2026-08-24

No agenda was available for this meeting, and the vault has no closed-set roll-call membership list for the Vigo County Budget Committee to check against (the 2026-08-13 and 2026-08-12 sessions of this same body were never given their own speaker rosters). This roster is built entirely from transcript self-identification and direct address, per the archive's transcript-evidence standard. Only the 20 labels carrying substantial speech are resolved; the 209 sparse labels merged into <other> in the source transcript are out of scope.

Confirmed (3 labels / 3 people)

  • Steve — speaker_43 (canonical; merges speaker_44, speaker_178). Named by direct address 6 times across the meeting by four different other speakers, always addressing the flat-raise-vs-percentage argument this cluster carries throughout. Self-describes as an elected council member who votes on raises. Surname never spoken.
  • Judy — speaker_95 (canonical; merges speaker_394). Named or addressed three times across the meeting — once in third person immediately after explaining a stipend-grading point, twice by direct address — with the identity's own turns and its merged split both answering in character. Senior auditor's-office knowledge throughout. Surname never spoken.
  • Charles Johnson — speaker_434. Judge, Vigo County Superior Court Division I, also Chief Judge. Self-identified by name and title.

Probable (5 labels)

  • Steve — speaker_44, speaker_178. Diarization splits of the confirmed speaker_43 cluster (see merge_with); each carries a literal mid-sentence handoff to or from speaker_43 rather than an independent naming event of its own.
  • Judy — speaker_394. Diarization split of the confirmed speaker_95 cluster (see merge_with); carries one direct address answered with a personal, first-person detail only the addressee could supply.
  • Larry — speaker_207. Named twice by direct address, each time immediately after this label's own turn. Two namings, not three — kept at probable. Surname unknown.
  • Kevin Gardner — speaker_305. Outside compensation consultant, invited up by full name mid-meeting and referenced again afterward by first name. Two naming events, not three — kept at probable.

Role-only (12 labels)

Auditor's-office staff doing fund/stipend mechanics: speaker_52, speaker_55, speaker_145, speaker_675. Unnamed committee members / unclear function: speaker_3 (chair, by function — opens the session), speaker_42, speaker_74, speaker_191, speaker_192 (closes the session with the formal recess and addresses others by name, but is never named in return — a plausible chair or vice-chair, left unresolved), speaker_272, speaker_316 (addresses speaker_43 as "Steve" but is never named in return), speaker_487.

Two known diarization failure modes handled here

Split labels (same person, two-plus clusters), both merged on literal evidence, not topical similarity alone:

  • speaker_43 / speaker_44 / speaker_178 — a literal mid-sentence handoff recurs at least twice ("...the thought process would be rather than to do it by a percentage" [speaker_178, t=1928] continuing directly as "every county employee would get the exact same raise..." [speaker_43, t=1936]; "Also, while we're waiting for you to bring that up here, I spoke to Travis Norris, and" [speaker_178, t=3553] continuing as "he did indicate that he probably just assumed he'd keep the budget..." [speaker_43, t=3566]) plus a request-to-speak handoff ("Can we just talk openly? Can I just say what I would like to see?" [speaker_44, t=1893] immediately preceding speaker_43's flat-raise pitch [t=1901]).
  • speaker_95 / speaker_394 — each label is independently addressed as "Judy" and each answers in character on its own label (see the Confirmed section above), which is why these are merged as one identity rather than left as two separately-probable "Judy" labels.

Considered and rejected:

  • speaker_74 echoes the same page-by-page stipend-review style as the speaker_43 cluster but never shows a literal sentence-level handoff, so it was left unmerged rather than folded in on style alone — recorded here so the next reviewer doesn't have to redo the comparison.
  • speaker_3 and speaker_192 both perform chair-like procedural functions (opening and closing the session, respectively) but no literal handoff or naming event ties them together, so they are kept as two separate role-only labels rather than merged on function alone.