Mandates

Mandate is not a separate term in the model’s glossary. This page gathers a subject that cuts across Governance, the Execution Policy and the Commercial Gate: how a decision can be delegated, to a person or a system, and where that delegation stops.

What question does this solve?

If every decision needed a fresh human approval, a service built on small, frequent advances would drown in waiting. If systems could decide anything they were technically able to do, nobody could trust the service. Delegation has to be explicit enough that a system can decide on its own within a scope, and recognize exactly when a question lies outside it.

What a mandate is

A mandate is a delegation that allows a function or resource to take certain decisions within defined conditions. It states its scope, its limits and the responsibility associated with it. A mandate can allow contextual judgment: a delegated authority can compare alternatives and choose a solution consistent with objectives and conditions, not only execute fixed rules. What it must make possible is to recognize when a choice falls within its scope and when it needs another decision.

Three separate authorities

The central point is that different parties hold different authorities, and each can delegate its own without granting the others.

Party	What it can delegate	What its delegation does not grant
The buyer	Purchasing continuation within a ceiling, and business choices within stated criteria.	Authority for the provider to issue arbitrary offers, or permission to act in production.
The provider	Forming offers, allocating work, and technical acceptance.	Authority to spend the buyer’s money beyond the commitment.
Whoever runs the environment	Permission to deploy a revision that is ready.	Authority to change the scope or accept an output.

Technical autonomy is not purchasing authority. A system that can build an alternative has not been authorized to buy it. A buyer’s economic authorization does not let the provider act in production without the corresponding authority. A fully autonomous path does not concentrate every authority in whoever executes.

How a mandate works

It has conditions, not only a ceiling. Budget availability alone is not enough. A mandate to buy continuation can require, for example, that the result is usable, the integration is identified, acceptance criteria are defined and commercial terms are compatible. The authorized system checks those conditions and the validity of the offer before deciding.

It can be simple or automated. Within an established limit, the decision mechanism can be simple or automated, provided it recognizes the authorized scope and routes exceptions.

What remains is authority, not money. When a delegated decision commits less than the ceiling, the difference is uncommitted authorization. It is not spending, it is not the provider’s revenue, and it is not general permission to produce extra features.

Silence is not consent. A missing response is not authorization, unless a rule agreed in advance gives it that meaning within clear limits. The operation must recognize which rule actually applies rather than invent one while waiting.

It can be revised or withdrawn. Work in progress must take the change into account. Withdrawing an authorization does not confirm that an action already started has stopped.

It meets its limit through escalation. When a question exceeds the mandate, it is routed through Escalation to whoever can decide, which may be another system with a sufficient mandate or a person.

Why it matters for the hypothesis

Mandates are where engineering control and the economics of recurring service meet. The cost of defining and maintaining a mandate can be spread across the admissible decisions of successive demands, instead of rebuilding an approval for every step. Automating a decision this way is a hypothesis about reducing latency and coordination effort. It has to be evaluated together with the quality of the decisions made and the cost of handling exceptions. Automating only the final answer, without making it cheaper to prepare the decision, may shorten one wait without making the rest of the route sustainable.

In the running example

After discovery, priced at 20, the provider offers to implement, evaluate and deploy booking for 80; reminders would add 15, making 95. The barbershop has delegated the continuation under an additional ceiling of 90, separate from the price of discovery, conditional on usable booking, an identified integration, defined acceptance criteria and compatible commercial terms.

The authorized system checks those conditions. Booking at 80 fits the mandate; booking with reminders at 95 does not. The system accepts the offer at 80 and records scope, price and references. Ten remains as uncommitted authorization, which does not make the reminders partly bought. If the essential technical conditions had not been clarified, even the offer at 80 would not go ahead under this mandate: the mechanism would defer, ask for clarification or route the question.

The barbershop’s authorization to spend does not allow the provider to deploy without the environment’s permission, and the environment’s permission does not widen the scope. A direct human decision could have produced exactly the same choice; the example shows how the function can be delegated, not that it must be.

Boundaries and failure modes

A vague mandate is not a mandate. A rule that says only “use good judgment” may not tell a system what it is allowed to do when a relevant exception arises.

Delegation does not transfer responsibility away. Holding responsibility is not the same as executing each decision. Engineering and responsibility for the effects stay identifiable even when authorized systems take every decision in a demand.

Mandates have a cost. Defining, maintaining and auditing them takes effort. Their advantage depends on how many admissible decisions they cover and on how well exceptions are handled; the right limits of delegation remain an open question.

Connected concepts

• Engine overview
• Previous: Governance, the rules and responsibilities mandates belong to
• Execution Policy, autonomy over work and decisions
• Commercial Gate, the economic decision a buyer’s mandate can delegate
• Glossary