Most AI governance programs sort systems into three or four risk tiers and apply the same controls to everything in a tier, which breaks down when one platform hosts a harmless FAQ bot and an agent that can delete production data.
Decision criticality is a rating of how much harm results if a specific AI output or action is wrong in its deployment context. This whitepaper sets out a seven-axis scoring method, legal floors drawn from Colorado SB 26-189, California's CPPA ADMT rules, ECOA, FCRA, the EU AI Act and OMB M-25-21, and the controls each of four tiers requires.
The evidence is regulatory text, public standards and analyst forecasts. The weights, thresholds and worked examples are Logiciel's proposed method, not a regulatory standard, and nothing here is legal advice.
A criticality score is only as sound as the answers behind it. Three questions at intake settle most of the outcome, and each can be answered on paper before anyone writes a test. Each also produces a named artifact that counsel, an auditor or a governance committee can check later.
Ask whether the output affects eligibility, selection, price or terms in credit, housing, insurance, employment, education or healthcare. Colorado's "materially influences" standard reaches ranking and recommending, and California's ADMT rules cover similar significant decisions, so an underwriter making the final call does not settle the question. A match sets a minimum tier regardless of the weighted score. The artifact is a legal floor entry naming each matched law and its citation.
Ask how much a human reviews before the output takes effect, and be strict about what counts. California's ADMT rules recognize human involvement only when the reviewer can interpret the output, weigh other information and has authority to change the decision. A reviewer who only clicks approve is monitoring, not deciding. The artifact is a written description of the review step, naming who reviews, what they see and what they can overturn.
Ask for every tool and permission scope the agent holds, including tools it can reach by calling another agent. OWASP names excessive functionality, permissions and autonomy as root causes of LLM agent harm and recommends enforcing authorization outside the model. Refunds, deletions, production deploys and privilege changes each need their own score and gate. The artifact is a tool inventory with a tier and an approval gate recorded against each action.
Write one sentence on who is affected, what changes for them and what the AI contributes. Then list each tool and permission scope the system or agent will hold, since each is scored separately.
Compare the use case against Colorado SB 26-189, California's ADMT rules, ECOA, FCRA, EU AI Act Annex III and OMB M-25-21. Record any match with its citation and involve counsel.
Rate impact on people, business impact, reversibility, scale, autonomy, explainability and data sensitivity from 0 to 3. Overrides for legal triggers, severe harm, irreversible autonomy and safety only ever raise the tier.
Each tier fixes its testing, review, monitoring, documentation and approval level. Register rescoring triggers such as a new tool, a model change, a wider population, an autonomy shift, drift or a new law taking effect.
Decision criticality is a rating of how much harm results if a specific AI output or action is wrong in its deployment context. It weighs impact on people and the business, reversibility, scale, autonomy, explainability needs and data sensitivity, with legal definitions of consequential decisions setting a minimum.
The resulting tier sets the testing, human review, monitoring, documentation and approval level the system must meet.
Score each decision point on seven axes from 0 to 3, apply the weights and map the total to four tiers. Then apply override rules for legal triggers, severe impact on people, irreversible autonomous actions and safety, which only ever raise the tier.
The final tier is the highest of the use-case tier, the highest ungated tool tier and any legal floor.
An AI system needs a human in the loop when its output is consequential, irreversible or must be explained to the person affected, as in credit, insurance, employment, housing, education and healthcare.
California's ADMT rules count a reviewer only when they can interpret the output, weigh other information and have authority to change the decision. Low-impact, reversible tasks can run on-the-loop with sampling.
A consequential decision is one about education, employment, housing, financial or lending services, insurance, healthcare or essential government services, under Colorado SB 26-189, effective January 1, 2027. California's ADMT rules cover similar significant decisions, and credit adverse actions also trigger ECOA and FCRA notice duties.
Under Colorado, technology that only ranks or recommends can still qualify if it materially influences the outcome.
Treat every tool and permission scope as its own decision and score it separately. Reads of public data sit low, while sensitive reads, external writes, financial commits, deletions, production deploys and privilege changes sit high or critical.
The agent's tier is the highest action it can take without a gate, so adding gates and narrowing permissions lowers it, in line with OWASP's guidance on excessive agency.
The whitepaper gives you a seven-axis scoring worksheet, override rules, a tier-by-tier control matrix, agent action classes, reclassification triggers and a ten-step intake checklist. Its evidence is regulatory text, public standards from NIST, ISO and Canada, OWASP guidance and Gartner and McKinsey research.
The weights, thresholds and worked examples are Logiciel's proposed method rather than a regulatory standard, and legal status reflects November 2026 sources, not legal advice.
The whitepaper gives no sourced cost figure, because cost depends on how many decisions and agent tools you score. Its argument is that design choices are often the cheaper lever: moving an action into human-in-the-loop review, or narrowing an agent's permissions, can lower a tier without adding testing.
Gartner cites inadequate risk controls among the reasons it expects over 40% of agentic AI projects to be canceled by 2027.
Drop your details and we'll send The AI Governance Decision-Criticality Framework straight to your inbox - no spam, unsubscribe anytime.
Bring one AI use case or agent you run today, with the tools and permissions it holds. We will work through its criticality score, the legal floor it meets and the controls its tier calls for, alongside your counsel rather than in place of them. SECTION 7 - FAQ - 5 to 8 questions
Book a criticality review