GlossaryOriginSpecs

Glossary

Self-Attestation Oxymoron (SAO)

A Self-Attestation Oxymoron (SAO) is an assurance claim that is produced, judged, signed and stored by the same party whose performance the claim describes. The claim presents itself as independent evidence while containing none.

ProofJack Rating: Human 100% · AI 0% (self-estimated; PP-SPEC-023, 17 September 2026, by Craig Thomas Ellrod)

Also known as: SAO, Self Attestation Oxymoron

Mynted 2026-10-20 · Updated 2026-10-20

First used: PP-SPEC-023, 17 September 2026, by Craig Thomas Ellrod (DOI 10.5281/zenodo.22821379)

What it means

Attestation means a party vouches for something. Self-attestation means a party vouches for itself. That is a legitimate baseline: it is verification, and every buyer should check it.

The oxymoron appears when self-attestation is presented as proof. A claim cannot be both self-produced and independent. When one party runs the test, sets the threshold, decides the result, signs the record and keeps the record, the claim describes the party’s opinion of itself, however it is packaged.

The test

A claim is an SAO when every one of these roles is held by the same party:

Role Question
Verifier Who ran the check?
Judge Who set the threshold and decided pass or fail?
Issuer Who issued the result or credential?
Trust anchor Whose key signed it?
Record keeper Who holds the evidence?

If the answer to all five is the same name, the claim is a Self-Attestation Oxymoron. If even one role is held by an independent party with access to the evidence, it is not.

Why it matters

An SAO borrows the language of proof (certified, verified, cryptographically secured, tamper-evident) without the substance of proof: an independent witness. Buyers, auditors and insurers who accept it inherit the issuer’s undisclosed failure rate as unpriced risk.

The problem gets worse with AI agents. An agent reporting “task complete”, “policy enforced” or “identity verified” about its own actions is an SAO by construction, and agents make those claims at machine speed with no human reviewing the outcome.

What it is not

How to resolve one

Move at least the witness role outside the party’s trust boundary. Under Proof of Efficacy, expected outcomes are committed before the test, the test runs under real adversarial conditions, and the actual outcome is captured by a witness the system under test does not control.

Example

A vendor runs its own detection test, scores its own results, publishes a signed report from its own certificate, and hosts the evidence on its own servers. The report may be correct. It is still a Self-Attestation Oxymoron, because every role in the chain belongs to the vendor.

Where the term comes from

First defined by Craig Thomas Ellrod in PP-SPEC-023, Structural Independence and the Fidelity-at-Capture Requirement, 17 September 2026 (DOI 10.5281/zenodo.22821379): a proof of efficacy cannot originate from the entity whose efficacy is in question, not because the entity is dishonest, but because the structure of self-attestation makes independence unverifiable regardless of intent. This page expands that definition with the five-role test.

Related terms

Sources

Updated 2026-10-20