Govern · Consequence authorization
Turn enterprise intent into consequence authorization.
Aarmos evaluates a specific proposed consequence — who is acting, what they want to do, and which resource would be affected — under declared enterprise policy before governed execution.
Your organization defines policy, authority, and the facts a policy may require. Aarmos evaluates that declared intent; it does not decide what your governance ought to be.
This applies to governed actions that reach a supported Aarmos origin. Pre-consequence enforcement applies only where the path is confirmed as enforcing; direct or known-bypass paths remain outside that boundary.
The governed object
Evaluate the consequence, not the agent in the abstract.
A Decision answers one bounded question under the policy and facts in force at that moment.
- 01
Actor
Who is proposing the action
- 02
Proposed consequence
What the actor wants to do
- 03
Resource
What would be affected
- 04
Policy evaluation
Declared rules, authority, and facts
- 05
Decision
allow · deny · step_up · defer
A Decision is an answer. It is not Authority, an Attempt, or an Effect. A step_upasks for additional authority; a defer returns the question without converting it into a denial.
A consequence in context
Access is not authorization for this payment.
An invoice agent may have credentials that can reach a payment system. That access alone does not authorize a particular vendor payment. The proposed consequence still has to be evaluated under the organization’s declared policy.
- Proposed consequence
- Invoice agent → finance.pay_vendor
- Applicable policy
- A finance-manager authority is required for this consequence
- Decision
- step_up
- Authority state
- Required; not yet satisfied
- Next step
- Request the required authority, then evaluate the bounded consequence again
Complementary controls
Enterprise controls establish access. Govern answers a different question.
Identity systems establish who or what is acting. Access controls, gateways, credentials, network controls, and application rules determine reachability and system-specific permissions. Those controls may enforce their own boundaries.
Aarmos composes with them by evaluating whether this actor is authorized for this proposed consequence against this resource, under declared policy and authority. When policy requires more context, external systems can provide authoritative facts or evaluations; policy determines what those inputs mean.
The boundary
Govern stops at the Decision.
Govern
Determines authorization under declared policy.
Run
Enforces governed execution under the applicable Decision and Authority at supported consequence boundaries.
Prove
Preserves governance evidence that can be independently verified.
Technical references
Go deeper on the model.
See a consequence reach a Decision.
Follow a bounded scenario from the proposed action through policy evaluation and its next step.