Who decides
The people accountable for what gets published, and what each of them decides.
Last updated
No one is named here yet. That is a gap, not a style choice. “The editorial team” is not accountability — a reader should know whose judgment they are trusting. The roles below are real and defined; the names go in before the first real story is published.
The roles
These are jobs, not job titles. At founding scale one person may hold several — what matters is that each decision has an owner.
| Role | Decides |
|---|---|
| Editor | Whether a story fits, how it is shaped, and when it publishes. Applies the rubric on the contributor guide. |
| Moderator | Which peer responses are published, under the response guidelines. |
| Operator | Accounts, access, retention, and responses to data requests. |
| Corrections owner | Whether something is corrected and whether it is logged publicly. |
Access follows those roles in the software itself: the staff area enforces viewer, editor and operator permissions on the server, so the boundary is real rather than a convention.
When an editor is too close to a story
An editor who has a relationship with the contributor, or with an organization named in the story, hands the decision to someone else. Where there is genuinely no one else — which happens at this size — the relationship is disclosed on the story.
If you think a decision was wrong
Say so through contact. A different editor reviews it where one is available, and we will tell you plainly when one is not.