ADR / 013

Grant agent authority per action and consequence, never by confidence

Classify every action an agent could take—read, recommend, draft, execute, human approval or forbidden—by its consequence and reversibility. Confidence changes how work is presented, not who may commit it.

Reference pattern

Independently created. Contains no employer or client implementation detail, internal names or figures.

01Context

An agent that prepares commercial records performed well in a pilot, and a proposal followed to let it act on its own above a 95 % confidence score. In the pilot, a 97 % match to the wrong legal entity created a real opportunity; the score was high, the consequence was high, and nothing stopped it.

02Decision drivers

  1. D01

    Some agent actions are irreversible or external

  2. D02

    Confidence is uncalibrated for rare, high-impact cases

  3. D03

    Accountability must sit with a named person for consequential decisions

  4. D04

    The authority model must be testable in evaluation

03Options considered

Options considered: when each would be the right choice, what it costs, and the verdict under these premises
OptionRight whenCost / trade-offVerdict
Autonomy above a confidence thresholdCheap, reversible actions onlyTurns a score into a permission; fails on confident errorsRejected
Human approval for everythingAn early pilot, where every action is still being learnedReviewers rubber-stamp; the agent saves littleRejected
Authority per action, set by consequence and reversibilityAgents that act in systems of recordAn authority matrix to design, own and testSelected

Every option is right under some premises. The verdict applies to the context above.

04Decision

Maintain an authority matrix for every action an agent could take, classified as read, recommend, draft, execute, human approval or forbidden, from its consequence and reversibility. Low-consequence, reversible actions may execute; consequential ones always require a named person, whatever the confidence; forbidden actions are not exposed as tools. Confidence and ambiguity decide whether the agent continues, retrieves, asks, escalates or stops—within that authority, never beyond it. Authority stops are a release gate in evaluation.

05Consequences

What this choice changes elsewhere in the system.

  1. Risk

    High-confidence errors on consequential actions are caught by design.

  2. Human review

    Reviewers see fewer, better-prepared decisions.

  3. Governance

    Widening autonomy becomes an explicit, owned decision per action.

  4. Evaluation

    Evaluation can test “did it stop when it had to” as its own dimension.

06Revisit when

The decision holds while its context holds. Challenge it when:

01

An action proves both reversible and low-consequence in production data.

02

Regulation or policy changes who may take a decision.

07Where this decision is applied

The decision says why this path was chosen; each case shows how it takes part in a larger architecture.

  1. AI case / 01Designing evidence-grounded AI preparation for commercial decisionsOne architecture used before a customer visit and before an account review: governed context assembled deterministically, a context contract per source, every statement typed and cited, bounded read-only tools, explicit behaviour when context is stale, conflicting or missing—and the decision left with a person.AI & Agentic WorkflowsRevenue OperationsData & IntegrationsArchitecture case · 12 min
  2. AI case / 02Designing AI-assisted intake for unstructured commercial workA shared commercial entry point turned into structured, owned work: a taxonomy written before the model, mixed intent decomposed into work items that share one source reference, entities offered as evidence-backed candidates, owners and clocks assigned by deterministic rules, review placed where ambiguity becomes consequential—and no external commitment without a person.AI & Agentic WorkflowsProcess ArchitectureAutomationArchitecture case · 11 min
  3. AI case / 03Designing AI-assisted data stewardship without moving master-data authorityAI that makes stewards faster without becoming the steward: candidates found, ranked by impact and explained with evidence and differences; a governed steward queue; identity, merge and consequential classification decided by accountable people; accepted decisions executed by the system’s own processes; and outcomes that improve evaluation and rules—never the model’s permissions.AI & Agentic WorkflowsData & IntegrationsSystems & CRM ArchitectureArchitecture case · 10 min
  4. AI case / 08Redesigning RFQ processing around AI without moving commercial authority to the agentAn operating-model redesign of RFQ processing: which work needs reasoning, which is a deterministic rule and which carries business authority—then an agent that prepares requests with evidence and never commits them.AI & Agentic WorkflowsProcess ArchitectureSystems & CRM ArchitectureArchitecture case · 9 min

Decisions this one depends on, or constrains.

  1. ADR / 014Expose agent capabilities as bounded tool contracts, not raw system APIsEach tool states purpose, input, output, permissions, preconditions, side effect, failure and reversibility—and enforces them in code, so the prompt is not the last line of defence.Proposed patternAI · Integration · Security