CivicLine Clerk · Local Government

Ingest a council recording or live stream. The agent transcribes it, then identifies each speaker through a two-layer process: first a voiceprint match against enrolled profiles, then LLM contextual inference cross-referencing the agenda and sign-in sheet for any speakers it can't match.

​

Structured extraction pulls attendance, motions with mover and seconder and full vote tally, public comment summaries, and a narrative body — written straight back to the official Minutes record. Every segment records how its speaker was identified, so the audit trail tells you why the agent thought the council member was who it said they were.

​

The certify step is the human approval gate. The agent drafts; the clerk signs.

Two tool calls cover the full workflow.

​

Process request searches across the local document index, your Microsoft 365 Exchange and SharePoint, and any other connector you register. It runs structured-citation redaction — PII patterns plus an LLM exemption classifier that cites the specific statute for every withholding. It drafts a cover letter that reflects the active state-level policy pack for your jurisdiction.

​

Release package is the approval gate. Admin role required, plus separation of duties — the approver cannot be the same person who initiated the action. On approval, the cover letter is signed via DocuSign or Adobe Sign, the request flips to released, and the envelope ID is stamped on the audit record.

Every morning, eight scanned categories: FOIA requests overdue, due soon, or still unsearched; ethics filings past their annual cycle; pending approvals older than four hours; records past their retention disposition; ordinances adopted more than thirty days ago but not yet published to the code; today's meetings.

​

Each item carries an urgency tier and a deep link back into the agent. The short version caps at ten lines so it reads cleanly on a phone; the full digest lands in email or chat. Per-tenant timezone scheduling — one process, many cities, each one delivered at the right local hour.

​

The clerk doesn't have to remember to ask.

Ask for an office briefing and get the office in a packet: active FOIA requests by status, upcoming meetings, expiring board appointments, expiring contracts, pending motions awaiting action, records due for disposition.

​

Read-only. Nothing it surfaces requires approval to view. The whole point is that institutional memory stays in the building when the person who carries it doesn't.

Search across ordinances, resolutions, minutes, and motions — hybrid keyword and semantic retrieval, with a citation on every result. "What did we do last time someone asked about short-term rentals?" answered in seconds, with the exact ordinance section to point at.

​

Then turn the precedents into a starting point. Tell the agent what you need — a noise ordinance, a special-use resolution, a FOIA cover letter — and it retrieves up to five similar prior documents and produces three meaningfully different draft variants. Nothing touches the official record until the clerk picks one and promotes it through the admin-gated tool.

Push-to-talk from the clerk's phone during a live council session. The audio is transcribed; the agent answers in one or two sentences, no markdown, no formatting clutter — "per last month's minutes…"

​

Same tools, same audit log, same security boundary as the full chat interface. Different presentation, designed for a moment when the clerk needs an answer fast and discreetly.