Prototype open-source benefit eligibility and child welfare systems for a state

The Chief of Staff at Georgia's Department of Human Services used Claude Code to build two AGPL Rust prototypes, one for SNAP and Medicaid eligibility and one for child welfare.

Done withClaude Code· Nov 20, 2026

What they did

The poster runs the office of Georgia's Department of Human Services, which administers SNAP, TANF, Medicaid eligibility, child support and child protective services. Frustrated that every state pays a vendor for a near-identical system each decade, they used Claude Code over several months to build two systems: one for federal benefit eligibility and one for child welfare case work. Both are in Rust under the AGPL and published on the agency's GitLab. The design keeps shared core logic separate from each state's policy choices, which live in their own git repository. Rules were first encoded with the zen-engine rules engine, and eligibility rules were later prototyped in Catala, a language built for formally checking legal rules. Waivers are handled through WebAssembly plugin points in the core.

How it went

Both systems are prototypes, not ready for production, and the poster lists known problems: very heavy dev tooling, a lot of over-engineering, a few huge files and missed chances to share code. One small piece, a new mandated reporting portal that forwards reports to the existing system of record, is due to go live early next year, built by the agency's IT staff. The poster leaves the role on January 11 and plans to hand the work to the incoming team.

Worth knowing

The production portal was kept deliberately stateless to limit what can go wrong, and the poster says it still goes through the same federal data security rules and paid bug bounties as any other system. Writing it in Rust cost more tokens and iterations, a trade the poster chose on purpose for correctness.

Try it

With Claude Code· 5 parts to fill in

Help me prototype an open-source system for [government program or regulated process]. Keep the core logic that every [jurisdiction or customer] shares separate from the local policy choices, and put those choices in a separate config repository at [path]. Use [language] and encode the eligibility or business rules in [rules engine or rules language] so they can be tested on their own. Start with a written design and the list of policy options you plan to support, and wait for my approval before writing code. After that, build one module at a time with tests, and stop after each module to show me what changed.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related