Verifiable analytics — at1 qsign
When you report an analytic result — “1,284 transactions over $10k in Q3”, a filtered extract handed to a regulator, a number on a dashboard — the recipient has to trust it really came from the stated data, unaltered. at1 qsign runs a predicate/projection query against a queryable .at1 and emits an Ed25519-signed receipt that binds three things together: the SHA-256 of the exact source container, the canonical query, and the SHA-256 of the result rows. Anyone with the public key and the source file can re-run the query and verify the signature — proving the reported result is genuine and the source wasn’t swapped or edited.
Use it
# 1) make a signer keypair
at1 qsign keygen --out-key signer.key --out-pub signer.pub
# 2) run a query and emit a signed receipt
at1 qsign sign txns.at1 --signing-key signer.key \
--where amount:10000:60000 --select id,amount,region --out receipt.json
# 3) anyone with the public key + the source file can re-check it
at1 qsign verify receipt.json txns.at1 --pubkey signer.pub
# -> verified: true (tampered source / forged count / wrong key -> false)What it proves
- Provenance — the result was computed from this exact file (source hash bound).
- Integrity — the reported rows and count match a fresh re-run (result hash + count bound).
- Authenticity — signed by the holder of the private key; pin an expected public key to prove who.
Swap the source for an edited copy, forge the count in the receipt, or present a different signer, and verification fails. This is the AT-1 verified thesis applied to analytics: not just compressed and queryable, but provable.
Pairs naturally with the confidential clean-room (scoped query grants) and the AT-1 Ledger (tamper-evident event log).