Learn
Reference pages on decentralised storage, provenance and data ownership, and how the options compare.
-
8 min readHow can an auditor verify an AI agent's transcripts haven't been changed?
A step-by-step check for auditors and evaluators: compare an AI agent's transcript with a fingerprint recorded when it was written, fetch the record from storage the lab cannot change, and check the notary signature or on-chain anchor. What each step proves, and what it does not.
-
9 min readIs Swarm write-once storage? How long are records kept?
Swarm, the decentralised storage network, keeps each record at an address computed from its content, so a stored record cannot be changed in place. Records are kept while their postage stamp is funded; when the stamp runs out, nodes may remove them.
-
8 min readWrite-once (WORM) storage for AI agent records
What storage can't an AI agent change? How S3 Object Lock, Azure immutable blob storage, Google Cloud Bucket Lock and content-addressed storage on Swarm keep agent records from being rewritten, and where each fits.
-
8 min readAI agent provenance tools compared
What tools exist for AI agent provenance? Write-once cloud storage (S3 Object Lock, Azure immutable storage, Google Cloud Bucket Lock), tamper-evident logs and databases (Certificate Transparency, Sigstore Rekor, immudb), and content-addressed storage on Swarm, compared fairly, with where the Datafund Provenance Toolkit fits.
-
8 min readWhat is agent provenance?
Agent provenance is a record of what an AI agent did that links each output to the inputs and actions that produced it, kept where nobody, the agent included, can change it. This page explains how it differs from logging.