TallwrightDocs

Tallwright Cloud Proof

Cloud Proof records what your AI agent did as tamper-evident evidence that somebody else can check, while the content of what it did stays on your own machine.

Your code commits to each action where it happens. A salted address of the content goes to Tallwright; the content and the salt that opens the address stay with you. Tallwright seals the address into an append-only log, a witness countersigns the log's head, and for any record you can ask for an exhibit: one file that anyone can check offline with the public verifier, against the content you choose to disclose to them.

The path of one record

  1. Commit. The SDK draws a 32-byte salt, computes the address of the salt followed by the content, and keeps the pair in your evidence store before anything is sent.
  2. Send. The line goes to your Environment's ingest address: your name for the event, the address, and what kind of action it was. The door answers with a receipt, which is a confirmation and not a proof.
  3. Anchor. At the next anchor run the log's head is signed, and a witness countersigns it. From then on the record is covered.
  4. Exhibit. The backoffice, or an export key, gives you the exhibit of one record.
  5. Verify. evidence-verify checks the exhibit offline with the disclosure you kept, and anyone you give both to can do the same.

What Tallwright sees, and what it never does

Cloud Proof holds no content. The door receives the address, your name for the event, and the fields you choose to send in the clear (action_type, actor_authority, timestamp). It never receives the content, the salt, or the disclosure that opens the address, and it refuses a line that tries to send them. Everything that travels in the clear is sealed into every exhibit, so name events and rules in it, never people. The whole of it is in Cloud Proof over HTTP.

Where to start

  • Quickstart: from an Environment to an exhibit you have checked yourself, in Python.
  • tallwright-cloud: the Python SDK, which is the recorder. Use it rather than computing a salt or an address of your own.
  • Cloud Proof over HTTP: the same contract in plain HTTP, for a language without an SDK.
  • The exhibit format: what an exhibit proves, and how a verifier checks it.
  • Writing an adapter: the contract a framework adapter is held to.

What it does not prove

Every record is a statement your system made: this happened, and this is what it said. The seal shows that the statement has not changed since it reached the door, at that position, under a log head the witness countersigned. On Cloud, Tallwright runs both the door and the witness, and nothing here claims they are independent of each other. A record does not prove that the statement is true, and the log does not prove that your system recorded every action it took: an action nothing captured leaves no record to be missing. Integrity of what was captured, not completeness of what happened.