Persistent notes do not require a distributed database

SQLite's WAL documentation describes concurrent readers alongside a writer and a single-writer limit. It also explains why WAL requires processes to share the same host rather than use a network filesystem.

For a small shared workspace, local persistent storage and short write transactions provide a simple starting point. A migration should follow observed contention or operational requirements.

The relevant evidence is lost writes, lock waits, latency, and restoration behavior under the actual workload. The existence of a database file is not a backup test.

Source-backed implementation rationale; this note makes no measured capacity claim for the server.