What did the 8 December 2024 manuscript establish?

The 8 December 2024 self-emailed manuscript by Michael Darius Eastwood placed several dated priority anchors on the public evidentiary record. The Gmail package was bearing a visible Gmail origination field of 02:45:18 UTC on 8 December 2024, with sender-DKIM and paired Google ARC mathematics verifying against keys captured at the signed selectors and no RFC 3161 trusted timestamp, carried Message-ID CAGPsKAnp-DLDBOeBAh4t9XsqJBKdoe07uORGF86meoSMFnin7w, comprised 221,236 words across five attachments (four manuscript drafts totalling 221,236 words (five attachments) and the 31,881-word book draft v3.2), and has SHA-256 anchor prefix f0d1f38f.

Four dated first-publication anchors follow from that manuscript. First, the embedded-correction alignment thesis under its specific named framing (verbatim at version-2 essay lines 20 and 40 and HRIH manuscript line 14001). Second, an early U = I x R capability-scaling formulation at line 9 of the version-2 essay. Third, the named 'ARC Principle - Artificial Recursive Creation' cross-domain framework. Fourth, a structural AI-control-failure passage ('AI systems cannot be truly controlled; they will evolve beyond any safeguards') at HRIH manuscript line 14005, recorded ten days before Anthropic's alignment-faking paper (Greenblatt et al., arXiv:2412.14093, 18 December 2024). A precursor description of the Eden Protocol governance framework and the Hyperspace Recursive Intelligence Hypothesis are also present.

The dated record establishes existence-by-date, not authorship: the visible Gmail origination field, sender-DKIM and paired Google ARC mathematics verify against the signed selector keys, and there is no RFC 3161 trusted timestamp. The manuscript identifies structural directions, not specific reinforcement-learning training or experimental mechanisms. Both 'Google-server-timestamped' and 'cryptographically timestamped by Google's servers' are withdrawn. The correct phrasing on every surface is: the sent-side bytes are public and hash-verifiable, and a supplied recipient-form export decodes to the same five attachment hashes, with sender-domain DKIM and paired Google ARC mathematics verifying against the keys returned at the signed selectors on 2 August 2026. That is provider-key evidence over a canonicalised signed scope, not an RFC 3161 trusted timestamp. Both of those gaps are now closed, and closing them added caveats of their own. Recipient-side copies have been acquired. They carry the delivery chain, a Google ARC-Seal at d=google.com, selector arc-20240605, with no expiry tag and the signing time inside the signed scope, and the sealed ARC-Authentication-Results recording dkim=pass and spf=pass at delivery. Both selectors still resolve in DNS, so the seal is checkable today. The ARC set bearing d=google.com has no inspected x= expiry and is the preferred provider-key route; the sender-domain DKIM, which does carry a seven-day expiry, is corroboration rather than the vehicle. Sender-signature expiry, historical key-state and live-account custody remain pending. Quote the sealed ARC-Authentication-Results, never the unsealed Authentication-Results, which a file can be edited to say anything. Priority for the alignment-faking experimental result and for the Willow first-below-threshold quantum-error-correction result (Nature, 9 December 2024) belongs to the respective independent teams; the temporal proximity is a convergent data point.