← Mathematical compendium

Published equation contexts

Approval(a)={automatic,p(a) S(a)≤Bhuman required,p(a) S(a)>B\text{Approval}(a) = \begin{cases} \text{automatic}, & p(a)\, S(a) \le B \\ \text{human required}, & p(a)\, S(a) > B \end{cases}

Why this formula appears here

Whether human-approval checkpoints become automated and statistical is, likewise, mostly a readout of Axis B rather than a genuinely separate question. A useful way to see the dependency is to write the automation decision as a threshold rule. Let p(a) be a certified upper bound on the probability that action a violates its specification, and let S(a) be a severity score for the consequence class a belongs to. A natural rule an organization or regulator could adopt is Approval(a)={automatic,p(a) S(a)≤Bhuman required,p(a) S(a)>B\text{Approval}(a) = \begin{cases} \text{automatic}, & p(a)\, S(a) \le B \\ \text{human required}, & p(a)\, S(a) > B \end{cases}. where B is a risk budget set by policy. The rule only does useful work where p(a) is a number someone can trust — which is exactly what Axis B’s certified branch would supply and its empirical branch would…

Read the full article-specific guide →

Read the representative guide

How to interpret it

Read it with the definitions, units, and assumptions supplied by the article.

Research cited beside this formula

Learn the mathematics behind it

Published contexts (1)

A symbol can carry a different meaning in another article. Each occurrence keeps its own guide and term definitions.

Approval(a)={automatic,p(a) S(a)≤Bhuman required,p(a) S(a)>B\text{Approval}(a) = \begin{cases} \text{automatic}, & p(a)\, S(a) \le B \\ \text{human required}, & p(a)\, S(a) > B \end{cases}

Equation 5 · AI Agents & Systems

AI Agent Architecture in 2035: Four Scenarios, Their Signals, and What Would Falsify Them

This equation states a bound: one expression must stay on the indicated side of the other under the article’s assumptions.

Whether human-approval checkpoints become automated and statistical is, likewise, mostly a readout of Axis B rather than a genuinely separate question. A useful way to see the dependency is to write the automation decision as a threshold rule. Let p(a) be a certified upper bound on the probability that action a violates its specification, and let S(a) be a severity score for the consequence class a belongs to. A natural rule an organization or regulator could adopt is Approval(a)={automatic,p(a) S(a)≤Bhuman required,p(a) S(a)>B\text{Approval}(a) = \begin{cases} \text{automatic}, & p(a)\, S(a) \le B \\ \text{human required}, & p(a)\, S(a) > B \end{cases}. where B is a risk budget set by policy. The rule only does useful work where p(a) is a number someone can trust — which is exactly what Axis B’s certified branch would supply and its empirical branch would…

Meanings in this article

  • BB: a risk budget set by policy.
Equation guide → · Article →