Who Owns the Decision Logic? Why the Decision Layer Must Belong to the Enterprise, Not the Model Provider
Models can be rented. Judgment cannot. The rules that turn a model’s output into an organizational decision are the part of AI an enterprise must own.
The decision logic layer is the explicit, versioned set of rules that turns a model’s output into an organizational decision: who may decide what, which thresholds and policies apply, what evidence is required, when human approval is needed, and how outcomes are recorded. In a well-designed AI architecture the enterprise owns this layer; the model provider supplies a component inside it.
The quiet transfer of judgment
Most enterprise AI programs start with a model choice: which provider, which model, which assistant. The decisions that matter come later and are rarely named. A credit limit, an escalation threshold, a supplier risk score, the line between “recommend” and “execute” — these end up written into prompts, buried in a vendor’s assistant configuration, or left to whatever the model happens to infer.
When that happens, the organization has not just bought technology. It has handed over part of its judgment. The logic is implicit, so nobody can review it. It changes when the provider updates the model, so last quarter’s decisions cannot be reproduced. It does not move when you change provider, so switching costs are not technical — they are institutional. And when an auditor or a regulator asks why a decision was made, the honest answer is “the model decided”.
Model versus decision logic: who owns what
| Model provider | Enterprise | |
|---|---|---|
| What it owns | Model weights, general capability, inference infrastructure | Decision rights, rules, thresholds, authority limits, approval gates |
| What it knows | The world in general | Its own data, context, constraints and history |
| What it answers for | Model performance and availability | The decision and its consequences |
| How it changes | On the provider’s release cycle | Through the organization’s own governance, versioned and reviewed |
The model is a component inside the agentic-intelligence layer, not the seat of authority. It reasons, drafts and proposes. The decision logic layer decides what happens next.
What belongs in the decision logic layer
- Decision rights — which role, agent or person may decide, recommend or only inform, for each class of decision.
- Policies and thresholds — limits, scores and conditions written as explicit rules, not as instructions inside a prompt.
- Evidence requirements — which data a recommendation must cite before it is acted on, and which source counts as the source of truth.
- Approval gates and escalation paths — where a human must approve, who that human is, and what happens if they do not respond.
- Risk tiers — how much autonomy each action gets, set by the consequence of the action (see Risk-Proportional Determinism).
- Decision memory — every decision with its evidence, approver and outcome, so the organization learns from results instead of the vendor learning from your data.
Five tests: do you own your decision logic?
- Portability. Could you replace the model next month without rewriting a single business rule?
- Traceability. For any decision, can you show which rule, which evidence and which approval applied?
- Versioning. Are thresholds and policies versioned in your systems, rather than embedded in prompts or vendor settings?
- Readability. Can an auditor or a business owner read the rules without reading a prompt?
- Learning. Do verified outcomes feed back into your own rules and memory?
If the answer to most of these is no, the decision logic currently belongs to whoever runs the model.
Why this matters for governance and regulation
Accountability cannot be outsourced to a model provider. Under the EU AI Act, organizations that deploy high-risk AI systems carry their own obligations, including human oversight and record-keeping. ISO/IEC 42001 asks the organization to run its own AI management system — risks, controls, roles and evidence. Both assume something an implicit, provider-hosted logic cannot give: decisions whose rules the organization can name, show and change.
Owning the decision logic also makes the architecture choice simpler. When the rules live with the enterprise, the model can run in the cloud for one task and on local hardware for another, without the decisions changing.
How Indigonix builds it
Agenticos makes the decision logic explicit at design time. From a process document it produces the workflow, the agent team, each agent’s authority limits and approval gates, governance notes and a test plan — artifacts the organization owns and can review. CompanyBrain runs that logic on top of the organization’s existing systems. Its model-management role decides which model runs where, in the cloud or locally, while the rules stay the same; every recommendation arrives with the evidence behind it, and every decision is recorded with its approver and outcome. The broader architecture is described in Enterprise AI Architecture.
Frequently Asked Questions
What is a decision logic layer?
The explicit, versioned set of rules that turns a model’s output into an organizational decision: decision rights, policies and thresholds, evidence requirements, approval gates and escalation paths, risk tiers, and a record of decisions and outcomes.
Why should the enterprise, not the model provider, own the decision logic?
Because the enterprise answers for the decision. When the logic lives in prompts or a vendor’s configuration it is implicit, changes with every model update, cannot be audited and does not move when you change provider. Owning it keeps decisions reproducible, auditable and portable.
Does owning the decision logic mean building our own model?
No. The model can be rented, in the cloud or run locally. What the enterprise owns is the layer around it — the rules, authority limits, approval gates and decision memory. The model is a component inside that layer, not the seat of authority.
How can I tell whether we own our decision logic today?
Ask five questions: could you change the model without rewriting business rules; can you trace any decision to its rule, evidence and approval; are thresholds versioned in your own systems; can an auditor read the rules without reading a prompt; and do outcomes feed back into your own rules?
How does this relate to the EU AI Act and ISO/IEC 42001?
Both place obligations on the organization that uses AI — human oversight and record-keeping for deployers of high-risk systems under the EU AI Act, and an organization-run AI management system under ISO/IEC 42001. Explicit, enterprise-owned decision logic is what makes those obligations demonstrable.
Indigonix designs governed enterprise intelligence architectures, agentic systems and AI governance programmes. Talk to us about an assessment, workshop or design engagement.
Contact usSee servicesTrainings & workshops← Indigonix System Intelligence