Dainin architecture

You decide how much of the wheel to hand over.

Technical ability is not delegated authority. Authority Lock keeps business decision boundaries explicit as autonomy increases.

Discuss your use case Explore the architecture

Separate the five questions.

Identity: who is acting. Access: what it may see or reach. Capability: what it can technically do. Decision Authority: what it may decide or commit. Autonomy: how independently it may act within that authority.

More autonomy does not increase authority.

A system can move from observation to advice, creation, execution or operation while the standing business boundary remains unchanged.

Observe

See the relevant state.

Advise

Recommend a next move.

Create

Prepare the work.

Execute

Carry out an approved task.

Operate

Manage a bounded workflow.

Autopilot

Act independently within the same defined authority.

5% standing authority. 9% requested.

Dainin can identify the opportunity and prepare the work. If the commitment exceeds the delegated limit, the decision stops at the boundary and moves to the appropriate person.

Illustrative account A-043Northstar OperationsOrganisation Double v41Personal Double v12Policy v3 · 5% limit

Requested9%

Standing authority5%

Authority Lock

This commitment needs you.

The proposed discount exceeds delegated authority. No offer is sent while the decision is pending.

Policy: Commercial discount · v3
Evidence: Prospect reply + opportunity brief
Decision owner: Commercial Director
Action status: Paused; no commitment made

Interactive illustration. No real offer, policy or customer record is changed. Approval here does not send anything.

Exceptions stay scoped.

A one-time approved exception does not silently change the standing policy for every future decision.

Understand Decision Authority Try the decision example

Bring one business question.

Explore the relevant Dainin workflow and the decisions behind it.

Request a demo