Policy changes in hours. Not eighteen months

The visual rule builder is the core of Commonwealth's policy engine. Rules are constructed from three building blocks: conditions (IF gross income ≤ 200% FPL), thresholds (shelter deduction cap = $672), and actions (THEN benefit = max allotment - 30% of net income). Policy administrators drag, connect, and configure these blocks in a visual canvas — seeing the rule logic in human-readable language at every step. The builder validates rules in real time, highlighting logical conflicts, unreachable conditions, and missing edge cases. When a rule is ready, the administrator previews its effect against historical case data before deploying. The entire process — from reading the federal memo to deploying the updated rule — takes hours, not months. And the person making the change is the person who understands the policy, not a developer interpreting a requirements document.

Agencies should not have to build eligibility rules from scratch. The federal regulations that govern SNAP, Medicaid, TANF, WIC, and other programs are substantially similar across all states — the differences are in state-specific policy overlays. Commonwealth maintains a federal regulation library: pre-built, validated rule templates for every major program, maintained by a dedicated policy team that monitors the Federal Register, USDA FNS memos, CMS State Medicaid Director letters, and ACF policy guidance. When a federal regulation changes, Commonwealth's policy team updates the federal rule template and delivers the update to all deployed states within 48 hours — as a configuration change that state administrators review, customize for any state-specific variation, and deploy. The state's responsibility is adapting the template to their specific policy choices, not building the federal logic from scratch.

Every state makes policy choices within the framework of federal regulation — and these choices are where most implementation complexity lives. Does the state use broad-based categorical eligibility for SNAP? What earned income disregard does the state apply for TANF? Does the state extend Medicaid to 138% FPL under expansion, or use a different threshold? Has the state waived the SNAP asset test? Commonwealth manages these as configurable state policy overlays that sit atop the federal rule base. The overlay system ensures that federal updates never overwrite state-specific choices, that state changes are independently testable, and that the audit trail clearly distinguishes between federal-mandated rules and state policy options. When a state legislature changes a policy — raising the childcare copay threshold, for example — the administrator modifies the state overlay without touching the federal base.

Every October, the Federal Poverty Level guidelines update. Every year, SNAP maximum allotments change. Deduction caps adjust. State Median Income percentages shift. In legacy systems, each of these annual changes requires a development cycle — because the threshold values are embedded in program logic, not stored in configurable tables. Commonwealth maintains all thresholds in dedicated, version-controlled configuration tables that administrators update through a spreadsheet-like interface: FPL thresholds by household size, SNAP maximum allotments by household size, standard deduction amounts, shelter deduction caps, earned income disregard percentages, childcare copay schedules, and WIC income guidelines. Each table carries an effective date — so future-year values can be pre-loaded and activated automatically on October 1 without any manual deployment step.

Income deductions and disregards are where eligibility determination gets complicated — and where most COBOL-era errors originate. SNAP allows a standard deduction, an earned income disregard of 20%, a dependent care deduction, an excess shelter deduction (capped for non-elderly/disabled, uncapped for elderly/disabled), and a medical expense deduction for elderly/disabled members. TANF applies different earned income disregards — often with time-limited transitional disregards. Childcare programs may disregard a percentage of child support received. Commonwealth manages all deductions and disregards in program-specific configuration tables — each with its own eligibility conditions, calculation methodology, applicable populations, and caps. When a state changes an earned income disregard percentage for TANF, the change affects only TANF calculations — never SNAP or Medicaid. Each deduction carries its own effective date, enabling prospective and retrospective application.

When a fair hearing officer asks "what rules were in effect when this determination was made?" the answer must be immediate, complete, and defensible. In COBOL systems, the answer requires archaeology — searching through code repositories, change request logs, and deployment records to reconstruct the logic that was running on a specific date. Commonwealth maintains a complete, immutable version history of every rule, every threshold, every deduction table, and every policy overlay — timestamped, attributed to the administrator who made the change, linked to the regulatory authority that required it, and instantly retrievable. The system can reconstruct the exact eligibility determination that would have been produced under any prior version of the rules — enabling fair hearing officers, quality control reviewers, and federal auditors to verify that the determination was correct under the rules as they existed at the time.

The biggest risk in policy changes is unintended consequences — a threshold adjustment that accidentally disqualifies a population that was meant to remain eligible, or a deduction change that interacts with another program's rules in an unexpected way. Legacy systems mitigate this risk through extensive regression testing that takes weeks and still misses edge cases. Commonwealth's impact simulation engine evaluates rule changes against the actual caseload before deployment: the administrator clicks "simulate" and sees exactly how many cases would be affected, how many would gain or lose eligibility, how benefit amounts would change (in aggregate and for representative cases), and whether any logical conflicts or edge cases exist. The simulation runs against 10,000+ historical case scenarios that cover the full diversity of household compositions, income levels, and program combinations. Only after reviewing the simulation results does the administrator deploy the change.

A rule change without case re-evaluation is incomplete — families affected by threshold increases, deduction changes, or new categorical eligibility pathways must be identified, their eligibility re-determined, and their benefits adjusted. In legacy systems, this is a months-long batch processing exercise. Commonwealth automates the entire chain: when a rule is deployed, the system immediately identifies every active case that is affected by the change, re-evaluates each case under the new rules, calculates the new benefit amount, generates the required notice to the family (including the old amount, new amount, reason for change, and fair hearing rights), and updates the case record. For threshold increases that expand eligibility, the system can also identify pending denied applications and recently closed cases that would now qualify — enabling proactive outreach to families who were denied under the old rules but are eligible under the new ones.