Documents
The protocol, the profile, the product
FileOnChain is deliberately layered: a neutral evidence protocol anyone can implement, an opinionated application profile for AI-agent evidence, and a hosted product that makes running it convenient. Each layer has its own document — this page maps them.
One principle, three layers
The protocol is neutral. The application profile is opinionated. The hosted product is convenient. Nothing in the outer layers is required to verify what the inner layers produce.
The protocol is neutral
The FileOnChain Evidence Protocol defines the envelope — subject, claims, signatures, receipts — and nothing about how you must use it. Anyone can implement it without FileOnChain's packages or services.
The application profile is opinionated
The Agent Evidence Profile decides what agent evidence must contain — run and agent identifiers, digest-based model metadata, tool calls, approvals, policies — and how it validates.
The hosted product is convenient
FileOnChain Cloud handles keys, credits, anchoring workers, and retention so your agents don't have to. It is never required: every envelope it produces verifies locally, without an account.
The documents
Canonical markdown in the repository — versioned, reviewable, and independent of this site.
Evidence Protocol — normative spec
ProtocolThe envelope format, canonical encoding, artifact and envelope signatures, receipt adapters, and profile registration — the document an independent implementation follows.
GitHub ↗
Agent Evidence Profile v1
ProfileThe org.fileonchain.agent claims — required run and agent identifiers, model digests, tool calls, approvals, policy, trace references — and their validation rules.
GitHub ↗
FileOnChain Cloud — product overview
ProductWhat the hosted product does on top of the protocol: managed anchoring with credits, API keys, and the honest split between what is available and what is planned.
GitHub ↗
Integration status ledger
StatusThe source-of-truth status ladder for every storage and settlement system — mirrored live by the in-app integrations page.
GitHub ↗
Architecture decision records
ADRsWhy the design is the way it is — the separation into protocol, profile, and product, and the decisions behind each layer, recorded as they were made.
GitHub ↗