diff --git a/docs/rust-server-upgrade-takeover.md b/docs/rust-server-upgrade-takeover.md
index 3707a32d8..0533635dd 100644
--- a/docs/rust-server-upgrade-takeover.md
+++ b/docs/rust-server-upgrade-takeover.md
@@ -10,6 +10,17 @@ read, and their `backup_verified`, `php_quiescence_verified`,
 `stored_representation_compatibility_verified` and `takeover_allowed` flags are
 always false. This note says what makes each one true.
 
+## Deprecation
+
+Takeover ships in 3.0.0 so self-hosted installations can upgrade a PHP Server
+database (layouts 2.5.14 through 2.11.8) in place. It gets no further
+investment beyond what 3.0.0 ships and is planned for deprecation in the 3.1.x
+line (operator decision, November 1, 2026, recorded on
+[#325](https://github.com/durable-workflow/server/issues/325)). Upgrade from
+PHP while running 3.0.x; the release that deprecates takeover will say so in
+its release notes. New installations start on a fresh native database and
+never take over a PHP one.
+
 ## Shape
 
 Takeover is an explicit command, never a side effect of starting the server.
diff --git a/docs/rust-server-upgrade.md b/docs/rust-server-upgrade.md
index 421908fc4..163fd9da7 100644
--- a/docs/rust-server-upgrade.md
+++ b/docs/rust-server-upgrade.md
@@ -5,6 +5,9 @@ backup-first, sequential upgrade of an existing PHP database. This document
 describes the first executable preparation step; production takeover remains
 unimplemented and unqualified.
 
+Takeover of a PHP database is planned for deprecation in the 3.1.x line; see
+[the takeover note](rust-server-upgrade-takeover.md#deprecation).
+
 ## Read-only source inspection contract
 
 The native `upgrade-inspect` command inspects a configured existing PHP