Three queues, each with its own order rule
- 01New submissions — oldest first. Nothing in this queue is live, so waiting costs a holder time and costs a reader nothing.
- 02Revisions against a published listing — oldest first, but the published copy stays up throughout, which is what makes oldest-first defensible here.
- 03Reports against a published listing — ahead of both, because the copy complained about is in front of readers while the report sits.
One inbox has one order, and these three need different ones. Collapsing them puts a report about live copy behind a fortnight of drafts; splitting them makes each queue’s order a decision somebody can defend, and a decision somebody can defend is one a holder can be told.
The reason list is closed
Reason codes
| Code | What it says | What the holder can do |
|---|---|---|
| category-wrong | the filing fails the category’s inclusion test | refile against the sibling named on the sheet |
| entry-duplicate | another entry already resolves this listed thing | ask for the two to be merged |
| name-off-register | the registered name does not match the register the portal draws on | correct the name or supply the register reference |
| body-off-subject | the body describes something other than what the category covers | rewrite the body or refile |
| contact-unreachable | the contact route did not answer when it was tried | supply a route that answers |
| slug-reserved | the requested slug is a word a surface answers on | choose another slug |
A moderator picks a code and may attach a note. The note is never the reason: a free-text reason cannot be counted, cannot be compared between moderators, and gives a holder nothing specific to fix. Codes make a queue countable, and a countable queue is the only kind whose rules can be argued about honestly.
A report carries a listing identifier and one code. It never carries anything about who raised it beyond the account identifier, and it is never shown to the holder with that identifier attached.
A record that only ever appends
- 1A state movesA moderator accepts, withdraws or removes, against a code.the queue
- 2One row is writtenListing, state before, state after, account, stamp, and the code.append only
- 3The holder is toldFrom that row and nothing else: the code, the sentence it maps to, the field, and what may be done next.no fresh wording
- 4A mistake is correctedBy a new row naming the row it corrects. The record shows both, never only the tidied version.never an edit
Nothing in the holder’s message is composed per holder, because a message written fresh each time is a message that can disagree with the record it describes.
Append-only has a cost, and it is accepted. The record grows and it is never compacted, so it is in the backup set and it is one of the three things a restore drill reconciles row for row.