docs: record that draft-rapp-ammp-00 was posted

CLAUDE.md

@@ -38,18 +38,19 @@ language** — README's "What AMAP is not" says this normatively; keep it true.
 - **Approved to publish is not the same as submitted.** The counsel gates are
   CLEAR: `ipr="trust200902"` (settled 2026-09-21, the full BCP 78 grant),
   `submissionType="IETF"` and `category="std"` (the editor's values,
-  owner-confirmed 2026-10-21), and an email for each author. The draft is
-  **ready for submission**; the editor is submitting the -00 (`draft/README.md`,
-  "Counsel gates"). Any future change to those values, to the author list, or to a
+  owner-confirmed 2026-10-21), and an email for each author. The editor
+  **posted `draft-rapp-ammp-00` on 2026-10-22**: an active individual
+  Internet-Draft, no stream yet (`draft/README.md`, "Counsel gates"). Any future change to those values, to the author list, or to a
   BCP 79 disclosure is a rights statement, not an editorial choice: do not
   make one on your own initiative. The history is in `draft/README.md` under
   "Counsel gates". Note the draft ASSERTS it is submitted under BCP 78/79,
-  because a real `ipr` value generates that boilerplate. Nothing has been
-  submitted anywhere, and submitting is the owner's decision, not an editorial
-  one.
+  because a real `ipr` value generates that boilerplate; that became true when
+  the -00 was posted. Each later revision is submitted by the editor on the
+  owner's decision, never as an editorial step. It is an individual draft:
+  never call it adopted or an IETF standard.
 - Keep shipped text free of absolute host paths and personal identifiers.
 
-## Version state (as of the -00 handed to the editor for submission, 2026-10-21)
+## Version state (as of the -00, posted 2026-10-22)
 
 | | |
 |---|---|

README.md

@@ -17,7 +17,8 @@ people and versioned independently.
 **Current revision: `draft-rapp-ammp-00`**, which corresponds to contract
 3.1.0 (wire `contract_version` `"2"` - the contract's own SemVer and the wire
 major track different things as of 3.0.0; see the draft's Versioning and
-Conformance section). The draft has not been submitted.
+Conformance section). The -00 was posted on 2026-10-22 as an individual
+Internet-Draft: <https://datatracker.ietf.org/doc/draft-rapp-ammp/>.
 Conformance gate: **121 fixtures**, 0 unexpected, plus the signed peer cases in `fixtures/peer-signed/`.
 
 ## Motivation

draft/README.md

@@ -131,6 +131,11 @@ no longer needed.
 router, and the Claude Code connector, plus taking AMAP to the IETF. Other
 Proofpoint products are explicitly out of scope and remain unpublished.
 
+**Posted, 2026-10-22: `draft-rapp-ammp-00` is an active individual
+Internet-Draft** (<https://datatracker.ietf.org/doc/draft-rapp-ammp/>), with
+no stream assigned yet. The paragraphs below are the history up to that
+point.
+
 **Status, 2026-09-24: the operator confirmed that counsel's gates are clear.**
 The front matter carries `ipr="trust200902"` and `submissionType="independent"`,
 and both authors' email addresses. The draft is ready for submission and **has
@@ -142,7 +147,7 @@ editor's review (2026-10-02) had set those two values (Intended status:
 Standards Track) in place of `independent` and `info`; the IETF stream is the
 one that leads to Dispatch, a BoF and a working group, which is the path the
 editor proposes. The owner confirmed both values on 2026-10-21, in session, and
-the editor is submitting the -00 on that basis. The IANA change controller in
+the editor submitted the -00 on that basis. The IANA change controller in
 the draft reads `IETF` accordingly. They remain rights statements: any later
 change is the owner's, not an editorial choice.
 
@@ -195,6 +200,7 @@ with our hand-written note of the same name, which had to be renamed to
 `note_About_This_Draft`. **The document now asserts it is an Internet-Draft
 submitted under BCP 78/79. Nothing has been submitted anywhere.** That gap
 closes when it is filed, and not before.
+**Update, 2026-10-22:** the gap is closed. The -00 was posted that day.
 
 ### The second author's email — settled