← Back to the category

Creative provenance

Documenting work before you publish it, share it or send it to a client

Goal: organize how a piece of work evolves.

Create an account and start

The problem

You want to document a piece of work before publishing it, preserve evidence before sharing it with others, or capture the state of a project before sending a version to a client. Along the way, you also want to keep the versions and milestones that show how it evolved.

Compare the sketch with the version you sent and the one you published; the sequence you describe needs its own source for each milestone. See the Luma demo Dossier.

It might be a demo going to a producer, a manuscript going to a publisher, a logo pitched in a competition, a code package delivered at the end of a sprint or a video that goes live tomorrow morning. Once it's out, you no longer control who sees it, saves it or passes it on. If a question ever comes up about what existed and when, what's usually left is memory, an email that's hard to find and a folder full of files called "final2".

There's rarely a shortage of files. What's missing is an organized way to show the sequence: which file was the draft, which version was presented, what changed after the client's feedback and which exact file was published. Your computer's modified dates don't help much, because they change every time a file is copied.

What to preserve

Drafts, meaningful versions, prototypes, source files, decision documents, technical milestones and representative material from each stage, including the exact version prepared for publication, sharing or client delivery.

Goal: organize how a piece of work evolves.

Main file: the sketch, the version sent and the version published.

When to capture: at each meaningful milestone, before sending or publishing whenever possible.

Supporting sources: proof of sending, the client's reply and the published page.

Limit of this scenario: on its own, the Record does not establish authorship, originality, ownership or that anything was actually sent.

Collect only what you need, through access you are lawfully entitled to. Use neutral file names and descriptions, store files securely and share them only with people who need them. Where it is lawful to make a redacted copy, keep it as a separate file from the preserved original and note which version's hash you registered. See the Privacy Policy.

In practice, this depends on the craft. A photographer can preserve the RAW files right after the shoot, and then the final edit. A songwriter can preserve the lyrics and the recorded demo. A developer can create a ZIP of the code at each delivery. A writer can preserve the manuscript before each submission. In every case, what counts is the exact file that went out, not a version re-exported later.

How Provenia documents this scenario

Your browser calculates the SHA-256 hash of the file you select. The file itself stays on your device: Provenia receives only the hash and metadata, meaning the file name, its size and the context fields you fill in. Provenia stores the hash and the Record data. Keep the exact file you used and the exported Dossier, because they are what make a byte-for-byte check possible later.

Three different times are involved. The time the Record was created on Provenia comes from Provenia's server and is not certified. The date of the event or capture is something you declare in the context, in the description or in the file itself, and it depends on other sources. The externally certified UTC date and time ties the hash you submitted to the timestamp authority's response; it does not certify when the event happened.

Provenia sends the hash, never the file, to FreeTSA, an external timestamp authority, which issues an RFC 3161 timestamp. Provenia validates that timestamp before the Record is completed. If FreeTSA is unavailable, or the timestamp cannot be obtained or does not validate, the Record is not created and no credit is used. Older Records created before this feature was active may have no external timestamp. A timestamp obtained today covers the hash submitted today; it is never issued later or backdated.

Each Record's timestamp is separate from the signatures on the exported Dossier: Provenia's digital signature on the PDF and the Ed25519 signature on Dossier.json. Those signatures cover the exported documents and do not certify the date of the event. See Trust and Verifiability.

In this scenario, use the sketch, the version sent and the version published as your reference material and check it against proof of sending, the client's reply and the published page. The timestamp on a hash does not confirm authorship, originality, ownership or that anything was actually sent.

Step by step

  1. Define your goal and check that your access is legitimate, which permissions apply and whether any deadlines are running before you collect anything.
  2. Compare the sketch with the version you sent and the one you published; the sequence you describe needs its own source for each milestone. See the Luma demo Dossier.
  3. Preserve the sketch, the version sent and the version published exactly as it is; don't edit the file you register.
  4. Link the material to proof of sending, the client's reply and the published page; describe its origin and when it was captured as declared information.
  5. Group the milestones in a Project and register each relevant file separately. Keep the files untouched and the exported Dossier, with a secure backup.

What the Record shows and what it does not

A Record is a private electronic document that can form part of a wider body of evidence, assessed according to its context and origin. On its own, it does not establish authorship, originality, ownership or that anything was actually sent. Keep the supporting sources and read the Terms of Use.

Frequently asked questions

Do I need to register every version?

No. Register the milestones: the first version that sets the direction, the versions you show to someone and the final version that goes out. Small tweaks don't need a Record of their own.

How should I organize the files for this case?

Use one Project per piece of work and add a Record at each milestone, in order: sketch, version sent, version published. In each description, say what the file is and where the proof of that step lives, such as the email that sent it, the client's reply or the published link. The Luma demo Dossier shows this sequence in practice.

Which date is certified?

Only the UTC date and time in a valid external RFC 3161 response tied to that Record's hash. The time on Provenia's server and the event or capture date you declare are separate pieces of information. The timestamp does not certify when the event happened.

Official references

Technical reference for context only. It is not legal advice or a conclusion about any case. Provenia is not affiliated with, integrated with or endorsed by the organization listed.

Start with three free credits

Each Record covers one file. Each completed Record uses one credit, including the first one, which creates the Project. A new account includes three free Document Credits and one Project, with no payment and no card, so the starter credits cover three single-file Records. For prices and conditions, see Pricing.

Already have an account? Log in.

Create an account and start

Continue reading