diff --git a/docs/docs.json b/docs/docs.json
index 423efad6..9ca16b9c 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -192,7 +192,6 @@
               "rfds/custom-llm-endpoint",
               "rfds/model-config-category",
               "rfds/plan-operations",
-              "rfds/message-id",
               {
                 "group": "v2 Draft",
                 "expanded": true,
@@ -212,7 +211,8 @@
             "pages": [
               "rfds/rust-sdk-v1",
               "rfds/session-delete",
-              "rfds/session-usage"
+              "rfds/session-usage",
+              "rfds/message-id"
             ]
           },
           {
diff --git a/docs/rfds/message-id.mdx b/docs/rfds/message-id.mdx
index 24424657..a8ec5950 100644
--- a/docs/rfds/message-id.mdx
+++ b/docs/rfds/message-id.mdx
@@ -282,6 +282,7 @@ Future RFDs may propose extending `messageId` to other update types if use cases
 
 ## Revision history
 
+- **2026-06-03**: Moved the v1 portion of the RFD to Preview while v2-specific behavior remains part of the v2 draft work
 - **2026-06-03**: Moved the RFD out of the v2 Draft group while keeping v2-specific behavior; added a dedicated `MessageId` type, and made v2 require message IDs on streamed message chunks while v1 keeps optional message IDs for compatibility
 - **2026-06-02**: Updated the proposal so message IDs are Agent-generated only, removed client-provided prompt IDs and prompt response acknowledgments, and removed the UUID requirement in favor of opaque strings
 - **2026-02-17**: Added "Message ID Acknowledgment" section to clarify that presence/absence of `userMessageId` in response indicates whether the Agent recorded the ID; clarified that UUID format is MUST (not SHOULD) since both sides generate IDs; renamed response field to `userMessageId` for clarity (request keeps `messageId`)
diff --git a/docs/rfds/updates.mdx b/docs/rfds/updates.mdx
index 019ea42a..e4186675 100644
--- a/docs/rfds/updates.mdx
+++ b/docs/rfds/updates.mdx
@@ -6,6 +6,14 @@ rss: true
 
 This page tracks lifecycle changes for ACP Requests for Dialog. For broader ACP announcements, see [Updates](/updates).
 
+<Update label="June 3, 2026" tags={["Preview"]}>
+
+## Message ID RFD moves to Preview stage for v1
+
+The v1 portion of the RFD for adding message IDs to streamed message chunks has been moved to Preview stage. Please review the [RFD](/rfds/message-id) for more information on the current proposal and provide feedback before the v1 behavior is stabilized.
+
+</Update>
+
 <Update label="June 3, 2026" tags={["Preview"]}>
 ## Session Usage RFD moves to Preview stage