Michael Darius Eastwood · Independent AI alignment researcher
Published
The 8 December 2024 evidence artefact is an .eml file. Its scientific value rests on parts of the header that most people never look at. This is a plain guide to what to open, what each field proves, and where the evidence stops being decisive.
Every message that Gmail accepts is assigned an identifier that looks like a compact hash with a domain suffix, for example [Message-ID redacted]. This string is generated by Google when the message is processed and is unique across their infrastructure. A stranger inspecting the .eml can read this ID directly and, in a dispute with Google as arbiter, use it to distinguish the exact message under discussion from any other. It is not, in itself, a public verification: Google would need to confirm the ID resolves in their stores. What it is is a stable handle, unforgeable outside a compromise of Gmail's own systems, that the file carries with it forever.
Below the Message-ID sits a sequence of Received: lines describing the servers the message passed through and the timestamps at each hop. On a self-sent message these are Google's own servers, and the sequence shows the message being handed from the composing server to the delivery server within a fraction of a second, all inside Gmail's infrastructure. This is what the phrasing Google-server-timestamped refers to: not a signature the reader can independently verify without Google, but a machine-generated log that Google would have to falsify retroactively to change.
The DKIM signature is applied to the outgoing message by the sending domain. For Gmail-to-Gmail traffic, it is Google signing on behalf of the sender domain, and Google verifying the signature on receipt. The signature is stored in Gmail's copy of the message and is visible via Gmail's Show Original view. The .eml export format does not preserve the DKIM-Signature header line, however, which is why the evidence page's exact phrasing is Google-server-timestamped via Gmail Message-ID; DKIM verified in transit. That is not a claim of DKIM verification against the downloadable file itself. The signature is a mechanism operating inside Gmail, not a property the exported file carries with it. The precision matters, and the truth gate blocks any looser wording.
It cannot verify the manuscript's content against any external claim. It cannot survive Google's server logs being compromised in a way undetectable to the reader. It cannot prove originality of the ideas. What it can do is give a stranger a machine-verifiable claim about existence: this file, unchanged from its published SHA-256, was processed by Google's mail infrastructure at this specific minute, with this specific ID, on this specific date. That is a smaller claim than authorship priority. It is a firmer claim than most priority disputes ever reach.
From the book Infinite Architects: Intelligence, Recursion, and the Creation of Everything by Michael Darius Eastwood.