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

In the delivery model, an approved delivery is sealed into a record and signed with a key kept off the platform. The public checker uses a synthetic demonstration: it shows the technology works, and it is not a real client delivery.

What a delivery contains

  • 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 the work. Their private identity is never given.

  • A statement of unaided work

    The professional states that the judgement is their own and declares any assistance they used.

  • An independent review note

    A second reviewer from the same field of expertise, who did not do the original work.

  • An ECDSA P-256 signature

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

How to check one offline

Four checks, one script and a published key. No account, no API call, no request to us.

  1. 1Recompute the SHA-256 digest of the delivered item and compare it to the digest in the record.
  2. 2Recompute the record hash from the record fields in the documented order, and compare it to the stated hash.
  3. 3Check that each record carries the hash of the record before it, from the genesis value to the last record, whose hash is the chain root.
  4. 4Verify the ECDSA P-256 signature over the chain root against the betaPlan public key you already hold.

Try it yourself

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

Open the checker

What a failure looks like

A sealed record cannot be changed without it showing. Each of the four checks fails in its own way, and you can read which one failed.

  • The item was changed after sealing

    Digest mismatch at step 1. The record still verifies, so you know the record is intact but 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

    Chain mismatch at step 3. Each record carries the hash of the one before it, so the record after the gap no longer matches its predecessor.

  • A record was forged

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

A sample record

Illustrative and invented, in the format of every delivery.

Chain intact, signature authentic

ECDSA P-256

Batch
BP-2026-0417
Task
T-0910
Field
Healthcare
Licence category
Pharmacist
Reviewer identifier
bench/AL-3F92
Unaided
Yes
Independent review
bench/AL-7C41
Review outcome
approve
Sealed at
2026-04-17T09:14:02Z
Chain position
1 / 3

Content digest

b9b5213e99a3c45e45f3ca2fbb35d2fcf716e35c90cdf88dfcce81658719c484

Record hash

5d9c43d3da7e667500a50450759582d900230b4b8a31fbdaa8ee978a3daa93fd

Check the sample record

Change one of its fields and see which check fails.

Open the checkerHuman evaluation