Vellumproof

Authorship record

Understudy

by Dylan Reed · started 2026-07-04

Verdict

The seal is cryptographic: every version is signed when it's made, and any tampering with the record breaks it visibly.

Timeline intact — 11 sealed versions, chain and signature verified.

content, chain, and seal freshly verified for every version · download the signed record to verify independently

Cadence — total words over time

Cadence is your writing rhythm made visible — when the words came, straight from your sealed versions.

#When (UTC)WordsΔSeal
12026-07-06 22:32878+8783e63ec57e334
22026-07-07 13:501,004+126a8efcbde7954
32026-07-07 14:191,239+235d0541ef7adeb
42026-07-07 18:592,077+838483390eeb8cb
52026-07-08 22:273,034+95736984c5f83a4
62026-07-09 15:203,037+31b107840af52
72026-07-14 18:003,307+27022da8396582b
82026-07-14 18:123,624+3174a0114be9cee
92026-07-15 22:173,994+370f0a2b59e194a
102026-07-19 14:445,075+1,081c49b2194c922
112026-07-21 19:276,084+1,0092c5aa2240984

Files & provenance

Everything here is timestamped by our servers and tamper-evident. A 'sealed' file is a snapshot we can prove nobody quietly changed or backdated — good evidence you did the work, though not proof a human typed every word instead of pasting in AI text a little at a time. An 'observed' file was written right here in the editor, so we watched it grow keystroke by keystroke — that catches wholesale paste-ins and is much harder to fake, but someone truly determined could still feed us fake typing in real time. Our strongest evidence of real, live authorship — not an ironclad guarantee.

Process evidence

What the record shows about how this manuscript was written — evidence, never a verdict. Every line is labeled with how much weight it can carry.

What the labels mean

sealedCryptographically signed and tamper-evident — version history, timestamps, content hashes.
observedRecorded live by the editor — typing cadence, sessions, paste events — shown as evidence, not verdicts.
not provenWhat the record can't establish, stated plainly. Honesty is what makes the rest believable.

What this does not prove

not provenWhich human sat at the keyboard — a record of the writing can't rule out a ghostwriter.
not provenThat no AI was consulted outside the editor. Retyping generated text is possible; the record shows the shape of the writing, but draws no conclusion.
not provenAnything about work that happened off the record — imported text is labeled as arriving in bulk, nothing more.

Replay

The author chose to share this — watch the draft take shape, keystroke-batch by keystroke-batch, exactly as the server recorded it.

Loading the replay…

Loading the replay…

Loading the replay…

Loading the replay…

Loading the replay…

Loading the replay…

What this record proves

Every version above is sealed the moment it's saved and fully re-verified — content, chain, and seal — on every visit to this page. That catches edits to the manuscript's text or structure, backdated or reordered timestamps, doctored word totals, a forged or transplanted seal, and a truncated (deleted) tail of the timeline.

It cannot prove a human — rather than a patient drip-feed of AI text — wrote these words. And it has one honest blind spot: an attacker with direct database access who wipes every version and this project's signed anchor leaves behind a vault indistinguishable from one that was never used — and an attacker who captured an earlier signed anchor can roll the vault back to that earlier state undetected, verifying clean as a shorter, older timeline. Download the signed record and keep your own copy: it becomes an independent anchor of what existed when you downloaded it, outside our database, that later tampering here can't rewrite.

Commit messages and per-file labels are plain display fields — not covered by any of the sealed layers.