Atestan Atestan

See the model without mistaking a demonstration for production proof

A demonstration is useful for understanding how the model works. It is not evidence that a deployment has reached any level of proof. The one on this page is scripted, labelled as such, and it is the only demonstration this product has — the verification page was deliberately stripped of its own, because a page that looks like it verifies is worse than no page.

01

What to look for

No simulated certainty

A polished interface must not imply that a capability exists in production when it does not. What is demonstrated conceptually is labelled as such — and nothing on this page performs live cryptography, so it is a representation of the model, not a substitute for independent validation.

The useful question during a demonstration is not whether the screen turns green. It is: what exactly has the system established, and what has it deliberately not claimed? That is the discipline this product is built to bring to a critical communication — and it is what the three cases below are arranged to show.

02

Watch a verification run

The same message — “our bank details have changed” — in three situations that differ only in what the issuer can prove. Pick one and watch the ladder.

This is a scripted demonstration

Nothing on this page performs live cryptography. The engine is built and tested but has not yet been ratified by an external cryptographer, and no production registry is anchored. What you are watching is an exact walk-through of what the ladder reports in each case — with the fictional company “ABC SAS”. We would rather show you a labelled demonstration than a convincing illusion.

Your accounts-payable inbox

ABC SAS · billing@abc-sas.example

Change of bank details — invoice 2026-0431

Following a change of bank, please update our details for all future payments. New IBAN below. Kindly confirm once done — the next invoice falls due Friday.

Channel checks (SPF / DKIM / DMARC) PASS — the domain is authentic

  1. Idle — press “Run the verification”.

Claim ladder

  1. Signed by the issuing organisation

    Signature

    Waiting.

    not evaluated

  2. Addressed to your organisation

    Recipient resolution, at the date of issue

    Waiting.

    not evaluated

  3. Receipt acknowledged

    Acknowledgement / workflow

    Waiting.

    not evaluated

  4. Action not executed

    Closure / proven absence

    Waiting.

    not evaluated

  5. Complete proof, publicly anchored

    Public anchoring at closure

    Waiting.

    not evaluated