Dainin Reference
What may an AI decide for a business?
Decision Authority is the delegated right to decide, commit or change something on behalf of an organisation within a defined scope. It is different from knowing an account’s identity, being able to access a system or being technically capable of performing an action.
Separate the five questions.
Identity identifies the actor. Access concerns systems or information. Capability concerns the available operation. Decision Authority concerns the business mandate. Autonomy concerns independent action within that mandate.
A system can have access to a CRM without the right to agree any commercial terms it chooses.
A commitment is not only an API call.
The technical action may be “send offer.” The business decision may be whether a nine-percent concession is acceptable. The applicable authority can depend on the customer, value, policy, evidence and conditions.
The runtime needs the relevant business boundary, not merely a successful authentication.
One exception does not change the policy.
Suppose the standing limit is five percent. A Commercial Director approves a one-time nine-percent exception. The exception is scoped to that request; it does not become a new limit for every future customer.
Increasing the agent’s autonomy should not silently expand the right to change the governing policy.
How Dainin applies the concept.
Authority Lock is Dainin’s name for the boundary mechanism around supported decisions and actions. Decision Ledger keeps the relevant evidence, authority, actor, decision and outcome connected.
Try the fictional example to inspect the difference between pending, approved and declined. It records no real business commitment.
Bring one business question.
Explore the relevant Dainin workflow and the decisions behind it.
Request a demo