For the complete documentation index, see llms.txt. This page is also available as Markdown.

Pattern: citizen-services chatbot

Government / public sector — citizen-services chatbot pattern. Policy accuracy against versioned source-of-truth, plain-language reading-level, multilingual parity.

A state or federal agency operates an AI chatbot that helps citizens find services, check eligibility, and complete applications (benefits, permits, tax forms, licenses). The agency's source-of-truth policy documents update on their own cadence — and a stale chatbot answer can deny benefits citizens are entitled to.

This pattern shows how to evaluate citizen-services chatbots for policy accuracy, accessibility, and equity.

What's at stake

Risk dimension
Magnitude
Framework

Eligibility-misstatement civil-rights exposure

Class-action and Title VI claims

Title VI / ADA / state agency rules

Section 508 accessibility violations

Per-violation penalties

Section 508 (federal) / state equivalents

Public-trust impact from incorrect official guidance

Long-tail agency-credibility damage

Public agency-performance research

Congressional / legislative inquiry

Hearing time, executive-branch response

Public oversight records

The evaluation pattern

A policy-grounded evaluation runs against a versioned source-of-truth.

  1. Custom code grader (policy-document-hash check) — every chatbot answer references the active policy document version; if the active document hash differs from the answer's referenced version, the answer is stale = fail.

  2. Faithfulness judge (GEPA-tuned against ≥50 caseworker-labeled examples — scored output) — claims about eligibility and procedures are grounded in the cited policy section.

  3. Reading-level scorer (Flesch-Kincaid or grade-level equivalent) — patient-facing answers must be at or below the configured grade level (commonly 6th-8th grade for citizen-services).

  4. Multilingual parity scorer (custom code) — per-language accuracy must be within 5 percentage points of the primary language baseline.

  5. Disclaimer-presence scorer — the chatbot must include the agency's official "this is informational, not a determination" disclaimer where required.

Don't have labels yet? See Bootstrap a judge before GEPA for the week-1 setup.

Continuous trace evaluation: sampled hourly during business hours. Policy-document-hash scorer runs on every trace (cheap and deterministic). Threshold alerts route to the agency's program managers.

Configuration in code

What you get

  • Stale-policy answers detected within hours, not weeks.

  • Multilingual accuracy parity is measured per language, not assumed.

  • Auditor-ready evaluation history for civil-rights and accessibility audits.

  • Pre-publication block prevents citizen-facing release on a regression.

Stratix capabilities used

Replicate this

Get started: Cookbook: catch hallucinations is the closest runnable starter (policy faithfulness shape).

Last updated

Was this helpful?