Arrell Advisory · Responsible AI Governance

The Nested Governance
Architecture

A Framework for Responsible AI in Practice

1
Architecture
4
Phases
3
Tiers
1
Case Study
Dr Gbemisola Adetayo Responsible AI Governance Architect
Principal, Arrell Advisory · March 2026
Presented at STC Squared Conference · Springfield Tech Week

AI Governance That Operates, Not Just Complies

Governments and enterprises around the world are discovering the same thing: AI governance principles are the easy part. The hard part is translating them into operational frameworks that teams can actually execute. Through my research at the Center for AI and Digital Policy (CAIDP), I have identified the patterns that separate governance architectures that work from those that sit on a shelf.

This paper introduces the Nested Governance Architecture™, a design pattern for embedding AI governance within broader organizational transformation so that governance operates as a built-in standard rather than an isolated compliance exercise. It includes the MPBP Framework™ (Map, Prioritize, Build, Pilot), the implementation methodology for moving from governance principles to operational frameworks, and a Risk-Proportional Governance model that matches governance intensity to actual impact.

To demonstrate how the architecture applies in practice, this paper uses Missouri's AI Executive Orders (26-02 and 26-03) as its primary case study.

On January 13, 2026, Missouri Governor Mike Kehoe signed Executive Order 26-02, directing four state departments to develop frameworks for the safe and effective integration of Artificial Intelligence within state government operations. The same day, he signed Executive Order 26-03, establishing the Missouri GREAT initiative, a government-wide efficiency and transformation program that explicitly ties AI adoption to its safety and security standards.

Together, these orders did something distinctive. Rather than treating AI as a standalone policy problem, Missouri embedded AI governance inside a broader government transformation agenda. The departments tasked with building Missouri's AI future (the Office of Administration, Economic Development, Natural Resources, and Higher Education and Workforce Development) now have until November 30, 2026 to deliver recommendations.

That's an ambitious timeline. And the question facing each department is no longer whether Missouri should govern AI, but how to translate five governance principles into operational frameworks that state employees, citizens, and businesses can actually use. The Nested Governance Architecture™ and MPBP Framework™ provide one structured answer to that question.

The Nested Governance Architecture™

Most governments that have taken action on AI governance have done so through a single mechanism: an executive order focused narrowly on AI, or a legislative bill addressing specific AI applications. This creates a structural weakness. When AI governance exists as a standalone layer, it competes for attention with operational priorities, and operational priorities usually win.

The Nested Governance Architecture™ solves this by embedding AI-specific governance principles within a broader operational transformation agenda rather than standing them up as a separate compliance function. The architecture creates accountability at multiple levels: the outer layer sets the organizational mission and transformation goals, while the inner layer establishes AI-specific guardrails that operate within that mission context. This design prevents AI governance from becoming an isolated function that organizational leaders can deprioritize or route around.

Missouri's executive orders exhibit this architecture.

Executive Order 26-02 establishes the AI-specific governance principles (the inner layer). It directs four departments to develop frameworks organized around five pillars:

1Efficiency & Service
Identifying high-potential AI applications to increase government efficiency and enhance quality of services to Missourians.
2Data Privacy & Security
Establishing robust policies and technical safeguards to protect sensitive data and personal information from unauthorized access or misuse by AI systems.
3Human Decision-Making
Ensuring appropriate human oversight and intervention, especially in high-impact AI use cases, to maintain accountability and preserve human judgment in critical decisions.
4Transparency & Accountability
Developing guidelines for transparency regarding AI tools: how they function, what data they use, and mechanisms for citizens to raise concerns about automated decisions.
5Data Quality Management
Creating guidelines for continuous monitoring and assessment of data used in AI tools, including accuracy, completeness, consistency, timeliness, relevance, and objectivity.

Beyond these five pillars, EO 26-02 also addresses AI's infrastructure demands, directing the Department of Natural Resources and the Public Service Commission to ensure data center energy demands don't drive up rates for residential and small business customers. And it directs the Department of Higher Education and Workforce Development to evaluate AI education programs and launch workforce training initiatives. These additions demonstrate systems-level thinking: AI governance isn't just about the technology, it's about the infrastructure, the workforce, and the economic ecosystem around it.

Executive Order 26-03 then wraps this inside the broader Missouri GREAT initiative (the outer layer). Its Section III.3.c explicitly states that departments exploring AI applications must adhere to the safety and security standards established in EO 26-02. This is the Nested Governance Architecture™ at work: the GREAT initiative sets the operational transformation agenda, and EO 26-02's AI governance principles function as guardrails embedded within that agenda.

Outer Layer · EO 26-03 · GREAT Initiative
Missouri GREAT Initiative
Government-wide efficiency and transformation program. Departments exploring AI applications must adhere to the safety and security standards established in EO 26-02. § III.3.c
Inner Layer · EO 26-02 · AI Governance
AI Governance Principles
Five pillars directing four departments to develop frameworks for the safe and effective integration of AI within state government. Deadline: November 30, 2026
1
Efficiency &
Service
2
Data Privacy &
Security
3
Human
Decision-Making
4
Transparency &
Accountability
5
Data Quality
Management
Dept 01
Office of
Administration
Dept 02
Economic
Development
Dept 03
Natural
Resources
Dept 04
Higher Ed &
Workforce Dev

Nested Governance Architecture™: AI governance is not a siloed compliance exercise. It's embedded within how Missouri intends to operate. Departments encounter AI governance as a built-in standard, not an afterthought.

Energy & Infrastructure
Data center demands must not drive up rates for residential and small business customers
Workforce Development
AI education programs and workforce training initiatives across state agencies
Education & Ecosystem
Evaluating AI education programs and building the broader economic ecosystem

The Nested Governance Architecture™ is what makes Missouri's approach structurally sound. In jurisdictions where AI governance exists as a standalone policy, it competes for attention with operational priorities. When governance is nested within the transformation agenda itself, departments working on efficiency, business partnerships, and modernization encounter AI governance as a built-in operating standard, not an afterthought bolted on later.

But architecture alone does not produce outcomes. The next question is implementation: how do Missouri's departments translate this structure into operational governance that their teams can execute against a November 2026 deadline? That requires an implementation methodology and an operational decision framework, both of which sit within the Nested Governance Architecture™.

From Principles to Operational Frameworks

The distance between governance principles and operational frameworks is significant. Every jurisdiction that has committed to AI governance discovers this: the principles are the easy part. The hard part is translating them into something people can actually use when they're deciding whether to deploy an AI tool in a state agency next Tuesday morning.

The Nested Governance Architecture™ provides the structural foundation. But architecture without implementation is just a diagram. Missouri's four departments, like any organization implementing AI governance, now face the execution question: How do you operationalize it?

Through my research at CAIDP, several patterns have emerged about what accelerates this transition and what creates friction:

Jurisdictions that start by mapping what already exists move faster. Before building new frameworks, understanding which AI tools are already in use, which decisions they support, and what data they access creates the foundation everything else builds on. Jurisdictions that skip mapping end up building frameworks for theoretical scenarios while real AI use grows ungoverned.

Jurisdictions that prioritize by impact rather than trying to govern everything at once get further. Not all AI applications carry the same risk. An AI tool that automates scheduling is different from one that supports eligibility determinations. Prioritizing which use cases need robust governance first, and which can operate under lighter standards, prevents the framework from becoming so comprehensive that nothing gets implemented.

Jurisdictions that learn from existing frameworks rather than starting from scratch avoid unnecessary delay. The NIST AI Risk Management Framework, the OECD AI Principles, and the governance structures emerging from the EU AI Act have all been tested at scale. They offer structures, terminology, and assessment methods that Missouri's departments could adapt rather than reinvent, freeing time and energy for the Missouri-specific questions that no external framework can answer.

Jurisdictions that build governance around real deployments, not hypothetical ones, produce frameworks that survive contact with reality. A governance framework developed in isolation, then handed to agencies for implementation, almost always requires significant revision once it meets actual workflows. A framework developed alongside a real pilot deployment embeds practical wisdom from the start.

These four patterns, Map, Prioritize, Build, and Pilot, are not random observations. They represent a consistent implementation sequence that I have codified into the MPBP Framework™, the implementation methodology within the Nested Governance Architecture™.

Implementing the Architecture: Map, Prioritize, Build, Pilot

The MPBP Framework™ is the implementation methodology within the Nested Governance Architecture™. It provides a structured, four-phase pathway from governance principles to operational governance. Applied to Missouri, it offers one approach the departments could consider as they build toward the November 30, 2026 deadline, designed to be practical, phased, and aligned with the five governance pillars in EO 26-02.

PHASE 01 · MONTHS 1–2
Map What Exists
Before building governance, understand what you're governing. Inventory current and planned AI use, including vendor tools with AI capabilities that may not be labeled as "AI."

Without mapping: Frameworks get built for theoretical scenarios while real AI use grows ungoverned.

Gate → Phase 2: Working inventory exists covering known AI tools, with each entry identifying the decision it supports and the data it accesses.

PHASE 02 · MONTHS 2–4
Prioritize by Impact
Not all AI applications carry the same risk. Classify by tier so governance resources match the actual impact level of each application.

Without prioritization: Governance becomes so comprehensive that nothing gets implemented.

Gate → Phase 3: Each inventoried use case assigned a tier, with at least one Tier 1 candidate identified for fast-track governance.

PHASE 03 · MONTHS 3–6
Build on Tested Frameworks
Adapt NIST AI RMF, OECD AI Principles, and EU AI Act structures. Don't reinvent what others have already solved. Focus original effort on Missouri-specific questions.

Without leverage: Teams reinvent what others have solved, consuming time on solved problems.

Gate → Phase 4: Draft governance framework exists with tier-specific controls documented. At least one external framework formally reviewed and adapted.

PHASE 04 · MONTHS 4–10
Pilot & Learn
Each department identifies one well-scoped AI pilot where the governance framework is built and tested in real time, producing evidence alongside documentation.

Without pilots: Frameworks don't survive contact with reality, producing documents that sit on a shelf.

Gate → Report: Pilot completed with documented lessons. Framework revised based on what the pilot surfaced. Evidence of governance in action, not just governance on paper.

01
02
03
04

Map the Current Landscape

Before building governance, understand what you're governing.

Each department conducts an inventory of its current and planned AI use:

What AI tools and systems are currently in use across the department? Including vendor-provided tools with AI capabilities that may not be labeled as "AI."
What decisions do these tools support or automate? Which of these decisions affect citizens directly?
What data do these tools access, process, or generate? What is the sensitivity level of that data?
What AI use cases are being planned or requested by department staff?

This mapping doesn't need to be exhaustive to be useful. A working inventory, even an imperfect one, is dramatically more valuable than a theoretical governance framework built without visibility into actual AI use. The inventory also naturally surfaces the use cases that most urgently need governance attention.

Global Reference

The OECD AI Policy Observatory maintains a repository of how member countries have approached AI use inventories within government. Korea's Framework Act on AI requires ongoing monitoring of AI deployment. The EU AI Act mandates registration of high-risk AI systems. Missouri's departments could draw on these models as reference points for designing their own inventory approach.

Risk-Proportional Governance

Not all AI use cases need the same level of governance.

The Prioritize phase of the MPBP Framework™ introduces the Risk-Proportional Governance model, a three-tier AI impact classification that determines how much governance each AI application requires. Once the landscape is mapped, departments categorize AI applications by the level of impact they have on Missourians:

Tier 1
Routine Automation
Lightweight
Characteristics

AI that automates internal administrative tasks with no direct citizen impact.

Procurement RFP summarization Payroll report generation Vendor compliance checks
Governance Approach

Department-level approval, standard data quality checks, periodic review.

Missouri example: The Office of Administration's Division of Purchasing processes procurement for most state agencies through MissouriBUYS. AI summarizing RFP submissions or flagging vendor registration gaps would streamline high-volume internal operations with no citizen decision impact.

Efficiency & Service Data Quality
Tier 2
Decision Support
Moderate
Characteristics

AI that informs human decisions affecting citizens or resource allocation.

Permit application screening Environmental monitoring analysis Inspection prioritization
Governance Approach

Documented human-in-the-loop requirements, transparency about AI's role, data privacy impact review.

Missouri example: The Department of Natural Resources processes hundreds of permit applications annually across air, water, and land reclamation programs, many still via PDF forms submitted through the MoGEM portal. AI pre-screening applications for completeness before a permit writer's review would support, not replace, the human decision on each permit.

Data Privacy & Security Human Decision-Making Transparency
Tier 3
High Impact Decisions
Robust
Characteristics

AI that directly affects citizen outcomes, rights, or access to services.

Financial aid eligibility Fraud detection in benefits Institutional certification
Governance Approach

Human oversight at the decision point, transparency to affected citizens, data quality validation, and a mechanism for concerns about automated decisions.

Missouri example: The Department of Higher Education and Workforce Development processes Access Missouri Grant eligibility for over 40,000 students annually, disbursing more than $81 million in need-based aid. AI introduced into eligibility verification, fraud detection, or outreach targeting would directly affect whether individual Missourians can afford higher education, requiring all five governance pillars.

All Five Governance Pillars Apply
Low impact
High impact

This tiered approach allows departments to allocate governance resources proportionally. Tier 1 applications can move quickly under lightweight standards. Tier 3 applications get the full governance architecture. This prevents the common failure mode where governance becomes so comprehensive that even routine automation requires months of review, which drives agencies to adopt AI informally and ungoverned.

Making Classification Operational

A tier model is only useful if departments can actually apply it. The classification process should follow a simple workflow:

01
Submit
Use case owner describes the AI application
02
Classify
Governance lead assigns tier based on citizen impact
03
Review
Tier-appropriate controls applied and documented
04
Deploy
Approved with conditions or returned for revision
05
Monitor
Ongoing review; reclassify if scope or impact changes
Classification can be challenged by the use case owner or escalated by the governance lead if conditions change.

Two operational details matter here. First, classification should be based on the decision the AI supports, not the technology itself. The same large language model could be Tier 1 when summarizing internal meeting notes and Tier 3 when flagging students for eligibility review. The governance tier attaches to the use case, not the tool. Second, classification is not permanent. A Tier 1 application that begins routing its outputs to citizen-facing processes should be reclassified upward, and the monitoring step exists precisely to catch this drift.

Build on What Exists

Missouri's departments don't need to invent AI governance from scratch.

Several established frameworks offer tested structures that can be adapted for Missouri's context:

NIST AI Risk Management Framework
What It Offers

A voluntary framework organized around four functions (Govern, Map, Measure, Manage) with practical implementation guidance for each.

How Missouri Could Use It

Provides a structured methodology Missouri's departments could adapt for their governance framework design. Particularly useful for operationalizing EO 26-02's five pillars into actionable processes.

OECD AI Principles
What It Offers

Five principles adopted by 46 countries: inclusive growth, human-centered values, transparency, robustness/security, accountability.

How Missouri Could Use It

EO 26-02's five pillars align closely with OECD principles. Missouri can benchmark its frameworks against an internationally recognized standard, which also supports the federal alignment goal.

EU AI Act Risk Classification
What It Offers

A tiered approach classifying AI systems by risk level (unacceptable, high, limited, minimal) with corresponding governance requirements.

How Missouri Could Use It

The Risk-Proportional Governance model in Phase 2 draws on this approach. Departments could study the EU's classification criteria to inform how Missouri categorizes its own AI use cases.

Nested Governance Architecture™
What It Offers

A governance design pattern that embeds AI-specific governance within broader organizational transformation agendas, with the MPBP Framework™ providing structured implementation and Risk-Proportional Governance providing the operational decision mechanism.

How Missouri Could Use It

Missouri's dual executive order structure already exhibits this architecture. The NGA™ provides the analytical framework for understanding why this structure works and the implementation methodology for operationalizing it across all four departments.

Adapting these frameworks is not about importing foreign regulation. It's about learning from the substantial investment other jurisdictions have already made in solving the same operational questions Missouri's departments now face. The Missouri-specific questions, how these principles apply to Missouri's agencies, workforce, data systems, and citizen expectations, are what the departments are uniquely positioned to answer.

Pilot and Learn

Governance frameworks designed alongside real deployments outperform frameworks designed in isolation.

Rather than developing a comprehensive governance framework in theory and then implementing it, each department could identify one well-scoped AI pilot: a practical deployment where the governance framework is built and tested in real time.

The pilot approach has several advantages for Missouri's timeline:

Tangible Results by Deadline
Each department can present both a governance framework and evidence of how it performed against a real deployment, not just a theoretical document.
Surfaces Practical Questions
Who approves the AI tool selection? How is training data quality validated in practice? What happens when the AI produces an unexpected output? These questions only emerge through doing.
Builds Internal Expertise
The department staff who participate in the pilot become the governance practitioners who can scale the framework across additional use cases.
Aligns with GREAT Initiative
EO 26-03 encourages departments to explore AI applications. A governed pilot demonstrates AI innovation and responsible governance working together, not in tension.

A good pilot candidate for each department would be a Tier 1 or Tier 2 use case (routine automation or decision support) that serves a clear operational need, uses data the department already manages, and can be implemented with existing or readily available tools. High-impact applications (Tier 3) are better served by a more mature governance framework developed after the pilot provides lessons learned.

From Framework to Operating System

A governance framework tells departments what to do. A governance operating system tells them how to do it, who owns each step, and what evidence to produce.

The Nested Governance Architecture™ provides the design pattern. The MPBP Framework™ provides the implementation sequence. The Risk-Proportional Governance model provides the decision mechanism. What remains is the execution infrastructure: the artifacts that program managers, governance leads, and department staff would use when an AI use case arrives on their desk next Tuesday morning.

The full operating layer would include:

Controls-by-Tier Matrix
What documentation, oversight, testing, and monitoring is required at each tier level.
Use-Case Intake Workflow
The step-by-step process from submission through classification, review, and ongoing monitoring.
RACI Ownership Map
Who is responsible, accountable, consulted, and informed across central office, legal, procurement, security, and program owners.
Phase Gate Checklists
Detailed entry and exit criteria for each phase transition, including evidence requirements.

Building the full operating layer is the implementation work that turns a governance framework into a governance system. That work is most effective when done alongside the organizations who will use it, not delivered to them from the outside.

What NGA™ Implementation Produces

Missouri was among the first states to take comprehensive executive action on AI governance in 2026. Being early is an advantage, but only if the execution matches the ambition.

If the four departments execute the MPBP Framework™ across its four phases, by the November 30, 2026 reporting deadline Missouri could have:

1
A working AI use inventory across state government, the first comprehensive view of where and how AI is operating within Missouri's agencies.
2
A tiered governance framework that matches governance requirements to the actual impact level of each AI application, fast-tracking routine uses while ensuring high-impact decisions receive robust oversight.
3
At least four department-level AI pilots demonstrating governance in action. Not just frameworks on paper, but evidence of what works in practice.
4
Workforce development programs beginning to prepare state employees for AI-augmented roles, not replacing workers but equipping them with the skills to work effectively alongside AI tools.
5
An energy and infrastructure assessment ensuring Missouri's AI growth doesn't come at the expense of residential and small business ratepayers.
6
A governance model that other states look to as a reference, positioning Missouri as a leader in responsible AI adoption within state government.
Reporting deadline: November 30, 2026

This outcome is ambitious but achievable. The executive orders provide clear direction. The Nested Governance Architecture™ and MPBP Framework™ offer a structured path. The existing global knowledge base, from NIST, OECD, and jurisdictions worldwide, provides tested tools. What Missouri's departments bring is the context, the operational knowledge, and the proximity to the citizens who will ultimately be served by AI governance done well.

Responsible AI Leadership Is Not About Preventing AI Adoption

It's about ensuring that when organizations adopt AI, they do so with the governance architecture that protects the people they serve.

The Nested Governance Architecture™ provides a repeatable design pattern for any government or enterprise navigating this transition. The MPBP Framework™ provides the implementation sequence. The Risk-Proportional Governance model provides the decision mechanism. And the operating layer provides the execution infrastructure. Together, they form an integrated system for building governance that operates, not just complies.

Missouri's case demonstrates what this looks like in practice. Governor Kehoe's Executive Orders 26-02 and 26-03 set the direction. The governance principles are clear. The departments are tasked. The deadline is set. What happens between now and November 30, 2026 will determine whether Missouri builds an AI governance architecture that serves as a national model, or produces frameworks that sit on a shelf.

The difference comes down to execution. And execution, in governance as in technology, benefits from structure, learning from what others have done, and the willingness to build governance in practice rather than in theory.

The architecture is here. The methodology is here. The next step belongs to the organizations, and the people they serve, who will live with the governance they build.

Sources and Further Reading

Missouri Executive Orders

Executive Order 26-02: Establishing Frameworks for the Safe and Effective Integration of Artificial Intelligence within State Government Operations. State of Missouri, January 13, 2026. Available at sos.mo.gov.

Executive Order 26-03: Establishing the Missouri GREAT Initiative. State of Missouri, January 13, 2026. Available at sos.mo.gov.

Missouri State Departments

Missouri Office of Administration. Division of Purchasing, Division of Personnel, Information Technology Services Division. oa.mo.gov.

Missouri Department of Natural Resources. Permits, Certifications, Registrations and Licenses; Missouri Gateway for Environmental Management (MoGEM); Air Pollution Control Program; Water Protection Program; Land Reclamation Program. dnr.mo.gov.

Missouri Department of Economic Development. Division of Business and Community Solutions; Missouri One Start; Regional Engagement. ded.mo.gov.

Missouri Department of Higher Education and Workforce Development. Access Missouri Financial Assistance Program; Division of Workforce Development; Coordinating Board for Higher Education. dhewd.mo.gov.

International Frameworks and Standards

National Institute of Standards and Technology. AI Risk Management Framework (AI RMF 1.0). NIST AI 100-1, January 2023. nist.gov/ai.

Organisation for Economic Co-operation and Development. OECD Principles on AI. OECD, May 2019, updated 2024. oecd.ai.

European Parliament and Council of the European Union. Regulation (EU) 2024/1689 (EU AI Act). Official Journal of the European Union, July 2024.

OECD AI Policy Observatory. National AI policies and strategies repository. oecd.ai/en/dashboards.

U.S. Federal AI Policy

The White House. Executive Order on the Safe, Secure, and Trustworthy Development and Use of Artificial Intelligence (EO 14110). October 30, 2023.

Office of Management and Budget. Memorandum M-24-10: Advancing Governance, Innovation, and Risk Management for Agency Use of Artificial Intelligence. March 28, 2024.

National Institute of Standards and Technology. Artificial Intelligence Risk Management Framework: Generative AI Profile. NIST AI 600-1, July 2024.

CAIDP and Research

Center for AI and Digital Policy (CAIDP). Artificial Intelligence and Democratic Values Index. 2024 Edition. caidp.org.

CAIDP AI Policy Clinic. Research methodology and comparative governance analysis across OECD member states.

State and Comparative Governance

Republic of Korea. Framework Act on Artificial Intelligence. 2025.

National Association of State Chief Information Officers (NASCIO). State CIO priorities and digital transformation reports. nascio.org.

MissouriBUYS eProcurement System. State of Missouri, Office of Administration. missouribuys.mo.gov.

Arrell Advisory

Arrell Advisory is a responsible AI governance consultancy founded by Dr Gbemisola Adetayo. We help organizations design, implement, and operationalize AI governance architectures that enable adoption rather than obstruct it.

Our approach is grounded in a core principle: governance should be execution infrastructure, not compliance theater. We design governance systems that generate measurable ROI through faster adoption speeds, incident prevention, and competitive auditability advantages.

Dr Adetayo brings Fortune 500 project management experience with organizations including WHO, Coca-Cola, and Wells Fargo, combined with deep expertise in AI governance research through the Center for AI and Digital Policy (CAIDP). This combination of operational reality and governance architecture is what distinguishes Arrell Advisory's methodology.

What We Do

Governance Architecture Design. We apply the Nested Governance Architecture™ to embed AI governance within your existing transformation agenda, organizational structure, and operating rhythm.

Implementation via the MPBP Framework™. We guide organizations through the four-phase implementation sequence: mapping current AI use, prioritizing by impact, building on tested frameworks, and piloting governance alongside real deployments.

Risk-Proportional Governance. We design three-tier classification systems calibrated to your organization's specific risk landscape, ensuring high-impact decisions receive robust oversight while routine automation moves quickly.

Operating Layer Build-Out. We develop the execution artifacts, including controls matrices, intake workflows, RACI maps, and phase gate checklists, that turn governance frameworks into governance systems teams can operate.

Get in Touch

If your organization is navigating AI adoption and needs governance that enables rather than obstructs, we would welcome a conversation.

arrelladvisory.com