You do not have to trust us. Check the record.

In the delivery model, an approved delivery is sealed into a record and signed off the platform. The public checker uses a synthetic demonstration; it is technical capability proof, not a current client delivery.

What arrives with a delivery

  • The annotated item

    The work itself, in the format you asked for.

  • A content digest

    A SHA-256 hash of the delivered item, computed at seal time.

  • A pseudonymous attribution

    The licence category and the reviewer identifier of the person who did it. Never their private identity.

  • An unaided attestation

    The professional affirms the judgment is their own and names any assistance used.

  • An independent review line

    A second reviewer of the same licence category, who did not do the original work.

  • An ECDSA P-256 signature

    The record root, signed with a key held off the platform.

How to check one offline

Three commands and a published key. No account, no API call, no request to us.

Check one yourself

A sample delivery you can tamper with in your browser, with the four checks running on real hashes. No account, nothing sent anywhere.

  • The delivered work still matches its digest
  • The record fields still match the record hash
  • Each record carries the hash of the one before it
  • The chain root is signed by the published key
Open the checker
  1. 1

    Recompute the SHA-256 digest of the delivered item and compare it to the digest in the record.

  2. 2

    Recompute the record hash from the record fields in the documented order, and compare it to the stated hash.

  3. 3

    Verify the ECDSA P-256 signature over that hash against the betaPlan public key you already hold.

What a failure looks like

A sealed record cannot be edited quietly. Each of the three checks fails in a different, legible way.

  • The item was changed after sealing

    Digest mismatch at step 1. The record still verifies, so you know the record is intact and the file is not.

  • A record field was changed

    Hash mismatch at step 2. The signature no longer covers the record you are holding.

  • A record was removed from the chain

    The next record hashes the one before it. Removing one breaks every hash after it.

  • A record was fabricated

    Signature check fails at step 3. Forging it requires a private key that is not on the platform.

A sample record

Chain intact, anchor authentic

ECDSA P-256

Batch
BP-2026-0417
Task
T-0912
Field
Healthcare
Licence category
Pharmacist
Reviewer identifier
bench/AL-3F92
Unaided
Yes
Independent review
bench/AL-7C41
Sealed at
2026-04-17T09:22:41Z
Chain position
#5

Content digest

3f7a9c1e8b40d25a6f13c9e07b8a4d61e29f5c380a7b14d6e5c2f908a3b71d4e

Record hash

09c5e0a39eeb8088778a077d674a46d39eaf7d3a9fa40e4f168d3e6404dac94a

Illustrative and anonymised. The format every delivery carries.

How we check