Insights / 05

The defining risk of an autonomous system is not intelligence alone, but the authority attached to its decisions.

Independent software assuranceSM / 05.37

SecondMark position

Assurance should map every route from observation to decision to effect, including delegation, approval, interruption, and recovery.

The examination is bounded to defined claims, a versioned system, and evidence that can be traced to the state under review. Any material exclusion or uncertainty remains visible in the conclusion.

01

Core questions

What the examination needs to establish.

  1. 01

    What can the system cause in the world?

  2. 02

    Which approvals are substantive rather than cosmetic?

  3. 03

    Can delegated authority expand recursively?

  4. 04

    What survives when execution becomes uncertain?

02

Evidence model

Evidence is assembled around the claim—not the folder structure.

01

Explicit definitions

Collected, attributed, challenged, and connected to the exact system boundary under examination.

02

Reasoned assurance principles

Collected, attributed, challenged, and connected to the exact system boundary under examination.

03

Practical system implications

Collected, attributed, challenged, and connected to the exact system boundary under examination.

04

Boundaries and counterexamples

Collected, attributed, challenged, and connected to the exact system boundary under examination.

Intended outcome

An authority-centered model for evaluating autonomy beyond benchmark performance, with attention to interruption, attribution, and recovery.

A sharper decision frameQuestions for system stewardsPractical next steps
03

Professional boundary

What an opinion does—and does not—mean.

It provides

A traceable independent conclusion on defined claims, grounded in the evidence and system state examined.

It does not provide

A guarantee that failure is impossible, a permanent certification, or a conclusion beyond the stated scope and validity conditions.