Provenance Disclosure
Provenance Disclosure generates a structured document that records what the issuer is willing to state about how a work was created, what role automation played, and who approved the final result.
The service does not determine truth or verify the underlying facts. It turns declared information into a durable issued record with stable language and stable document structure.
1. Draft
Enter the statements, systems, references, and limitations that apply to the work. Leave anything out that you cannot honestly support.
2. Review
Review the assembled document in its final layout and confirm that the language says exactly what you intend to stand behind.
3. Issue
Issuance creates an immutable record with issuance metadata. If anything needs to change later, the correct remedy is a new disclosure.
4. Use
Share or archive the issued PDF as a point-in-time declaration. It is meant to be reviewed as a declared record, not as certification, verification, or legal advice.
How to use these docs
This documentation explains how the disclosure works, how each part of the document should be understood, and what happens during drafting, review, issuance, and reprints.
Use the sidebar by question:
- Orientation explains what the document is for and where its limits are.
- Framework explains the meaning of the main field groups in the disclosure.
- Structure explains how information is organized in the issued record.
- Lifecycle explains what changes at draft, review, issuance, and reprint time.
- Policies explains how the service handles data, retention, and positioning.
Start here
If you are deciding whether this document fits your use case, start with What this is and is not.
If you are preparing to issue a disclosure, review Claims, Issuance, and Reprints and versions.
If you want to see the final artifact first, open the example disclosure PDF.