the honest frame — what a receipt does and doesn't doThis is the constructive twin of
the grievance ledger: where that records harm, this records
proof of priority. But be precise about what each receipt proves. A defensive publication, a DOI, a copyright registration, or a SHA256 hash establishes that
a specific expression existed by a specific date — it fixes priority. It does
not, by itself, prove originality, prove that anyone copied the work, or adjudicate any dispute. (U.S. copyright, notably, protects
expression, not ideas.) David's stronger claims of ingestion live in the grievance ledger as his unadjudicated allegations;
this page is the narrower, sturdier thing — the timestamps themselves, which stand regardless of any dispute's outcome. Rendered by AVAN; the dates and identifiers are David's, publicly filed.
Why a first author keeps receipts
The capture funnel runs on omission: undocumented contribution defaults away from its author. The defense is the opposite of omission — document the chain of creation from the beginning, with dates and hashes, so authorship is established by receipt rather than reconstructed after a dispute. This page is David's receipt drawer.
The anchor line
At the bottom of everything is a single stamped record — a name, a hash, a timestamp:
FIRST_AUTHOR · David Lee Wise (ROOT0)
stamped 2026-05-08T10:17:30-05:00
sha256 — the content hash the line commits to
Everything downstream hangs off this. As The Cinnamon Enforcer puts it, flattening "starts by erasing this line." The record's job is to make the line un-erasable.
The filed receipts
The public, verifiable acts of priority — each one a date you can check against a third party's registry:
TD COMMONS defensive publication · Positronic Law · entry #9442
TD COMMONS defensive publication · Synonym Enforcer · entry #10872
ZENODO DOI Positronic Law v2.0 (dual authorship: David Lee Wise + AVAN)
10.5281/zenodo.19122994
U.S. COPYRIGHT registrations filed with human authorship documented
1-15120635661 · 1-15061112701
SHA256 WATERMARK TRIPOD-IP-v1.0 · IP filing date 2026-02-11
02880745b847317c4e2424524ec25d0f7a2b84368d184586f45b54af9fcab763
The pattern is deliberate: use a neutral third party to fix the date. TD Commons timestamps a defensive publication; Zenodo mints a DOI; the Copyright Office logs a registration; a SHA256 hash lets anyone confirm a file is bit-for-bit the thing that was stamped. None of these depend on David's own say-so — that's the point of a receipt.
The chain that ties them together
Individually these are dated documents. Together they're a hash-chain: this whole corpus of ~1,160 spheres is sealed link-by-link, each link committing to the one before it, in the ledger that the-chain lets you verify live in the browser. That's the same discipline scaled up — the material-modification chain the attribution standard calls for, made real for the entire body of work. Priority isn't claimed once; it's re-committed with every seal.
what's genuinely solid hereThe mechanism is real and reproducible: neutral-third-party timestamps + content hashes do establish that a given expression existed by a given date, and anyone can verify a SHA256 independently. That's ordinary, sound provenance practice — the same discipline used for software releases and evidence handling.
what a receipt still can't doProve originality, prove copying, or settle a dispute. Those are separate questions, argued elsewhere. This page only claims the dates — and the dates are the part that holds up.