Proving You Made It First

§ 01The Problem With "I Made This"

Anyone can claim authorship after the fact. The internet makes that claim cheap and easy — a screenshot, a repost, a redate, and suddenly someone else's work looks like theirs. What separates a credible claim from a contested one isn't intention or outrage; it's evidence. Specifically, it's evidence that existed before the dispute arose.

This is provenance: the documented history of a work's creation. In the art world, provenance establishes where a painting has been and who owned it. For a blog post, a photograph, a research paper, or a piece of software, the same logic applies. A chain of dated, verifiable records makes your claim of prior creation hard to challenge — and easy to believe.

§ 02What Actually Counts as Evidence

The most useful evidence is the kind you didn't manufacture for the purpose of proving something. That's why drafts matter so much. A folder of iterative saves — with filesystem timestamps showing version 1 at 9 a.m., version 5 at 3 p.m., version 12 the following week — tells a more convincing story than a single polished file with a creation date you could have edited in metadata.

Platform timestamps are similarly useful because they're not under your control. When you publish to a blogging platform, a social network, or a code repository, the server records the date and time independently. A public post timestamped on a given date is, in ordinary disputes, strong evidence you had the work by that date. Git commits in a hosted repository go further: each commit carries a cryptographic hash that makes retroactive tampering detectable, and the entire history is preserved in sequence.

Email is underrated. Sending yourself a draft, or sharing it with a collaborator or editor, creates a third-party record. The recipient's mail server logs the receipt time. An email chain showing you sent draft copy to a colleague on Tuesday, and received notes back on Thursday, is exactly the kind of mundane documentation that holds up.

Cloud storage services that maintain full revision history — many document editors do this automatically — can produce a timestamped log of every edit. If a dispute reaches a formal process, the ability to show sixty-three incremental saves over a month is considerably more persuasive than a single assertion.

What doesn't count for much: screenshots with visible dates, because dates are trivially editable; unverifiable "I posted this on my hard drive" claims; and, famously, the "poor man's copyright" — mailing yourself a sealed envelope. The postmark tells you when the envelope was mailed, not what's inside, and the seal's integrity is easy to question. It carries no legal weight in most jurisdictions, and the myth that it does has persisted far longer than it deserves. (copyright myths debunked deals with this and related misconceptions directly.)

The postmark tells you when the envelope was mailed, not what's inside, and the seal's integrity is easy to question.

§ 03Building the Trail Before You Need It

The most effective provenance strategy is one you implement as a matter of habit, not in response to a crisis. A few low-effort practices compound into a solid record over time.

Version everything. If you write in a document editor with autosave and revision history enabled, do nothing — the trail builds itself. If you work in plain files, name versions with dates (essay-2025-04-01.md) and don't overwrite old ones. A folder of dated files costs nothing and proves a lot.

Publish early, even partially. Posting a draft, a summary, or a teaser to a public platform on a given date stakes a claim in a way that a private file cannot. You're not obligated to show unfinished work, but even a locked or unlisted post with a server-side timestamp is more robust than an unpublished document.

Register where registration is available. In some jurisdictions, formal copyright registration strengthens your position significantly — not because it creates the copyright (which, in most countries, exists automatically from the moment a work is fixed), but because a formal registration record, timestamped by an official body, is almost impossible to dispute. The US Copyright Office, for instance, allows registration for a modest fee, and a timely registration can unlock statutory damages and legal fee recovery in infringement proceedings.

Archive your sources and process. If your work builds on research, interviews, or earlier sketches, keep that material. A photo of handwritten notes dated the week before you published shows the creative process in a way that a finished file alone cannot.

§ 04When It Actually Matters

Most creators never need any of this. Most work circulates without incident, is attributed correctly, and the question of priority never arises. But in the cases where it does — a licensing dispute, a plagiarism allegation, a claim of joint authorship, a rights transaction that requires you to prove you originated the work — the evidence you assembled quietly, in the ordinary course of making things, becomes essential.

The lesson is one of the oldest in documentation: the best time to build a paper trail is before you need it. Timestamps accumulate; disputes don't wait. A habit of saving versions and publishing to dateable platforms isn't paranoia — it's the kind of quiet record-keeping that lets you answer "prove it" with confidence.

APPENDIXAttached to the record

Filed as general information, not legal advice.