Abstract
Safety Is Designed Before Capability Growth: Boundaries, stop mechanisms, verification criteria, and rules for expanding authority must exist before the system receives the corresponding freedom. “We’ll patch it later” does not work when the consequence is irreversible.
A Claim Is Not Evidence: Neither the developers’ words (“we checked everything”) nor the system’s own words (“I am safe”) count as engineering evidence. Trust is built on a structure of checks that can be independently repeated.
Freedom Grows in Steps, Alongside Verifiability: Autonomy is not a switch but a set of distinct authorities. Each step requires its own basis, and verification depth is tied to the amount of independent action that can be allowed: reduce verification, and freedom falls with it.
No Self-Authorization, and No Safety “Only from the Outside”: The system does not decide for itself when the evidence is sufficient. But protection that exists only as a fence around unlimited capability is not enough either: safety must be built into the architecture itself and preserved as capabilities grow. The doctrine is not trying to keep a system below some fixed level of intelligence; it is trying to ensure that the properties of control do not disappear as capabilities increase.
Unknowns Must Remain Visible: The absence of an observed failure does not prove the absence of failure. An unassessed item does not count as passed. Every safety claim has boundaries: configuration, conditions, scope, and validity period.
Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 License.
Recommended Citation
Kotegov, Volodymyr, "Earning the Right to Act", Technical Disclosure Commons, (October 26, 2026)
https://www.tdcommons.org/dpubs_series/12413