Seal evidence pack (sample)
===========================

This is a real receipt emitted by the Seal production gateway on
2026-07-24 and signed with Aqta's published verifying key. It is
published as a sample so a reviewer can check the format, and the
verification path, without a pilot and without an Aqta account.

Verify it offline
-----------------
  npx aqta-verify-receipt@1.0.7 receipt.json --key "$(cat PUBLISHED_KEY.txt)"

or in Python:

  pip install aqta-verify-receipt
  python -c "import json;from aqta_verify_receipt import verify_receipt; \
    print(verify_receipt(json.load(open('receipt.json')), \
    trusted_public_key=open('PUBLISHED_KEY.txt').read().strip()).valid)"

Neither command contacts Aqta. Change one character in receipt.json and
the signature stops matching.

Contents
--------
- receipt.json              ATTESTATION-v1 envelope (12 fields + signature)
- rules_in_force.json       Policy ids and text in force at decision time
- countersignatures.json    COUNTERSIGN-v1 layers (empty for this sample)
- PUBLISHED_KEY.txt         The verifying key to pin
- README.txt                This file

What this pack proves, and what it does not
-------------------------------------------
It proves that this gateway, holding this key, recorded this outcome for
this request hash at this time, and that the record has not changed since.

It does not prove the decision was correct, it does not prove which model
weights served the call, and it does not prove anything about text that is
not in the envelope. The full threat model is published at
github.com/Aqta-ai/attestation-spec/blob/main/THREAT-MODEL.md

The signer is not the subject: verification uses a published key and never
calls back to Aqta or to the operator being reviewed.

Format: ATTESTATION-v1. Spec: github.com/Aqta-ai/attestation-spec
