What this is. A second approach to the RFC, on the 27/08 outline: Motivation → Proposal → Discussion → Details → Chores → Open questions → Implementation → Affected Specifications, the shape of the five merged Mantle-side RFCs (four by the protocol lead, #375 by Frederico Teixeira). Bullets, not prose.
Citation rules (28/08). Harvard-style inline citations. Specifications by name and revision at the pinned commit (References); pull requests, EIPs and arXiv papers keep their numbers; internal research notes cited as such, paraphrased rather than quoted. Material from 1:1 feedback, review comments and transcripts is paraphrased, never quoted. Register codes, tier tags, bolding, em dashes and internal work history are removed; tier travels in the citation form. The register mapping is preserved at
archive/rfc_v2_draft_pre_citation_2026-08-28.md.Ground rules. Two variants throughout: the sovereign design is the subject and is specified; the native form is described per part under one stated premise. Corpus pinned at logos-lips
48fbc82(captured 2026-08-27). The Discussion is the weight-bearing section; the v1.1 Details are carried by reference where unchanged.
EXECUTE precompile, an enshrined universal state-transition verifier (draft; proof of concept 2026-03).