Champions · For the people who carry the message

Built so that Louisianans don't lose Medicaid for the wrong reasons.

This page is for the people who will champion this work in their communities. State legislators, county officials, advocacy directors, faith leaders, and the policy nonprofits that hold the line for Medicaid beneficiaries.

The technical depth lives at /platform and /safeguards. This is the human story. Every claim on this page traces to a public Architecture Decisions Record, a statute, or a sourced public document. Nothing on this page is invented.

For

State legislators, county officials, advocacy directors, faith leaders, healthcare-policy nonprofits

Length

A 10-minute read. A two-minute scan.

Brief

A four-page version is downloadable at the close.

01 · The compliance crisis

The federal compliance infrastructure is publicly broken. The federal government has said so itself.

HUD has not been able to estimate improper payments for eight years running.

The HUD Office of Inspector General audited HUD's compliance with the Payment Integrity Information Act in May 2025. The finding: "For the eighth consecutive year, HUD was unable to estimate improper payments for its two largest rental assistance programs." Those two programs together represent roughly $50 billion, about two-thirds of HUD's total expenditures.

Source: HUD OIG report 2025-FO-0006, May 2025.

$5 billion in potential payment errors. 30,000 deceased tenants still on the rolls.

HUD's own FY2025 Agency Financial Report acknowledges more than $5 billion in potential improper payments. The same report identifies approximately 30,000 deceased tenants still enrolled in rental assistance. Secretary Scott Turner's public statement on the report described the situation as a massive abuse of taxpayer dollars driven by failure to implement strong financial controls.

Source: HUD-No. 25-152, FY2025 AFR.

HOTMA was delayed to the same date as §71119. HUD's own systems could not keep up.

HUD pushed its own HOTMA recertification compliance deadline to January 1, 2027 (the same date as §71119), citing implementation challenges in HUD's internal systems including the Tenant Rental Assistance Certification System. Two federal compliance deadlines on the same day, one already publicly delayed because the legacy infrastructure cannot keep up with the rule changes.

Source: HUD Notice H 2025-07.

Sixty percent of HUD-assisted Medicare Advantage enrollees are also on Medicaid.

HUD's own research arm reports the dual-program overlap: "Slightly more than 60 percent of HUD-MA individuals were dually enrolled in Medicaid." The same population is being asked to clear two failing compliance regimes at once. A grandmother in New Orleans East with HUD voucher and Medicaid coverage faces both recertification clocks on the same population, navigating systems that the federal government has publicly admitted are not keeping up.

Source: HUD USER, August 2024.

Arkansas already showed what happens when tracking fails.

Within seven months of the Arkansas Medicaid work-requirement launch, 18,000 people lost coverage (1 in 4 of those subject to the requirement). The disenrolled "only found out when they tried to seek medical care or fill a prescription." The lessons cited in the Urban Institute analysis: notice failure, technology overreliance, and the absence of personal interaction.

Civitas Compliance is the infrastructure built so that the next §71119 deadline does not produce the next Arkansas.

Source: Urban Institute, Lessons from Launching Medicaid Work Requirements in Arkansas.

02 · What the platform does

Eight commitments. Each one enforced in code.

Each row pairs the architectural commitment with what it means for a real beneficiary. Every numeric claim comes from the architecture itself, not from imagined pilot data. Every claim cites the public Architecture Decisions Record or statute that backs it.

  1. 01

    Zero wrongful disenrollments by code refusal.

    Disenrollment-deadline violation throws an exception in code, not a policy warning. ADR-006.

    Mary does not lose her Medicaid because a deadline got mishandled at the case-worker level. The platform structurally refuses the action.

  2. 02

    100% statutory due process.

    Every disenrollment passes through 15 sequenced phases with explicit valid-transition tables. None can be skipped or reordered. ADR-006; 42 U.S.C. § 1396a(xx)(6).

    No beneficiary loses coverage without notice, an active cure period, case-worker review, an alternative-eligibility check, and a hearing notice, in that order.

  3. 03

    Cure-period protection during state capacity shortages.

    When a state runs out of volunteer placement capacity, the cure-period countdown legally suspends. Remaining days are preserved. ADR-007. Precedent: Gresham v. Azar, 950 F.3d 93; Stewart v. Azar, 366 F. Supp. 3d 125.

    A beneficiary in Rapides Parish on a 45-mile waitlist is not penalized for capacity gaps on the state's side. When a slot opens, her countdown resumes at the exact remaining count.

  4. 04

    15 languages from day one.

    Onboarding, dashboards, exemption forms, and in-app guidance ship in 15 languages. Right-to-left text rendering for Arabic, Urdu, and Persian. /civicpath §2.

    A Vietnamese-speaking grandmother in New Orleans East does not lose her Medicaid because the form was English-only.

  5. 05

    17 of 17 statutory exclusion categories evaluated.

    Every federal exemption category from § 1902(xx)(7) is enforced at the database layer. /safeguards hero metric; ADR-005.

    A pregnant beneficiary, a medically frail beneficiary, a caretaker of a child with a disability, a former foster youth, a Native American with IHS eligibility: every federally-protected category is honored without staff having to remember to check it.

  6. 06

    No AI denials, ever.

    The compliance determination engine has no AI input path. CivicAI is read-only by architecture. ADR-008.

    No Louisianan's coverage is denied by a model that the platform cannot explain to a fair-hearing officer.

  7. 07

    Audit-trail integrity that survives subpoena.

    Every compliance determination is written as a new row in an immutable ledger. The integrity is enforced at the storage layer, not the policy layer. ADR-001; ADR-002.

    Three years after the fact, in a fair hearing or a court of law, the record holds. The beneficiary can see exactly what happened to their case.

  8. 08

    Offline mode for the audience the legacy systems forgot.

    Hours captured offline sync to the ledger when connectivity returns. /civicpath §3.

    A beneficiary on a rural bus route or in a transit dead-zone does not lose credit for hours she actually worked or volunteered.

03 · Real Louisianans

Eight people the platform is built to protect.

These are the canonical personas the platform engineers test against. The first four are detailed below. The remaining four are open to expand.

Persona 01 · Volunteer compliance · New Orleans

Patricia Ann Decuir.

Patricia volunteers at NOLA CAN, a community organization in New Orleans. She has logged 85 hours over the compliance period. The organization confirmed her attendance through the partner attestation portal. The platform's approval-side review auto-approved her hours. Her compliance posture is current. Her Medicaid is not at risk.

Each hour Patricia logs is timestamped, geolocated, and written to an append-only ledger that cannot be altered. Three years from now, in a fair hearing or a record review, every one of those hours holds up exactly as it was recorded.

Patricia is the everyday case the platform is built for. She is what compliance looks like when the infrastructure does its job: invisible to her, defensible to an auditor, durable in the record.

Read the architectural commitments behind Patricia's case at /decisions/append-only-decision-ledger and /decisions/phased-noncompliance-procedure.

Persona 02 · Rural compliance · Rapides Parish

Travis Wayne Fontenot.

Travis lives in Rapides Parish. His nearest approved community partner is 45 miles away, and the parish has run out of volunteer placement capacity. He is on a waitlist that is not his fault.

Under the platform's capacity-shortage tolling, Travis's cure-period countdown legally suspends. His remaining days are preserved. When a placement opens, the countdown resumes at the exact remaining count. He is not penalized for living somewhere the state has not yet built enough capacity to serve. The protection is visible to him in his mobile app on every waitlist screen, not buried in a policy memorandum.

The architectural posture here is informed by the body of federal court precedent on Medicaid work-requirement waivers. Gresham v. Azar, 950 F.3d 93 (D.C. Cir. 2020) and Stewart v. Azar, 366 F. Supp. 3d 125 (D.D.C. 2019) both established that administrative actions failing to consider the impact on beneficiary coverage carry an audit-posture risk under the Administrative Procedure Act. Civitas's tolling architecture answers that risk in code.

Read the architectural record at /decisions/capacity-shortage-tolling.

Persona 03 · Federal exemption · Native American (United Houma Nation)

James Allen Dardar.

James is an enrolled member of the United Houma Nation. He is eligible for Indian Health Service care. Under § 1902(xx)(7), he holds a federal exemption from the community engagement requirement.

The platform recognizes James's tribal membership and his IHS eligibility automatically, because § 1902(xx)(7) recognizes them and the database refuses to drift outside that recognition. There are no enum tail-positions, no "OTHER" category, no free-text fields where his tribal status could be miscategorized or quietly overridden. The 17 statutory exclusion categories are 17 enum members at the database layer. None more, none fewer. James's exemption is structural, not discretionary.

The Houma Nation is Louisiana indigenous, with members across the Terrebonne and Lafourche parishes and beyond. The platform's treatment of James is the same the platform offers every federally-recognized exemption category. There is no policy interpretation between the statute and his coverage.

Read the architectural record at /decisions/closed-set-actions.

Persona 04 · Re-entry transition · Louisiana

Darius Wayne Celestin.

Darius came home six weeks ago after his sentence ended. He is 73 days into a 90-day re-entry transition window, the federal period during which a returning citizen is exempt from the community engagement requirement. Transitional employment has started. His Medicaid is active.

On September 26, 2024, Governor Jeff Landry submitted Louisiana's Section 1115 Reentry Demonstration Waiver Application to the U.S. Department of Health and Human Services. The application asks for federal permission to provide Medicaid services (including case management, medication-assisted treatment, and a 30-day supply of prescription drugs upon release) for the 90 days prior to a Medicaid-eligible individual's release from prison or jail. The waiver is currently pending federal approval; in April 2026, the Louisiana Department of Health announced that the state had aligned the application with new federal budget-neutrality requirements under Section 71118 of H.R. 1, and anticipates approval. The application builds on Louisiana's existing Justice-Involved Pre-Release Enrollment Program, in place since 2017 through a partnership between the Louisiana Department of Health and the Louisiana Department of Public Safety and Corrections.

The Governor's letter is direct about the gap: the inability of Louisiana's Medicaid program to seamlessly begin care management for all individuals who will be eligible upon release leaves a very real possibility that there will be a gap in care when a justice-involved individual reenters the community. Louisiana sits at 596 sentenced incarcerations per 100,000 residents (1.7 times the national average), the fifth-highest drug overdose mortality rate in the country, and 73% of incarcerated individuals living with substance use disorder. The Civitas architecture is built so that the post-release compliance posture is defensible from day one. Darius's coverage was active when he walked out, his case management is current, and his audit trail holds. He is the bipartisan champion frame: re-entry coverage is rare ground where conservative and progressive champions meet, and Louisiana is asking the federal government to expand it.

Read the architectural commitment at /decisions/phased-noncompliance-procedure.

Personas 05 · 08 · Click any name to expand

Four more.

Each remaining persona maps to a different champion's audience. Faith leaders. Senior advocates. Disability-rights advocates. Health-equity advocates working on second-chance enrollment. Click any name to read the full case.

  • Persona 05 · Faith-based volunteer · New Orleans

    Reginald Wayne Batiste.

    Volunteer hours through a faith-based organization. AI assists with auto-approval on the approval side only. The pulpit is a partner.

    Reginald volunteers at his parish food pantry. The faith-based organization confirms his hours through the partner attestation portal. The platform's approval-side review auto-approves clear-approval cases quickly, so Reginald's compliance posture stays current without anyone waiting on a manual review.

    This is the architectural commitment behind the FBO partnership pathway. The platform uses AI on the approval side only. AI cannot deny anyone's coverage. CivicAI, the beneficiary-facing assistant, is read-only by architecture and cannot mutate any compliance state. Faith leaders championing the platform can speak with confidence: their congregation's hours flow through a system that does not let an algorithm take coverage away from anyone, and the human approval review is itself a separate layer the platform respects as the source of truth.

    Read the architectural record at /decisions/ai-auto-approve-only.

  • Persona 06 · Senior with delegated access · Louisiana

    Ethel Mae Treme.

    Age 74, age-exempt, account managed by her daughter. The platform supports family caregiving without compromising the audit trail.

    Ethel is 74 and exempt from the community engagement requirement on age grounds. Her daughter manages the mobile account on her behalf, with explicit delegation recorded in the platform. Every action her daughter takes is captured with the same audit-trail integrity that applies to a beneficiary acting on her own account.

    The platform does not assume tech fluency. Senior advocates championing the platform can speak directly to the design intent: the audience the legacy systems forgot is the audience the platform is built for. A grandmother who does not own a smartphone, or who finds the device confusing, can still be served because the family member who supports her can be served, with no loss of accountability and no second-class treatment.

    Accessibility commitments live across /civicpath and the WCAG 2.1 AA scope on /safeguards.

  • Persona 07 · Federal exemption · Disability

    David Anthony Arceneaux.

    Disability federal exemption (SSI/SSDI-linked, permanent exclusion). The platform recognizes the exemption at the database layer.

    David's disability exemption is linked to his Supplemental Security Income or Social Security Disability Insurance status. Under § 1902(xx)(7), this is a permanent federal exclusion from the community engagement requirement.

    The platform recognizes the SSI/SSDI link automatically. David never has to re-prove his disability to keep his coverage. The 17 statutory exclusion categories are 17 enum members at the database layer. The platform refuses to drift outside what § 1902(xx)(7) recognizes. Disability-rights advocates championing the platform can speak from the same architectural commitment that protects James Dardar's tribal exemption: the statute defines the categories, and the platform structurally honors all of them. Re-proving status year after year is not a feature; the statute does not require it, and the platform does not invent it.

    Read the architectural record at /decisions/closed-set-actions.

  • Persona 08 · Re-enrollment after compliance failure

    Jerome Duval Landry.

    Previously terminated, returning to compliance. The platform treats his second chance with the same architectural rigor as a first attempt.

    Jerome was previously terminated from the program. He is back. The reason for the prior termination is on the ledger. His new compliance is on the ledger. The audit trail shows the full sequence, intact and unaltered.

    The architectural commitment is that the platform treats every beneficiary's case with the same procedural rigor, regardless of history. The 15-phase noncompliance procedure runs the same way. The notice goes out the same way. The cure period is the same. The case-worker review and the alternative-eligibility check are the same. Health-equity advocates championing the platform can speak to a real durable property: a beneficiary who has been through the system before is served by the same architecture that protects a first-time beneficiary, and the prior history does not become a shadow rule that quietly weights the current case.

    Read the architectural records at /decisions/append-only-decision-ledger and /decisions/phased-noncompliance-procedure.

04 · For your community

Your constituents. Your congregation. The Vietnamese-speaking grandmother on Chef Highway who thought she had lost her Medicaid because the renewal form was in English. The veteran in Rapides Parish whose volunteer placement is 45 miles away. The cousin who came home six weeks ago after seven years inside, and who needs his medication tomorrow. The mother in Avoyelles Parish whose daughter manages her account because that is how their family takes care of each other. These are the people who lose coverage when the compliance infrastructure fails. They are also the people the architecture is built to protect.

05 · The discipline

Five rules the platform holds itself to.

  1. Every claim traces.

    Every architectural claim on this page cites a public Architecture Decisions Record, a statute, or a code-enforced mechanism. Every stakes claim cites a HUD audit, a federal letter, or a published study with date and URL. No "studies show" language. No imagined percentages. No invented outcomes. The architecture is the evidence; the citations make it auditable.

  2. AI cannot deny benefits.

    The compliance determination engine has no AI input path. CivicAI, the beneficiary-facing assistant, is read-only by architecture and cannot mutate any compliance function. AI is permitted only on the approval side, where it accelerates clear-approval cases. The constraint is enforced by the type system, not by a policy.

  3. The audit trail survives subpoena.

    Every compliance determination is written as a new row in an immutable ledger. The integrity is enforced at the storage layer through row-level database triggers, not by an honor code at the policy layer. Three years after the fact, the record holds up under cross-examination, fair-hearing review, and judicial discovery.

  4. Real Louisianans, never composites.

    Photography on this site, when it ships, will be documentary photography of real Louisianans, with releases and named subject lines. AI-generated faces are disqualifying for an audience that includes faith leaders and beneficiary advocates who detect inauthenticity instantly. While the photography commission is in progress, this page renders in abstract typographic restraint rather than substituting stock photography or AI imagery.

  5. No persona is fictional in the sentimental sense.

    Every persona on this page maps to a canonical entry in the same persona catalog the compliance platform's engineers test against. Their storylines are the scenarios the platform is built to handle. They are not marketing characters; they are the stress tests.

The full Architecture Decisions Record collection is at /decisions.

06 · Bring this to your community

We will come to your town hall.

If you want to bring this to your community, get in touch. We will come to your town hall, your parish council, your advocacy convening, your faith-leader gathering. We will also send the four-page brief, distilled from this page, that you can hand to a colleague, a mayor, or a constituent.

Schedule a briefing Download the champion's brief

A four-page document. Print-ready. No form, no gating, no follow-up sales loop.