Authority before execution.
Praesidias is an independent authority layer that determines whether AI agents and automated systems are authorized to take specific actions before they execute.
Access determines what a system can do. Praesidias determines what it is authorized to do.
01 — Access vs. authority
Identity, credentials and access can establish that a system is able to reach a resource. Praesidias asks a different question before a consequential action executes: does this actor have valid organizational authority for this exact action, under the organization’s current policy and conditions?
Technical ability
- Authenticated
- API reachable
- Credentials valid
- Tool available
The system can technically perform the action.
Organizational authority
- Delegated scope confirmed
- Current policy active
- Approval conditions met
- Requested amount within limit
Authorization depends on more than access.
02 — Where it sits
A separate authority boundary.
The system requesting an action should not be the final authority over whether that action is permitted.
Praesidias sits outside the agent or application requesting an action. It evaluates explicit authority and organizational policy deterministically before execution, then returns an authorization decision for the connected execution layer to enforce.
The authorization decision is deterministic. No LLM makes the final ALLOW/DENY decision.
04 — The decision
One action. One deterministic decision.
05 — Enforcement
Decision before execution.
06 — Evidence
Authorization should leave evidence.
Outcome Proof
07 — Institutional memory
Know why it happened. Years later.
At the moment of execution
What policy existed?
Who held authority?
What was delegated?
What action was requested?
Why was it allowed?
What outcome was recorded?
08 — Shared infrastructure
One authority layer. Different systems.
Systems should not merely have permission to act.
They should be able to prove they had authority.