Nothing stored, literally

When you say "we keep nothing", people usually hear "we keep it, but we promise to behave". Here it's simpler: there is nowhere to keep it.

The server is a single process. State lives in a handful of in-memory maps: the benches, the members, the messages, the day's bans. There's no database, no Redis, no file, no volume mounted on the container.

What that means

• A restart wipes everything. That's a feature, not an incident.
• A conversation can't be restored, not even under a court order: there is no backup to seize.
• It can't scale horizontally without changing the architecture. Accepted.
• The logs contain counters only: number of benches, number of people seated. Never a message, never a coordinate.

The constraint is brutal, and that's what makes it credible. You can't betray a promise you are technically unable to keep any other way.

There's a test in the suite that boots the real server, sends a canary sentence, kills the process and reads back its entire output to check the sentence appears nowhere. The day someone adds a chatty log line, that test fails.