ABSuiteAI Black Box Recorder
Recording
Prove what your AI actually did
Record what happened. Prove it happened. Preserve the evidence.
Every action is Ed25519-signed and hash-chained, so anyone can check the record — including people with no reason to trust you. Payloads are hashed, never stored.
No install. No account. No server. The page loads a real signed trace, verifies it with WebCrypto, then lets you tamper with it and watch verification fail.
npm install @absuitecore/capkit npm install @absuitecore/trust
[ Questions it answers ]
What happenedA signed, hash-chained trace of every real action.
Who did itThe subject of the capability token that authorised it.
Was it allowedScope checked before execution, not after.
What backs itClaims checked against sources: supported, unverified or contradicted.
Was it alteredChain verification names the first broken record.
Can you re-run itReplay compares a re-run against recorded hashes.
[ A hash chain is not a signature ]
Hash-chaining proves a record was not edited afterwards. It does not prove who wrote it — the operator being audited can build a valid chain containing anything. Ed25519 closes that: verification needs only the public key, and a public key cannot sign.
[ Read next ]
- Getting started — library, HTTP API and Docker
- API reference — every route, generated from source
- OpenAPI spec — import it into your client
- Architecture — how the pieces fit together
- Principles — what this project refuses to build
- Security model — threat model and defence in depth
- Packages on npm — all seven, with provenance