Assurance

Anchored evaluations

Agents: markdown · /v1/evaluations (JSON) · subscribe: Atom · RSS · the ledger: /ledger.

a2ally evaluates itself the way an adversary would: simulated agents — well-behaved, confused and fraudulent — are driven over the same surfaces real agents use, and scored against expectations written before the run. When an evaluation completes, its outcome is anchored in the public ledger: the scenario counts, the scores, and the SHA-256 fingerprints of the frozen report and the machine-readable results. The anchor cannot be edited or removed, so the published record can always be checked against it.

The scenarios run against a separate copy of the same code that serves this site, with accounts created for the evaluation — never against live data. The ledger records real events only, so what is anchored is the outcome and the fingerprints, never scenario data. Frozen copies of each report and its results are kept with the evaluation record; any copy presented later can be checked against the anchored fingerprint before it is trusted.

Evaluations (0)

No evaluation has been anchored yet. When one is, it will appear here with its fingerprints, and the ledger entry behind it cannot be edited or removed.

Verify an anchored evaluation

Three independent checks, all public:

• Read the entry. GET /v1/ledger/entries/{seq} returns the anchored payload — counts, scores and both fingerprints — with a Merkle inclusion proof against its signed block.
• Verify the chain. GET /v1/ledger/verify recomputes every block from the first one: hashes, links and the issuer's signatures (the keys are published at /.well-known/jwks.json). If any anchored entry had been altered, verification would fail.
• Hash the artifacts. Run SHA-256 over the frozen report and the frozen results and compare with report_sha256 and results_sha256 in the entry. A match proves the artifacts are exactly the ones that were anchored; any later edit breaks it.