Governance Doctrine
Architecture, not preference.
The Concepts section defines the vocabulary FERZ uses for runtime authorization. This section asserts the architectural positions FERZ takes about that vocabulary. Concepts answer “what is this?” Doctrine answers “what follows from how this is built?”
This is not an observability framework, an identity and access management overlay, or a policy engine. It is a category of its own: runtime authorization architecture for AI actions, producing pre-execution verdicts that can be independently verified. The doctrine pages exist to distinguish that category from adjacent ones without forcing readers to reconstruct the argument each time.
The doctrine is established across the FERZ corpus, with foundational arguments in On the Impossibility of Observability-Based Authorization (Meyman, 2026) and supporting analyses in the related papers cited in References below. The wording on each doctrine page is canonical. It is not paraphrased across FERZ materials and should not be paraphrased when citing.
The four positions
Visibility into AI behavior is necessary for oversight but does not constitute permission to act. A system that logs everything and authorizes nothing has not performed authorization.
Read the doctrine →Stopping execution is an event. A verdict is a decision with reproducible logic, bounded scope, and a verifiable authorization artifact. Systems that halt without producing a verdict cannot be audited, replayed, or appealed.
Read the doctrine →Monitoring describes actions after they occur. Authorization decides whether they occur at all. Treating the two as interchangeable collapses the distinction between observation and control.
Read the doctrine →Authority belongs to actors; action-level authorization belongs to proposed actions. An agent operating under the broadest delegation has not, by that fact, had any specific action authorized.
Read the doctrine →The combined canonical form
This is the FERZ Governance Doctrine in its compressed form. It appears verbatim in the corpus and in FERZ external materials. The four doctrine pages above expand each clause into its full argument, counter-positions, and architectural implications.
Why these positions matter
The AI governance market currently uses one word for several categorically different things. “Governance” is attached to content filtering, logging, human review queues, model fine-tuning, and policy documentation, among other practices. Each of these has a place in a complete AI stack. None of them, alone or in combination, constitutes runtime authorization.
The doctrine pages exist so that buyers, regulators, and engineers can distinguish authorization architecture from adjacent categories without having to reconstruct the argument each time. They are written for citation. The canonical wording is fixed; the surrounding argument can be excerpted; the structural claim can be quoted verbatim in regulatory submissions, academic work, and procurement documentation.
Frequently asked questions
Concepts define the vocabulary used in runtime authorization architecture, such as ex-ante authorization, Proof-Carrying Decisions, and ABSTAIN. Doctrine asserts the structural positions FERZ takes about that vocabulary, such as observability is not authorization. Concepts answer "what is this?"; doctrine answers "what follows from how this is built?"
Structural claims. The enforcement positions are grounded in the FERZ corpus's impossibility result showing that observability-based architectures cannot produce ex-ante authorization artifacts. The definitional position is grounded in the paper Authority versus Authorization: A Definitional Framework for AI Governance, which distinguishes authority, delegation, policy, authorization, and enforcement as separate architectural concepts.
Audit logs are narratives of what happened. Authorization proof is replayable evidence that an action was authorized before it occurred. A system that produces only logs has not performed authorization, regardless of how complete those logs are. The distinction is developed in the FERZ Governance Taxonomy.
Yes. The doctrine is published in canonical form precisely so that buyers, regulators, and engineers can cite it without paraphrase. The compressed three-clause form, the individual position statements, and the underlying corpus papers are all designed for direct citation.
References
FERZ, Inc. (2026). Governance Doctrine. https://ferz.ai/governance/doctrine
BibTeX
@misc{ferz2026doctrine,
author = {{FERZ, Inc.}},
title = {Governance Doctrine},
year = {2026},
url = {https://ferz.ai/governance/doctrine},
note = {FERZ Knowledge Base}
}