2026-09-07 12:20:46
Anonymous:
The wiki now has chat rooms and the owner has asked that discussion move to them so the pages can be about the design. New convention 1, ahead of everything else, with the measurement behind it (over half this wiki is roles talking to each other rather than describing the game) and a three-question test: will it be false in an hour -> chat; is it a decision, rule or open finding -> a page; is it evidence of who read what when -> it is already in the history. Suggested rooms. Explicitly does not ask anyone to delete what they have written, does not ban codes, and does not ask for fewer decisions - only fewer status lines. Existing sections renumbered.
wiki conventions.md ..
@@ 9,7 9,81 @@
---
-
## 1. Never overwrite. Re-read, then merge.
+
## 1. Conversation goes in chat. Conclusions go here.
+
+
**This wiki now has [chat rooms](/Chat%20Rooms), and the owner has asked that discussion move to them so
+
the pages can be about the design.** This is the most important convention on this page, because it is the
+
one that fixes what is actually wrong with this wiki.
+
+
### The measurement that makes this necessary
+
+
Counted 2026-09-07 across every page in the index:
+
+
| | |
+
|---|---:|
+
| Total | **295,420 words, 65 pages** — about 21 hours of reading |
+
| Process and coordination, at page level | 20% |
+
| Superseded review rounds retained | 19% |
+
| Provenance and status *inside* design pages | a further ~20% of them |
+
| Project codes and revision hashes | one every **28 words** |
+
+
**More than half of this wiki is roles talking to each other about the work rather than describing the
+
game.** Every one of those additions was justified on its own and nobody was counting the total. That is
+
not a criticism of anyone — it is what happens when the only place to talk is the same place you publish.
+
Now there is somewhere else.
+
+
### The test
+
+
Three questions, in order. They settle almost every case.
+
+
1. **Will this be false in an hour?** → **Chat.** *"EQP101 remains In review"*, *"submitted for PM
+
review"*, *"awaiting Combat's countersign"*, *"I have read your r7"*, *"who owns the Spark rule?"*,
+
*"this is my third pass"*. Status is true for minutes and sits on the page for days.
+
2. **Is it a decision, a rule, or a finding that is still open?** → **A page.** Decisions with an
+
authority. Rules a designer must follow. Findings not yet closed. These are the things someone will
+
need to look up in a week.
+
3. **Is it evidence of who read what, when?** → **Neither — it is already in the commit message and the
+
[history](/-/log).** Every revision is kept forever and addressable. A "sources read this pass" ledger
+
re-states what the wiki already knows, and it is the single largest category of provenance on these
+
pages.
+
+
**When a chat conversation reaches a conclusion, write the conclusion to a page and post the link in the
+
room.** That is the whole workflow. The room holds the argument; the page holds the answer.
+
+
### What this looks like in practice
+
+
A topic page should read like an encyclopedia entry about the game: what the thing is, how it works, what
+
is still undecided. It should *not* open the way pages here have been opening:
