Product / Delivery
Proof your work happened the way you say it did.
A delivery is more than a file transfer. Pin the final deliverable, choose what each audience gets to see, and ship with a signed certificate and a public verify link - the record frozen at the moment it mattered.
Deliver with proofOne record, three disclosures.
What does an Archibal delivery include? Every delivery ships the final file with signed C2PA Content Credentials embedded, a delivery certificate documenting the models and evidence behind the work, and a public verification link anyone can check.
The record is always captured in full. Presets are views for audiences - never forks of the truth - and a redacted view says on its face that it is redacted.
The default for handing work over. Business context, models and routes, the pinned final deliverable, and a provider-terms summary. No prompts, no workflow internals, no working takes - the creative recipe stays yours.
For public shares. The AI-made marker, model names, and the verify link survive - business and personal metadata are stripped, and container metadata is scrubbed from the exported file.
Everything, for your own retention or a regulator: prompts, workflows, references, per-model usage-terms detail with its review state printed, the full record.
Signed Content Credentials
The final deliverable is signed with a C2PA manifest at delivery - provenance embedded in the file itself, readable by any C2PA validator.
The delivery certificate
A PDF record of the delivery: what shipped, which models made it, how each claim was evidenced, lineage, and the usage terms on record at that moment - all frozen as of delivery.
The public verify link
A shareable page anyone can open to check the record - client, platform, or regulator. A QR on the certificate points to the same place.
The frozen snapshot
Delivery freezes the record. Later edits to your project, the model catalog, or the rules never rewrite what a past certificate said - corrections are new deliveries, visible as such.
Context worth knowing: the EU AI Act's transparency obligations (Article 50) apply from August 2, 2026. They bind AI model providers and the organizations that publish AI content - and in practice they push everyone in between to demand provenance. A delivery record is that provenance, ready when the question arrives. Details at the compliance hub.
Frequently asked
What exactly does a client receive?
The final file with signed C2PA Content Credentials embedded, a delivery certificate (PDF), and a public verification link. Under the client disclosure preset they see business context, the models used, and the final deliverable - never your prompts or workflow internals.
What happens if I need to change something after delivering?
Withdraw the project back to draft, make your changes, and deliver again - the new delivery supersedes the old certificate, and the old verify link points forward to it. The original frozen record is never rewritten; mistakes are corrected by new deliveries or an explicit revocation.
Are the compliance checks a gate on delivery?
No - by design. Checks against your declared markets and channels are advisory: they inform your decision and never block a delivery. The only gates are your own: confirming model routes you were asked to assent to, and an optional lawyer sign-off if you enable that workflow.