Skip to content

Home / Priority claims register / PC-001

Priority claim · PC-001

8 December 2024 self-emailed manuscript as earliest timestamped anchor

First date: Timeline

This was first published by Michael Darius Eastwood on . Anchored evidence is listed below. See the machine-readable priority record at /research/priority/ and the full ledger at /priority-claims.

The claim - verbatim

Michael Darius Eastwood first placed the embedded-correction alignment thesis under its specific named framing, an early U = I x R capability-scaling formulation, and the AI-control-failure passage on the public evidentiary record via a self-sent Gmail package 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, Message-ID CAGPsKAnp-DLDBOeBAh4t9XsqJBKdoe07uORGF86meoSMFnin7w, 221,236 words across five attachments (four text essays totalling 221,236 words (five attachments) plus the 31,881-word book draft v3.2), SHA-256 anchor prefix f0d1f38f. This is an existence-by-date anchor, not a cryptographic authorship claim.

Anchored evidence

Limits and citation guidance - what this claim does not support, and how to cite it

Limits. visible Gmail origination fields establishes existence-by-date, not DKIM-authenticated authorship. The manuscript identifies structural directions, not specific RL-training or experimental mechanisms. State which artefact is meant: the sent-side export preserves no authentication headers, while the recipient-form object carries sender-DKIM and Google ARC fields whose signature mathematics verify under the keys returned at the selectors on the audit date. When quoting Google's recorded verdict, quote the ARC-sealed ARC-Authentication-Results header, never the unsealed Authentication-Results. Existence-by-date only; not authorship; not an RFC 3161 timestamp.

Verify this claim. The machine-readable priority register is at /research/priority.json (this claim is PC-001 in claimsLedger[]). The full public ledger view is at /priority-claims. Where evidence points at a redacted evidence/... path, the public verification method is documented at /research/evidence-spine.html. Every result is independently checkable via the OSF programme at osf.io/6c5xb (DOI 10.17605/OSF.IO/6C5XB).

← Back to the priority claims register · public ledger view · machine-readable priority record · home.

reads aloud · highlights as it goes · jump to any section