What Proof Looks Like for Writers
A realistic walkthrough of what happens when a writer seals a draft before sharing it.
Tap to Watch the Walkthrough
Seal ID
Issued
Status
Protected
Record
Verifiable
The Scenario
A freelance writer — call her Maya — has spent three months researching and drafting a long-form feature article. She is fifteen minutes from emailing the final draft to her editor. Before she sends it, she wants a documented record that this exact version existed at this exact moment.
This is not about distrust. It is about having evidence that does not depend on her memory or her word alone. She has been in a situation before where she had no clean proof trail, and she knows what that feels like when proof is exactly what you need.
So she seals the file first.
The File Being Sealed
- File: feature-draft-v3-final.docx
- Size: 487 KB
- Type: Long-form feature article, approximately 6,800 words
- Version: Third major revision — the version she considers ready for editorial review
- Working title: "Infrastructure of Trust"
- Version label applied: v3-editorial-review
What Happens During Sealing
Maya drops the file into CREATORSEAL™. The entire process takes less than sixty seconds.
- Local fingerprinting. CREATORSEAL™ computes a SHA-384 cryptographic hash of the file contents entirely within her browser. The original file never leaves her device.
- RFC 3161 timestamp. The fingerprint is submitted to an independent Time Stamping Authority, which records the exact UTC time and issues a signed timestamp token. The time is set by the authority — it cannot be supplied or adjusted by Maya.
- Two artifacts produced. CREATORSEAL™ generates a Receipt of Provenance Record — a human-readable summary containing the fingerprint, Seal ID, timestamp, and name on record — and an Evidence Bundle, the machine-verifiable cryptographic proof material that any third party can independently check.
Neither artifact contains the original file. Only the fingerprint traveled. The article remained on her laptop throughout.
What She Has After Sealing
- Seal ID: A unique identifier tied to this specific file and seal event.
- SHA-384 fingerprint: A cryptographic hash of the file's exact contents at the moment of sealing.
- RFC 3161 timestamp: A signed timestamp from a trusted authority recording the exact UTC time.
- Receipt of Provenance Record: A human-readable summary she can reference, share with a lawyer, or file — without disclosing the article itself.
- Evidence Bundle: Machine-verifiable cryptographic proof material available for independent checking by any third party.
- Version metadata: Version label (v3-editorial-review), project name, and optional notes attached to the record.
If Maya also seals her earlier drafts, she builds a documented proof chain — a verifiable creative timeline showing how the article evolved from first draft through final revision. That kind of continuity is difficult to fabricate and straightforward to verify.
What Can Be Independently Verified
Because the Evidence Bundle contains all the cryptographic proof material, anyone — including parties who were not involved in the original sealing — can independently verify the following:
- File integrity: Does the file Maya holds today produce the same SHA-384 fingerprint that was sealed? If yes, the file has not changed since sealing.
- Timestamp authenticity: Was the RFC 3161 timestamp issued by a legitimate Time Stamping Authority at the recorded time? This can be checked against the authority's public certificate chain.
- Seal consistency: Do the Seal ID, fingerprint, and timestamp all correspond to the same recorded seal event?
The verification does not require trusting Maya's account of events. It requires only the file and the Evidence Bundle.
What This Does Not Do
A CREATORSEAL™ proof record does not determine legal ownership, replace copyright registration, or substitute for legal advice. It creates a documented, verifiable record that a specific file existed in a specific form at a specific time. That record can support a creator's position in a dispute — but legal outcomes depend on many factors beyond any single piece of evidence.
Common Questions
Does CREATORSEAL™ upload my manuscript?
No. CREATORSEAL™ computes a SHA-384 fingerprint of your file locally in your browser. Only the fingerprint is submitted to the timestamp authority — your manuscript never leaves your device.
What exactly is the Receipt of Provenance Record?
The Receipt of Provenance Record is a human-readable summary of your seal: the file fingerprint, Seal ID, UTC timestamp, and name on record. It is the artifact you can share, print, or file without exposing the file itself.
Can the RFC 3161 timestamp be backdated?
No. RFC 3161 timestamps are issued by an independent Time Stamping Authority and cannot be altered retroactively. The UTC time recorded is when the fingerprint was received by the authority — not a time you supply.
Does a CREATORSEAL™ proof record prove I own the copyright?
No. A proof record documents that a specific file existed in a specific form at a specific time. It does not determine legal ownership or substitute for copyright registration. Legal outcomes depend on many factors beyond any single piece of evidence.
What if I send multiple drafts to different parties?
Seal each version before sending. Each seal produces a unique Seal ID, fingerprint, and timestamp. If you later need to establish which version went to whom and when, you have a documented record for each.
Understanding these distinctions is not about being paranoid — it is about making informed decisions before you share your work. The best time to build your proof trail is before anyone else has seen the file.
Verify or Learn More
Ready to protect your draft?
Seal the file before you share it. Build the proof trail now.