Use AI. Keep control. Empower your people.

Explore Athena

Verification

Check the evidence without calling the vendor

An exported record is more useful when a reviewer can check it independently. Here is what an offline check needs, and what it can tell you.

28 May 2026 · 3 min read

Updated 28 October 2026

← All articles

Make the check independent

If the only way to check an old record is to ask the vendor's server, you still depend on that server. It may be unavailable, changed or no longer offered. Evidence tends to have a longer working life than a product roadmap.

Offline verification moves the supported checks onto the reviewer's own machine. The reviewer uses a copy of the record, a compatible verifier and independently trusted public-key material.

Agree what the reviewer receives

Keep the original sealed record and the format information needed to interpret it. Supply instructions for the applicable verifier version. Establish how the reviewer knows which signing key to trust.

A key that arrives inside an unfamiliar file is information, not automatic authority. The reviewer needs a trusted route for that key and any relevant validity or rotation history. Offline does not mean without trust assumptions.

Run a simple test

Use a sample record agreed for the demonstration. Check it with the compatible verifier on a separate machine. Repeat with the network disconnected, then change a signed value and check the altered copy.

  • The original should pass the supported checks with the correct trust material.
  • An altered signed value should fail verification.
  • An unexpected signing key must not be accepted as trusted merely because the file supplies it.
  • Keep the result and the setup used for the test.

Read the result carefully

A successful signature check supports the integrity of the signed content under the trusted key. Depending on the format, other supported checks may examine structure or relationships between an approval and a submitted action.

It does not prove every source observation was true, every relevant event was captured or the decision was lawful. A faithfully signed mistake remains a mistake. Cryptography is quite willing to preserve one.

Keep the handover usable

Ask for a sample record and the compatible verifier for the workflow you are evaluating. Confirm the evidence format, supported checks and trust profile before running the test. An unrelated package with a similar name is not a substitute.

Agree how records and trust material are retained after the engagement ends. Your reviewer should be able to repeat the agreed check without an Aelethion account or a live call to our service. Test that handover before it becomes urgent.

Sources and further reading

Originally published 28 May 2026. Rewritten on 28 October 2026.

Verification questions to ask

Keep exploring