[rappdw]

Prose-only corrections from the pre-submission review; no schema or fixture
changes, and the gates are unchanged (121 fixtures, 114 signed cases, 10 MIME
cases).

Factual errors:

• Binding Record: contract_version is optional there and on the Peer
  Directory, not "the one artifact where it is".
• Peer tree write rule: the permitted inbound/ write is for the delivery
  failure notice, not "as demotion requires".
• Outcomes table: add the "drop: both fields" row that check 1 and the
  Control Notice section already define.
• Pattern guard: eight schemas carry it, not three.
• History, 3.0.0 entry: two cites to Versioning now point at the appendix
  subsection that holds the reasoning.
• History, 3.1.0 entry: a Correction for the fixture breakdown that does
  not sum.

Consistency and leftover language: Runtime is "host-side", not
"(container)"; the dated MCP/A2A revision sentences and the "re-verify"
note are gone; inbound/ is the one tree the core defines; draft.to is
stated REQUIRED; the undecidable relayed-vs-authored MUST is dropped; the
roster is written for the fleet, not "once"; the Message-ID domain is the
sender's; the reverse-message rule names both ends; "binding check" is
"checks 1 to 11"; the delivery failure notice has one strength (SHOULD);
from is a sender claim only on the mail tree; the audit log covers every
candidate; the Inbound Message is in the REQUIRED list; Lane is defined;
Appendix I drops repository talk; Appendix J's prefix map has directory-
and roster-; the 3.1.0 entry says its "proposed" items were adopted; the
"non-authoritative rendering" note is past tense.

IANA: change controller is IETF, the stream the owner confirmed
2026-10-21 (draft/README.md, "Counsel gates").

Coverage: seven reworded sentences re-keyed; two baseline entries got
classes (113 unclassified remain); the new SHOULD is classed operational.

🤖 Generated with Claude Code