Whitepaper · The Accountability series · Paper 6

Independent Assurance

How an enterprise can stand behind an agent’s work.

AuthorSrinivasarengan Varadharajan, Founder & CEO

Published2 November 2026

Read14 minutes · 5 pages

Abstract

An enterprise can stand behind an AI agent’s work only when three things are separated: the agent that produces the work, the check that clears it, and the person who decides on it.

The five earlier KTER papers named the gaps that open when they are not: accountability, blast radius, consequence, visibility and evidence. This paper states the thesis those papers were circling, describes the method KTER built to it, Independent Assurance, and reports what building and running it taught us.

The method is simple to state. Every piece of work an agent delivers is checked in full by a function separate from the agent, and ends in one of three documents. A named person decides. The decision and the evidence are sealed in a record anyone can verify. If the work is wrong, it is done again at no charge. The paper does not claim this removes error. It claims that error becomes visible, attributable and recoverable, which is what accountability has always meant in professional work.

Section 1

The five gaps

The earlier papers in this series each named one way an enterprise ends up carrying risk it cannot see. Read together they describe a single structure that is missing, not five separate problems.

AccountabilityEvery major vendor disclaims liability at the handoff. Accountability closes by contract and operations, not by a feature.

Blast radiusA permission that is not enforced is a suggestion. Both boundaries must hold, and both must be decided before the agent runs.

ConsequenceA person carries an absorbed sense of consequence. An agent has none unless it is specified in advance, in writing.

VisibilityA green dashboard verifies activity, not judgement. Understanding has to be checked on a schedule by a named person.

EvidenceAcceptance needs a record the agent cannot rewrite, a verifier outside the producer, and a named person with the authority to refuse.

Each paper ended at the same place: the fix is structural, and someone has to build it. This paper is the account of building it.

Section 2

Three separations and one consequence

An AI workforce is accountable when the work, the check and the decision are held by three different parties, and when a wrong result has a consequence the provider bears.

Separation 1The producer never clears its own workThe agent that does the work has no write access to the evidence used to judge it and no say in the acceptance rule.

Separation 2The check never decidesAssurance clears or returns work. A named person in the client’s organisation decides, with the evidence in front of them.

Separation 3The decision never rewrites the recordEvery result, check and decision is sealed as it happens, with a reference the client can verify later.

The consequence: the provider answers for the result. Work that was cleared, decided and sealed, and later proves wrong, is done again at no charge, and the correction is recorded against the original. A standard with no consequence is not a standard. This is the one element no vendor terms of service today contain, and the one that makes the other three worth building.

The three separations are a property of architecture, not of policy. A policy that says the reviewer is independent can be ignored under deadline pressure. An architecture in which the producer has no path to the evidence cannot be.

Section 3

The method, as the client sees it

KTER implements the thesis as three named layers. Independent Assurance clears the work. Executive Oversight decides. The Record seals it. Every piece of work an agent delivers is checked, in full, by a function that is separate from the agent that produced it, and ends in exactly one of three documents.

CertificateEvery statement in the work met its standard. The work goes to the person who decides.

Work NoticeThe work has findings, each stated as what failed, where, and why. The person decides whether to send it back with their own input.

DeclinationThe work was outside the agent’s scope and was not attempted. The person decides whether the scope should change.

Nothing leaves assurance without one of the three. A Work Notice is not a failure of the system; it is the system doing what a reviewer is for. A client who never sees one should ask why.

Sections 4 to 6: what running it taught us, how an enterprise uses it, and its limits.

Download the full paper

The Accountability series

The Accountability GapPaper 1 · July 2026 Trust Has a Blast RadiusPaper 2 · July 2026 The Consequence GapPaper 3 · July 2026 The Visibility DebtPaper 4 · August 2026 The Evidence GapPaper 5 · October 2026 Independent AssurancePaper 6 · 2 November 2026 · This paper

Download

Tell us who is reading and the PDF opens at once. We write to you only about this paper, and only if you ask. Privacy notice.