01 / Access permission
Can the person or system enter?
Access governs technical reach into applications, data, and functions.
Authentication and identity
Application or data access
Technical permissions
AI Decision Authority
Authority follows consequence, not access.
Access is not authority. Assignment is not authority. AI capability is not authority. Vidamonti resolves who is institutionally permitted to approve, reject, modify, escalate, override, or stop the consequential decision under the conditions that actually exist.
Authority boundaryWho may decide under these conditions?
Permitted actionsApprove, reject, modify, escalate, override, stop.
Decision recordPreserve which authority path actually applied.
Authority is not access control
Technical permission can be valid and institutional authority can still be insufficient.
Identity and workflow systems remain essential, but by themselves they do not decide who may commit the institution to the consequence in front of them. Vidamonti resolves that boundary in context.
02 / Workflow role
What function do they perform?
Workflow roles define participation, assignment, and operating responsibility.
Operator, analyst, reviewer
Task ownership and routing
Context within the process
03 / Decision authority
What are they institutionally allowed to decide?
Authority binds consequence, context, thresholds, and permitted decision actions.
Approve, reject, modify
Escalate, override, stop
Delegated and final authority
Map authority to consequence
Resolve authority from the consequence, not the login.
Vidamonti evaluates decision type, consequence, jurisdiction, exception state, thresholds, delegation, and current conditions before the workflow exposes an action the institution can authorize.
Decision typeWhat institutional action is being considered?Context
ImpactWhat can happen if the decision proceeds?Consequence
JurisdictionWhich authority or policy boundary applies?Scope
Exception stateIs the decision inside the ordinary operating path?Control
ThresholdDoes the decision exceed delegated scope?Authority
Authority Resolver / Decision DA-2049Authority state
Decision factors
ConsequenceHigh
Evidence sufficiency74%
Policy exceptionPresent
Delegated scopeExceeded
Jurisdiction complexityElevated
Resolved authority path
Current reviewerRisk Operations
May review evidence and recommend disposition.
Required authorityExecutive Approval
Threshold and exception state require higher institutional authority.
Allowed next actionsEscalate / request evidence / hold
Approval is unavailable at the current authority level.
Authority resolution is configured to the institution's actual operating model and decision boundaries.
AI approval workflows
Build approval paths from real decision authority.
Vidamonti routes the decision to the authority that can resolve it, exposes only permitted actions, and escalates when the current authority boundary is insufficient. Exception handling remains inside the controlled path.
Authority Workflow / Cross-border transferDecision state: Review required
Control path
Recommendation
Policy
Evidence
Authority
Human Review
Decision Record
01RecommendationProposed action captured
02PolicyApplicable controls resolved
03EvidenceMaterial basis available
04AuthorityDelegated scope exceeded
05ReviewHigher authority required
Decision context
Current roleRisk Operations
Authority statusInsufficient for approval
Required reviewerExecutive Authority
Override postureNot permitted at current role
Permitted actions
ApproveUnavailable
Request evidenceAllowed
HoldAllowed
EscalateRequired path
OverrideUnavailable
RejectAllowed
Separate reviewer roles
Keep reviewer roles distinct inside the same control model.
Different workflows can require operators, supervisors, risk or compliance functions, executive authority, or other defined roles. Vidamonti keeps reviewer assignment and permitted decision actions explicit rather than inferring them from system access.
Role
Review
Approve
Escalate
Override
Operator
Yes
No
Yes
No
Supervisor
Yes
Conditional
Yes
No
Risk / Compliance
Yes
Conditional
Yes
Conditional
Executive Authority
Yes
Yes
Yes
Configured
Make delegation visible
Make delegated authority explicit, scoped, and time bounded.
Vidamonti can represent temporary, substitute, or emergency authority with a named source, defined scope, time window where applicable, and recorded use.
Named delegator and delegatePreserve where the authority originated and who received it.
Defined scopeSpecify decision type, threshold, jurisdiction, or operating boundary.
Explicit time windowTemporary authority expires at the configured boundary rather than persisting by accident.
Recorded useWhen delegated authority is exercised, preserve it in the decision record.
Delegation Record / DG-118Delegation state
DelegatorExecutive Authority
Active delegationApproval up to defined threshold
DelegateRegional Supervisor
Bounded scopeCross-border transfer review
Effective17 Sep / 08:00
Expires18 Sep / 20:00
OverrideNot delegated
Preserve the authority chain
Preserve the authority path that actually governed the outcome.
The decision record retains which authority path applied, who acted, which actions were available, and whether escalation, delegation, or override affected the final state, supporting later review and assurance where the operating model uses that record.
Decision Authority Ledger / DA-2049Authority decision record
Authority context resolvedOperator role identified. Delegated approval threshold evaluated.
Resolved
Delegated scope exceededDecision impact and exception state require higher authority.
Escalation
Executive reviewer assignedRequired policy and evidence context attached to review state.
Assigned
Approval with conditionsAction authorized within defined conditions and recorded rationale.
Authorized
Direct answers
Decision authority, in plain language.
These definitions make the authority model explicit for evaluators and operators without collapsing technical access into institutional permission.
What is AI decision authority?
AI decision authority defines who or what is institutionally permitted to move an AI-supported recommendation into an authorized state. It determines which roles may approve, reject, modify, escalate, override, or stop a consequential decision under defined conditions.
How is decision authority different from access control?
Access control determines whether a person or system can enter an application, data set, or technical function. It remains important, but by itself it does not grant institutional permission to make the consequential decision. Decision authority defines that separate boundary.
What is an AI approval workflow?
An AI approval workflow routes an AI-supported decision through the evidence, policy, authority, and human review steps required before action can proceed. The path defines who must review, what they need, which actions they can take, and where escalation ends.
When should an AI-supported decision escalate?
A decision escalates when the current role lacks sufficient authority, required evidence is unresolved, policy creates an exception, consequence crosses a threshold, or the workflow otherwise cannot resolve the decision inside the current operating boundary.
Decision Authority
Scale AI capability. Keep institutional authority explicit.
Do not allow technical access, workflow assignment, or increasing model capability to become institutional authority by accident.