Second Edition · 2026 Kindle ebook

When Scores Become Authority

A Field Manual for Audit-Survivable Decision Support

Computation may evaluate evidence and surface tension. It must not authorize irreversible action.

Includes operating checklists, evidence-boundary tests, Block/Contest/Signal gates, implementation patterns, and audit questions for high-stakes decision support.

Author

From material-damage practice.

Jason Saunders is an AIC and ASE Master-certified material-damage professional whose experience spans automotive repair, shop operations, and carrier claims. His work focuses on evidence-governed advisory systems that help reviewers locate unsupported assertions without transferring decision authority to AI.

Who it is for

Written for people who must locate the decision.

The greatest risk in modern decision-support is not an incorrect score. It is an untraceable act: a number that quietly became permission. This manual is written first for claims, regulated AI and governance, and the people who build those systems. The same failure mode appears in clinics, filings, and command posts.

  • Insurance and claims

    Leaders who cannot let a severity score, model output, or workflow state stand in for a named authorization on money, coverage, or settlement.

  • Regulated AI and governance

    Teams that may evaluate evidence but must remain non-decisional—and officers who must reconstruct who authorized an act, at what time, and on what evidence.

  • Decision-support builders

    Architects who need a field architecture—gates, tension, and human authorization—rather than another confidence dashboard.

Also applies in

  • Health / clinical decision support

    Scores and model outputs must not silently authorize irreversible clinical acts. Named humans remain accountable.

  • Legal

    Filings, settlements, and liberty-affecting or irreversible legal acts cannot be authorized by a score alone.

  • Command and control (C2)

    Evaluation may inform the operational picture. The system must not authorize irreversible operational acts.

What you will learn

Evidence-Aligned Tension, in operating language.

EAT draws a hard line between evaluation and authorization. The system may analyze the record and surface tension. A human remains the only party who can authorize an irreversible act.

Flow diagram of the Evidence-Aligned Tension framework. EAT evaluates the record, then three controls operate in parallel: EDIK when a claim outruns the evidence, ETM for tension instead of confidence, and CBAC so no irreversible act proceeds without a human. Those controls feed three gates: Block, Contest, and Signal. Rule: Humans authorize irreversible acts. The system does not.

Operating sequence

EAT Evidence-Aligned Tension
EDIK Claim vs. evidence
ETM Tension, not confidence
CBAC Human authorization
Block
Contest
Signal

Humans authorize irreversible acts. The system does not.

01 · EDIK

When a claim outruns the evidence

Detects when a statement exceeds what the record can actually support. Confidence is not a substitute for coverage. If the claim is larger than the evidence, the system says so.

02 · ETM

Tension instead of a confidence score

Replaces misleading confidence with measurable evidence tension. High certainty on a thin record is a failure condition, not a green light.

03 · CBAC

No irreversible act without a human

A structural control: the system cannot take—or silently become—the authorization. Named humans remain accountable. The audit trail is deterministic.

Three gates. One rule.

Humans authorize irreversible acts. The system does not.

  1. Block

    The record cannot support the act. Evaluation stops short of permission.

  2. Contest

    Tension is unresolved. A human must engage before anything irreversible proceeds.

  3. Signal

    Evaluation may inform judgment. It still does not authorize the act.

Inside the manual

The field outline, and a sample of the cadence.

The book is an operating manual, not a slogan deck. Below is the working outline and one drill from the Monday Morning cadence—enough to see the method, not a substitute for the playbooks.

Table of contents

Field-manual outline

Chapter-style headings. No page map. No claim of regulatory endorsement.

  1. 01 Locating silent automation
  2. 02 Evidence-Aligned Tension (EAT)
  3. 03 EDIK — when a claim outruns the evidence
  4. 04 ETM — tension instead of confidence
  5. 05 CBAC — no irreversible act without a human
  6. 06 Block / Contest / Signal gates
  7. 07 Monday Morning Checklists and operating cadence
  8. 08 Implementation patterns for builders and auditors
  9. 09 Cross-domain operating patterns: insurance, health, legal, C2

Sample · Operating cadence

Monday Morning Checklist

Before the week opens, locate last week’s silent automation: the places a score already functioned as permission without anyone saying “approve.” The drill is four questions. The playbooks sit behind them.

  1. 01

    Where did a score, model, or workflow state function as permission last week?

  2. 02

    Can you name the human who authorized each irreversible act—and the evidence they were given?

  3. 03

    Which outputs claimed more than the record could support?

  4. 04

    Which queues still default-accept when tension is unresolved?

Buy on Amazon for the full playbooks

Research

The architecture is on the record.

The field manual sits on open research and live production systems. Read the papers first if you need the formalism; buy the book if you need the operating cadence.

  • SSRN · 6507718

    Evidence-Aligned Tension — Full Research

    The full research treatment of Evidence-Aligned Tension as a non-decisional decision-support framework.

    Read on SSRN
  • SSRN · 6166447

    Formal Governance Architecture for Non-Decisional AI

    The governance architecture that keeps evaluation on one side of the line and human authorization on the other.

    Read on SSRN

FAQ

Straight answers before you buy.

Short record. If you need the formalism, start at the research. If you need the cadence, buy the manual.

Who is this for?

Insurance and claims, regulated AI and governance, and decision-support builders. It also applies in health and clinical decision support, legal work, and command-and-control (C2). The line is the same in each domain: evaluation may inform; it must not authorize. See audience.

Is this legal or compliance advice?

No. This site and the book are informational and educational. They are not legal, regulatory, compliance, tax, or other professional advice. See the disclaimer.

Kindle only?

Yes. The book is a Kindle ebook on Amazon.

What is the core claim?

Computation may evaluate evidence and surface tension. It must not authorize irreversible action.

Does this endorse any carrier or vendor?

No. No affiliation with any insurer, regulator, platform, or employer is claimed or implied.

Where is the research?

On the record: SSRN 6507718, SSRN 6166447, and the Conversational Computing whitepaper PDF on this site.

Buy the manual. Read the architecture.

Second Edition, 2026. A field manual for people who build or govern decision support where the act must survive audit.