A business assistant produces a poor answer, so the obvious response is to give it more reasoning time or a more expensive model. Sometimes that works. Often it solves the wrong problem: the relevant record was never retrieved, the operation was forbidden, a required specialist was absent, or the answer needed arithmetic rather than prose.

First diagnose the missing resource

The request 'Why did our margin fall?' may require current transaction data, a controlled aggregation, an interpretation of a known accounting rule and a narrative explanation. If the model has only a customer search tool and no purchase costs, additional reasoning cannot manufacture the missing inputs.

Runtime adaptation should identify the class of the gap. Is the evidence missing? Is there no capability for the needed operation? Is the issue permission, calculation, specialist knowledge, external timing or genuinely unknown reasoning?

The distinction matters for safety as well as cost. An authorization denial is not a puzzle for a smarter model to solve. Nor is an event that has not arrived a reason to keep an expensive thought loop spinning.

Deterministic compute should stay deterministic

Calculating a total, checking a field transition, validating an identifier or comparing two versions of a document can often be expressed as ordinary computation under a clear contract. There is no value in asking a language model to improvise a sum that a calculator can determine exactly.

Deterministic work can still be difficult engineering. The algorithm, input freshness, business semantics and unit conversions must be right. But that is a different kind of uncertainty from interpreting an ambiguous message or proposing an unfamiliar plan.

Use a model to determine when a calculation is needed, if useful; use controlled computation to obtain the number and keep the input and result inspectable.

Bounded decisions and open reasoning

A small selection problem may have a defined set of valid options. Which known capability pack is relevant? Which of three verified work templates matches a request? Does an event satisfy a narrow semantic classification? These are candidates for bounded decision mechanisms.

The key requirement is a genuinely complete candidate space. If the valid answer is missing from the set, a constrained classifier can be confidently wrong. A robust system therefore needs an explicit 'none applies' path and a mechanism to widen the problem when the task is genuinely novel.

Open-ended reasoning remains valuable for unfamiliar investigations, planning, synthesis and recovery. The goal is not to eliminate it, but to reserve it for work that truly requires exploration.

Budget is a systems concern

An agent team can multiply cost in subtle ways. Every child may request its own tools, context projection and model retries. If each actor assumes it has an independent unlimited budget, parallel work can turn into an unintended spending amplifier.

Resources need a notion of scope: a workspace, an Execution, delegated subtasks, tool calls and compute operations may each contribute to an overall cost and time boundary. A dormant wait should not consume inference as though it were an actively running solver.

The budget policy must also distinguish hard limits from preferences. A model cannot authorize itself to exceed permissions or safety boundaries because the task seems important; within legitimate constraints, the system can choose economical or deeper cognition.

Adaptation is not escalation of authority

Suppose a worker cannot read a payment record. Its first response should not be to ask the model for greater confidence, search a public website for an alternate path or quietly switch to an administrative tool. Missing authority is a governance outcome, not a reasoning deficiency.

The runtime may ask for an approved delegation, switch to permitted evidence or surface a human decision. A dynamically assembled worker environment may gain new relevant resources, but never by inventing privileges.

This requirement holds even if the task is important and the next step is obvious. The purpose of an adaptive environment is to fit resources to work, not to bypass the institution that owns the business data.

Measure the entire execution

Benchmark reasoning strategies against concrete end-to-end tasks. Track outcome quality, verification, number of model calls, tool cost, wall-clock time, recoverability and unnecessary retries. A cheap one-step computation that returns the correct result is better than an impressive chain of thought that still does not satisfy the task.

Artemis has adaptive-execution foundations, while its unified differentiated cognition policy is a vNext architecture stream. This article describes the intended division of responsibility, not published numbers or a demonstrated universal cost advantage.

The architectural reference is https://github.com/sarooo17/artemis-architecture/blob/main/docs/05-ADAPTIVE-COGNITION.md.