Show your work. Not your prompts.
A receipt on every deliverable: what changed, which tool touched it, and who signed off.
- None
- Declared
- Verified
- Human reviewed
- Project summary
What it does not keep. Also the point.
- Your promptsWhat you typed is yours. The receipt records that a tool ran, not what you asked it.
- Your filesHashes, not contents. The record proves a match without carrying the work.
- A scoreThere is no percentage of AI. A file either has a verified chain or it does not.
The receipt. Hashes, not contents.
Enough to prove a match and name who signed. Clients see it next to the version.
{
"badgeLevel": "human-reviewed",
"inputHash": "sha256:9f2c…41ab",
"outputHash": "sha256:e07d…c90e",
"toolName": "generative-fill",
"modelVersion": "2026-08",
"reviewerId": "5b1e…a7d2",
"validatedAt": "2026-09-02T16:20:11Z"
}
- ProofBeside the version the client is reviewing.
- Project summaryEvery deliverable, rolled up.
- Delivery packetShipped with the final files.
- SignalOn your phone, before you approve.
The rest of the job. Same app, same file.
- CollaborationThe same file at the same time, and the comment becomes the task.
- ProofSend a version, collect notes on the art, get a decision in writing.
- Brand KitsColors, type, and logos every file reads from.
- InvoicingQuote the job and bill the work that got approved.
- Varial MCPReal project context for your AI tools. Read only.
Good questions. Short answers.
Do I have to use this?
No. A file with nothing to declare sits at None and nothing shows.
Does it store my prompts?
No. It records that a tool ran, which one, and what the result hashed to.
Can I fake a badge?
You can declare anything. Declared is your word. Verified and above come from instrumentation, which is the difference.
What does the client see?
A badge next to the version, and the receipt if they open it.
Does this cost extra?
No. Provenance is in every plan.