ProofSmith - Independent & Provable - GOVERNED DECISION LINEAGE

National security

A Combatant Commander cannot prove an autonomous action stayed within authority. No fielded system can.

Authority, intent and rules of engagement are written with great care, and then the record of whether they were honored is kept by the system that acted.

On this page

The problem

Authority in a military organization is explicit. It is delegated in writing, bounded in scope and time, and its limits are the difference between a lawful action and an unlawful one. That discipline is old and well understood, and it works, for as long as a human being sits in the decision path, because that human being is the accountability.

Autonomy removes the human being from the path and puts nothing in that place. What remains is a log, written by the acting system, held by the acting system, in the acting system's format. When an inspector general, a coalition partner, a congressional committee or a court asks whether an action stayed inside the authority granted, the answer available is the actor's own account of itself.

The House has asked for the record. The defense authorization bill it passed on 22 July 2026 would direct the Department to update its policy on autonomous and AI-enabled systems so that it preserves human command responsibility for the use of force, identifies the commanders responsible for authorizing it, and sets requirements for auditability, traceability and accountability. A policy can require the record. It cannot produce one that does not depend on the word of the system that acted.

A coalition partner cannot be asked to trust an ally’s internal logs, and cannot be handed the intelligence behind a decision. What the partner needs is what every other reviewer on this site needs: proof that the decision stayed within authority, checkable without the ally’s cooperation. Shared confidence, not shared secrets, moves a coalition at speed. Classification and release authority stay where they are.

Tempo compounds it. Machine decisions are taken faster than any review cycle can follow, so oversight is behind from the first day of fielding, and each new capability widens the gap. The usual response is to slow the system down. That trades tempo for accountability, and no one should have to make that trade.

Authority delegates down the chain of command. Verifiable proof returns up.

Who the record has to satisfy

The record is produced for somebody who was not there.

An inspector general does not ask whether the system was confident. The questions are who authorized it, and where the record is.

Where it bites first

Three of the six, in this order.

AUTHORITY

Proving that an action stayed inside a delegated grant, to somebody outside the chain that executed it.

TEMPO

Keeping oversight in contact with systems that decide faster than people can review.

ATTRIBUTION

Separating error from misuse from adversary action, on the first day of an inquiry rather than the ninetieth.

All six →

Other sectors

The demonstration

Built around your problem, not around our example.

An agent proposes, the decision is adjudicated against authority, and anyone you authorize can verify it afterward. Tell us which of the six is costing you, and that is the one we will build.

Start a conversationRead the argument

We are not asking you to trust us. We are asking you to let us prove it.