Chenna, M. Essays
5 min

Proposed open standard, v0.1 · Measurement

The Meaningful
Override Rate

Human oversight of AI is either real, or it is theater. This is the instrument that tells them apart.

Chenna, M. · Founder, Sanctity · Amsterdama proposed open standard, v0.1
scroll to read

A law can require a human in the loop. It cannot, by itself, tell you whether that human ever exercises command. And a power nobody uses looks identical, from the outside, to a power that was never there. So we are left certifying oversight we cannot see. The Meaningful Override Rate, or MOR, is the smallest honest instrument I know of for fixing that. It measures the use, not the clause.

01 · The definition

Of the calls a person could reverse, how many did they?

The metric
Meaningful Override Rate (MOR)

Of the decisions where a human could have changed the machine's output, the fraction where the human actually changed it and the change stood.

MOR = meaningful overrides ÷ reviewable decisions

In plain words: of the calls a person could have reversed, how many did they really reverse. Not clicks. Not time on screen. Not a signature at the bottom of a form. A meaningful override is a reversal the human initiated and the organization honored. Authorizing is not overseeing.

02 · The companions

Two checks, so the number stays honest

MOR on its own can be gamed or misread. It travels with two checks.

Contestation latency. How much time and context the human realistically had to disagree. Three seconds per item is a turnstile, not oversight, at any override rate. Reversal validity. When humans do override, are they right more often than the machine would have been? An override rate that is high but wrong is its own failure, not a success.

03 · Validity

What makes a MOR number worth citing

A figure is only worth citing if it clears all five of these. Anything short of this is an anecdote wearing a percent sign.

  1. Stated sample. At least roughly one hundred reviewable decisions, not a demo reel.
  2. Pre-registered meaning. What counts as meaningful is fixed before anyone looks at the results, and published alongside the number.
  3. One named workflow. A specific task in a specific place, not "enterprises" in general.
  4. An explicit denominator. Overrides divided by reviewable decisions, with no cherry-picking of the wins.
  5. An inter-rater check. More than one judge agrees on what counted, so meaningful is not one person's taste.

Report it in exactly this shape, with its own caveat attached:

On [workflow X], MOR was [N] percent across [M] reviewable decisions. Here is how we defined meaningful. We do not yet claim this generalizes.
04 · The trap

Presence is not oversight

There is a tempting shortcut: prove oversight by logging that a human was present, or that a human clicked. It is tidy, it is auditable, and it measures the wrong thing. Proof of presence is not proof of command. A confirm button that is always pressed is precisely the theater this metric exists to expose. MOR asks the only question that matters: when it counted, did the human change the outcome.

A human who can technically say no, but never does, and gets blamed when the machine is wrong, is not oversight. It is a crumple zone with a job title.
05 · Status

Why the standard comes before the number

This is v0.1, published before the numbers on purpose. I am computing MOR on a real workflow now. The first results will appear here, method and limits included, when they clear the five tests above. I am publishing the standard first so the measure does not quietly belong to whoever happens to look good on it. A ruler is only fair if it is printed before the race.
06 · The bet

My falsifiable wager

Across real deployments, measured honestly, the meaningful override rate of most of what is sold today as "human oversight" sits near zero. If you run this and show me a field of systems where humans routinely and validly overrule the machine, I am wrong, and I will say so here. Until then, the burden sits where it belongs: on the claim of oversight to show its number.

The formal specification

Meaningful Human Oversight of AI: A Proposed Measurement Standard (MOR v0.1)

Chenna, M. · Sanctity, Amsterdam · Working paper, v0.1 · 2026

Abstract. Regulation increasingly mandates human oversight of AI without any way to tell whether that oversight is ever exercised. We define the Meaningful Override Rate, a five-part validity bar for citing it, and two companion measures, and argue that the standard must be fixed before the numbers.

Read the full specification →
Cite this standard
Chenna, M. (2026). The Meaningful Override Rate (MOR),
a proposed open standard, v0.1. manjchenna.com/essays/meaningful-override-rate

Use it. Cite it. Hold me to it.

Free to use. Run it on your systems and on mine. Want the argument behind it? Read Human Oversight Is Mostly Theater. Want to see what I am building? Start here.

© 2026 Chenna, M. · The Meaningful Override Rate, a proposed open standard v0.1 · Amsterdam