States have eight months to design exemption categories, build verification systems, establish coordination timelines, create delegation frameworks, and negotiate tribal sovereignty agreements. The ten articles in Series 7 demonstrate that these are not technical implementation details but fundamental policy choices determining who maintains Medicaid coverage independent of employment status or work effort. The regulatory architecture question is ultimately about trust and burden distribution: states trusting people create verification support infrastructure and exemption processes assuming legitimate barriers, while states skeptical of compliance create individual responsibility systems and gatekeeping mechanisms assuming work avoidance. These philosophical orientations pervade hundreds of granular regulatory choices whose cumulative effect rivals statutory eligibility rules in shaping coverage outcomes for 18.5 million expansion adults.
The Architecture IS the Policy#
The central insight threading through all ten Series 7 articles is that administrative design choices function as substantive policy decisions. When a state requires specialist attestation for medical exemptions rather than accepting primary care documentation (7A), the state has made a coverage decision affecting everyone without specialist access. When a state chooses centralized individual online reporting rather than distributed employer verification (7B), the state has determined that people without digital literacy or internet access face higher coverage loss risk. When a state imposes 30-day grace periods rather than 90-day transitions (7C), the state has decided that people experiencing job loss, exemption expiration, or circumstance changes have one month to navigate bureaucratic compliance. When a state leaves liability questions unresolved for employers and providers (7D), the state has ensured that third parties will not participate in verification systems, forcing reliance on individual reporting that Arkansas proved produces coverage loss from documentation failure rather than work failure.
Arkansas 2018 and Georgia 2025 made different architectural choices across every domain and produced dramatically different outcomes despite serving similar populations under identical 80-hour monthly requirements. Arkansas chose restrictive exemptions, centralized individual reporting through web portals, minimal grace periods, and unclear delegation authority. The result was 25 percent coverage loss, with the overwhelming majority of losses among people who were working or qualified for exemptions but could not navigate verification systems. Georgia chose expansive exemptions, distributed employer verification, generous transitions, and clearer third-party participation frameworks. Early results show coverage stability with substantially lower administrative failure rates. The difference is not populations served but regulatory philosophy embedded in hundreds of granular choices.
The Trust-Burden Framework Across Domains#
Reading the series together reveals a consistent meta-framework operating across all regulatory domains. Every architectural choice embeds an assumption about human behavior and allocates burden accordingly.
Exemption architecture (7A) assumes either that most people seeking exemptions face legitimate barriers or that most are trying to avoid work. States choosing the first assumption build automated identification through existing data, presumptive access during processing, proactive outreach to likely-exempt populations, and grace periods acknowledging that transitions require time. States choosing the second assumption require upfront documentation before protection, manual applications despite available data, restrictive processing timelines, and minimal grace periods.
Verification architecture (7B) distributes burden either to organizations with institutional capacity or to individuals least equipped for bureaucratic compliance. Distributed submission through employer payroll systems, MCO coordination, and educational institution reporting shifts costs to entities that can absorb them. Centralized individual reporting concentrates burden on populations with lower education levels, limited digital access, cognitive impairments, and language barriers. The evidence is unambiguous about which approach produces coverage loss.
Coordination timing (7C) creates either realistic compliance opportunities or procedural traps. Generous grace periods, coverage continuation during appeals, proportional transition times after exemption expiration, and automatic extensions during system failures protect individuals from procedural harm at the cost of administrative complexity. Compressed deadlines, coverage termination during disputes, and rigid deadline enforcement simplify administration at the cost of coverage losses from timing failures.
Delegation frameworks (7D) either enable participation by providing safe harbor protections, clear credentialing pathways, and reasonable audit standards, or prevent participation by leaving liability questions unresolved. Employers, providers, and community organizations will not participate in verification systems where legal exposure is unclear, regardless of administrative need or policy intention.
Tribal sovereignty (7E) demands recognition that standard work requirement architecture cannot function in contexts where formal unemployment exceeds 40 to 80 percent, subsistence economies provide unverifiable economic value, data sovereignty prevents state access to tribal records, and government-to-government relationships require negotiated consent rather than administrative mandate.
The Accountability Gap#
The synthesis surfaces a profound structural problem. No single entity controls enough of the system to guarantee functional outcomes. States design exemption categories but federal rules constrain options. Federal law creates the IHS exemption but states must operationalize it. Employers verify hours but have no legal obligation to participate. Providers document exemptions but may not be compensated for attestation work. MCOs coordinate support but contract terms remain undefined. Tribes negotiate agreements but lack administrative capacity to implement alternatives. Individuals must maintain compliance but face systems designed for employment realities different from their own.
This distributed accountability means that no mechanism forces coordination across independent actors and no party bears responsibility for gaps emerging from lack of integration. The consolidated decision matrix (7F) makes the interdependencies visible: data sharing agreements must precede system development, policy decisions must be final before vendor work begins, credentialing frameworks must exist before third-party participation, and tribal consultation must produce agreements before any tribal provisions can be implemented. Each dependency creates sequential requirements that compress the already insufficient eight-month implementation timeline.
What Eight Months Cannot Build#
The implementation timeline analysis across all ten articles reveals mathematical incompatibility between infrastructure requirements and the December 2026 deadline. States must finalize policies, execute data sharing agreements, develop technology platforms, train staff, credential third parties, negotiate tribal agreements, and test systems under realistic conditions. Each component requires months and assumes other components are already functional.
Most states have not finalized exemption categories, verification methods, coordination schedules, delegation authorities, or tribal frameworks as of early 2026. Vendors cannot build what states have not decided. Employers cannot credential for systems that do not exist. MCOs cannot develop member support programs when delegation authorities remain undefined. The coordination failure where no single party controls all necessary components predicts that December 2026 implementation will feature widespread system gaps producing coverage losses that no single entity’s failure caused but that collective unpreparedness guaranteed.
The handbooks (7A-HB through 7D-HB) provide comprehensive operational frameworks, but frameworks require months of regulatory development, stakeholder consultation, federal approval, and operational preparation. States beginning this process in early 2026 face severe compression. States that have not yet begun face impossibility.
The Philosophical Questions Remain#
Perhaps most critically, the fundamental philosophical choices examined throughout the series remain unresolved in most states. Will exemption systems assume legitimate barriers or work avoidance? Will verification support people or impose burden as gatekeeping? Will coordination protect coverage or prioritize administrative efficiency? Will delegation enable participation or create liability traps? Will tribal sovereignty be respected through negotiated frameworks or ignored through unilateral state action?
These questions reflect disagreements about safety net purposes, government responsibility, individual obligation, and burden distribution that regulatory handbooks cannot resolve. Different states will answer differently based on political priorities. The resulting variation will create 50 different implementation experiences where administrative architecture determines outcomes as powerfully as statutory eligibility rules. The next eight months will reveal whether that architecture becomes infrastructure supporting compliance or barriers preventing it.