Expound/Platform/Finality Assurance™

Finality Assurance

Generation gives you a candidate. Evaluation gives you a score. Acceptance (a named person may rely on this, for this purpose, now) is the scarce act, and it is the one Finality Assurance Standards (FAS) computes. From evidence anyone can re-check, not the word of the system that did the work.

The governing distinction

Generation. Evaluation. Acceptance.

Without Finality Assurance, the agent decides. Done is inferred from the answer of the party with the least incentive to look closely, and taken by everyone downstream because there is nothing else on offer.

Any architecture answers the question of who decides what done means, most by default, and without recording that it did. Of the three answers below, the third is the scarce act.

Generation: a candidate

Can the system produce an output? Answered by the system itself, about itself. Abundant, and getting cheaper.

Evaluation: a score

How well do outputs perform across a population? A statistical claim about a distribution, not about the result in front of you. A system can hold a strong aggregate score and have issued the one answer that is currently wrong.

Acceptance: a named party may rely, now

Has someone with the authority to do so accepted this result as doing what it was for, on evidence attached to it, so that this party may act on it for this purpose right now? This is what FAS computes.

Generation≠Evaluation≠Acceptance

Computed separately

None taken on the agent’s word.

FAS computes each of these separately and takes none of them on the agent’s word: what the result is about, who has standing to accept it, whether the required effect happened, whether an authority accepted it, whether that acceptance is settled, and what the result may be used for right now. Identity is not authority. Authority is not occurrence. A call returning is not the required effect happening. Approval is not acceptance. Reliance is the last of these computations, not the first.

Approval≠Acceptance

Settled then≠Relied on now

What differentiates it

Seven things that hold together as one thing.

Regulated industries built versions of several of these, each welded to its own domain. FAS holds all seven together as one portable system, specified precisely enough to be implemented under license and tested for conformance. Take any one away and the others stop working.

01

A graded verdict

Computed after the work happens rather than set before it or during it.

02

More than one way to pass

Each tied to a different decision it lets you make. Not just yes and no.

03

Conservative composition

Each evidence class carrying a ceiling fixed in advance, so no amount of weak evidence adds up to a strong conclusion.

04

Independent occurrence

Established through a path capable of contradicting the agent’s own account of what it did.

05

A check that can only lower

It can lower a verdict, cap it, or refuse it, and can never raise it. The asymmetry is what makes the check worth having.

06

Licensed, recorded reliance

Licensed to a named party and recorded, so it can be withdrawn from that party later.

07

Learning that cannot promote itself

A mechanism that learns from its own results cannot put itself in charge.

Grades without ceilings are opinion with numbers on it. Ceilings without an independent occurrence path grade the agent’s own story. A check that can raise as well as lower is a second producer. Reliance you cannot withdraw is not reliance; it is release.

A precise claim

Exactly what a verdict tells you.

That what was asked for was produced, that the evidence for it is bound to it, and that an authority with standing accepted it against conditions declared in advance, and that all of this still holds at the moment you rely on it.

It says so in a form a party who did not do the work can recompute. That is the claim you hand to an auditor, a regulator or a counterparty.

Asserted≠Computed

Recorded then≠Valid now