docs: add a maintenance and continuity page

A reader who checks maturity asks who maintains the gem, how a release
is published, and what they keep if maintenance stops. One page now
answers these questions and asks for more maintainers.

The README, the versioning page, and the comparison pages link to the
new page and no longer state a count of maintainers. A new test fails
when a page states one.

Author: cardmagic

README.md

@@ -13,7 +13,7 @@ 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. One maintainer.
+promise. First public release: August 6, 2026.
 
 **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
@@ -199,6 +199,7 @@ every claim in [`test/guides/`](test/guides/):
 - [Reminders](docs/reminders.md)
 - [Reactive ERB](docs/realtime.md)
 - [Detailed architecture](docs/architecture.md)
+- [Maintenance and continuity](docs/maintenance.md)
 - [Detailed documentation](docs/)
 
 The dashboard, benchmarks, migration cookbook, schema, and exhaustive API

docs/compare/good-job.md

@@ -210,7 +210,7 @@ How it works:
 
 - First public release: August 6, 2026.
 - Version 1.0.0: October 13, 2026. The public API follows [semantic versioning](../versioning.md).
-- One maintainer.
+- [Maintenance and continuity](../maintenance.md) tells you who maintains the project and how a release is made.
 - 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](../benchmarks.md) are development measurements. Longer soak tests are open work.
 

docs/compare/solid-queue.md

@@ -205,7 +205,7 @@ How it works:
 
 - First public release: August 6, 2026.
 - Version 1.0.0: October 13, 2026. The public API follows [semantic versioning](../versioning.md).
-- One maintainer.
+- [Maintenance and continuity](../maintenance.md) tells you who maintains the project and how a release is made.
 - 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](../benchmarks.md) are development measurements. Longer soak tests are open work.
 

docs/comparisons.md

@@ -23,4 +23,4 @@ The problem guides start from the same choices:
 
 ## Status
 
-Solid Objects 1.0.0 shipped on October 13, 2026. The first public release was on August 6, 2026. It has one maintainer. 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. See [versioning](versioning.md).
+Solid Objects 1.0.0 shipped on October 13, 2026. The first public release was on August 6, 2026. 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. See [versioning](versioning.md) and [maintenance and continuity](maintenance.md).

docs/maintenance.md

@@ -0,0 +1,65 @@
+# Maintenance and continuity
+
+This page tells you who maintains Solid Objects, how a release is made, and
+what you keep if maintenance stops. It also tells you how to help maintain the
+project.
+
+## Who maintains it
+
+Lucas Carlson ([@cardmagic](https://github.com/cardmagic)) is the lead
+maintainer of the Ruby gem `solid_objects` and of the npm package
+[`solid-objects`](https://github.com/cardmagic/solid-objects-js). The two
+packages use the same model and the same correctness contract. A change to the
+model goes into both packages, and the
+[parity ledger](https://github.com/cardmagic/solid-objects-js/blob/main/docs/parity.md)
+records each difference between them.
+
+The same maintainer sells [Solid Objects Pro](https://solidobjects.pro), a
+commercial package that batches operations at scale. Pro depends on this gem.
+This gem does not depend on Pro, and it needs no account, license key, or
+service from the maintainer.
+
+## How a change is checked
+
+CI runs on each push and each pull request:
+
+- The full test suite on SQLite, on each pair of Ruby 3.3, 3.4, or 4.0 and
+  Rails 7.1, 7.2, 8.0, or 8.1.
+- The full test suite on PostgreSQL and on MySQL, with both MySQL clients.
+- Standard, RuboCop, RBS, Steep, and Brakeman.
+
+[Compatibility and maturity](virtual-actors.md#compatibility-and-maturity)
+lists the supported versions. The [correctness contract](correctness.md) lists
+the guarantees that the tests check.
+
+## How a release is made
+
+1. The maintainer pushes a version tag, for example `v1.0.3`.
+2. GitHub Actions runs all test jobs again on that tag.
+3. If all test jobs pass, GitHub Actions builds the gem and pushes it to
+   RubyGems with trusted publishing. The repository keeps no RubyGems key.
+4. The same job makes a GitHub release and attaches the gem file.
+
+[Versioning](versioning.md) tells you what a release can change.
+`CHANGELOG.md` lists each release.
+
+## What you keep if maintenance stops
+
+- **Your data.** Actor state, mailboxes, reminders, and effects are rows in
+  your application's database. [Database schema](database-schema.md) describes
+  each table. No service of the maintainer holds your data.
+- **The code.** The [MIT License](../MIT-LICENSE) lets anyone use, change,
+  fork, and publish the code.
+- **The checks.** The tests and the CI configuration are in this repository. A
+  fork can check its changes with the same suite.
+
+## Help maintain Solid Objects
+
+The project wants more maintainers. Experience with Rails, with locks and
+transactions in PostgreSQL or MySQL, or with TypeScript and Node.js helps.
+
+1. Read [CONTRIBUTING.md](../CONTRIBUTING.md).
+2. Send a small pull request: a fix, a test, or a correction to a guide.
+3. After some of your pull requests are merged, open an
+   [issue](https://github.com/cardmagic/solid-objects-ruby/issues) to ask to
+   become a maintainer.

docs/versioning.md

@@ -41,8 +41,8 @@ lists the current minimum versions.
 
 Version 1.0 is a promise about the API. It is not a claim of measured scale.
 The [benchmarks](benchmarks.md) are development measurements and do not
-guarantee capacity. Longer soak tests are open work. The project has one
-maintainer, and no production use by other people is known.
+guarantee capacity. Longer soak tests are open work. No production use by
+other people is known.
 
 ## Releases before 1.0
 

test/unit/maintenance_documents_test.rb

@@ -0,0 +1,34 @@
+# frozen_string_literal: true
+
+require "test_helper"
+
+class MaintenanceDocumentsTest < ActiveSupport::TestCase
+  ROOT = File.expand_path("../..", __dir__)
+  MAINTAINER_COUNT = /\b(?:one|only|sole|single)\s+maintainer\b/i
+
+  def guide(path)
+    File.read(File.join(ROOT, path))
+  end
+
+  def documentation_paths
+    [ "README.md", "CONTRIBUTING.md", *Dir.glob("docs/**/*.md", base: ROOT).sort ]
+  end
+
+  test "the README links to the maintenance page" do
+    assert_includes guide("README.md"), "(docs/maintenance.md)"
+  end
+
+  test "the maintenance page names the lead maintainer" do
+    assert_match(/is the lead\s+maintainer/, guide("docs/maintenance.md"))
+  end
+
+  test "no page states a count of maintainers" do
+    pages = documentation_paths.select { |path| guide(path).match?(MAINTAINER_COUNT) }
+
+    assert_empty pages
+  end
+
+  test "the maintenance page tells a contributor how to start" do
+    assert_includes guide("docs/maintenance.md"), "(../CONTRIBUTING.md)"
+  end
+end