diff --git a/CHANGELOG.md b/CHANGELOG.md
index f25aaa6..2e79f46 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,13 @@
 # Changelog
 
+## 1.0.4 - 2026-10-18
+
+- The README no longer states the first public release date, that no
+  production use by other people is known, that longer soak tests are open
+  work, or that version 1.0 makes no claim of measured scale.
+  `docs/versioning.md` keeps the other three limits, and the README links it.
+  The comparison pages keep the first public release date.
+
 ## 1.0.3 - 2026-10-18
 
 - Add `docs/maintenance.md`. It tells you who maintains the gem, how CI checks
diff --git a/Gemfile.lock b/Gemfile.lock
index a1391f8..ae9fb7a 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    solid_objects (1.0.3)
+    solid_objects (1.0.4)
       actioncable (>= 7.1)
       actionpack (>= 7.1)
       actionview (>= 7.1)
@@ -392,7 +392,7 @@ CHECKSUMS
   rubocop-rails-omakase (1.1.0) sha256=2af73ac8ee5852de2919abbd2618af9c15c19b512c4cfc1f9a5d3b6ef009109d
   ruby-progressbar (1.13.0) sha256=80fc9c47a9b640d6834e0dc7b3c94c9df37f08cb072b7761e4a71e22cff29b33
   securerandom (0.4.1) sha256=cc5193d414a4341b6e225f0cb4446aceca8e50d5e1888743fac16987638ea0b1
-  solid_objects (1.0.3)
+  solid_objects (1.0.4)
   sqlite3 (2.9.5-aarch64-linux-gnu) sha256=78075b6337d3d182c6d2b4691049ed45cd220826160c9ea18946bf6a1de200dc
   sqlite3 (2.9.5-aarch64-linux-musl) sha256=18c801185deb4adc01ddb281e8f672a39e3d1729979ca91e39439cd3eac0402d
   sqlite3 (2.9.5-arm-linux-gnu) sha256=1bdfca0c7d63998c60b0f4a8e3c8df2d33800ccc4abd2d612eddbbbc92a4c48b
diff --git a/README.md b/README.md
index 6fee179..82bf6c0 100644
--- a/README.md
+++ b/README.md
@@ -13,12 +13,11 @@ model and when to use it.
 
 **Status.** Version 1.0: the public API follows semantic versioning and does
 not break before 2.0. [Versioning](docs/versioning.md) gives the limits of the
-promise. First public release: August 6, 2026.
+promise.
 
 **Production use.** One first-party application with more than 100,000 users
-runs it in production. That is a count of users, not a measure of load. No
-production use by other people is known. The [benchmarks](docs/benchmarks.md)
-are development measurements, and longer soak tests are open work.
+runs it in production. That is a count of users, not a measure of load. The
+[benchmarks](docs/benchmarks.md) are development measurements.
 
 **It is not** Solid Queue, SolidJS, or the `service_actor` gem, and it is not
 affiliated with Rails or Cloudflare.
@@ -208,10 +207,8 @@ explanations remain in `docs/`. The README stops here.
 ## Status and license
 
 Version 1.0 promises a stable public API. Its correctness core is tested
-against SQLite, PostgreSQL, and MySQL. It makes no claim of measured scale:
-the [benchmarks](docs/benchmarks.md) are development measurements, and longer
-soak tests are open work. [Versioning](docs/versioning.md) says what a release
-can change.
+against SQLite, PostgreSQL, and MySQL. [Versioning](docs/versioning.md) says
+what a release can change.
 
 Solid Objects is released under the [MIT License](MIT-LICENSE). It is an
 independent project and is not affiliated with, sponsored by, or endorsed by
diff --git a/lib/solid_objects/version.rb b/lib/solid_objects/version.rb
index 9e25219..fa617fb 100644
--- a/lib/solid_objects/version.rb
+++ b/lib/solid_objects/version.rb
@@ -1,5 +1,5 @@
 # rbs_inline: enabled
 
 module SolidObjects
-  VERSION = "1.0.3"
+  VERSION = "1.0.4"
 end