Written by practitioners, decided by editors.
The publishing engine, its permissions and its maker-checker control were built and tested — and until this tour, nothing was ever drawn. The contributor desk below is the design proposal for that missing interface; the editor’s queue is the reason the whole feature exists.
Publishing
Contributor desk
proposed — /world-app/ → Writing desk
This is the one surface with no interface at all today: the engine exists, the screen does not. So this drawing is a design proposal rather than a picture of something that runs.
Enforced by the real server
- No screen exists for this today — the engine is built, the UI is not
- Contributor standing is granted by a person, never earned automatically
- A published article is never edited in place
Your standing
Contributor Granted 4 March by the editorial team.
You may write and submit. Publication is decided by an editor who is not you.
Your manuscripts
| Title | State | With | Action |
|---|---|---|---|
| What a good estimate basis actually contains | Published | — | |
| Recovering a slipped programme without lying about the date | In review | Editor: R. Vance | |
| Contingency drawdown for people who hate spreadsheets | Drafting | — |
Submit “Recovering a slipped programme”
Before an editor reads it, four questions. These are recorded as you answer them now and are not editable afterwards.
Editor thread — “Recovering a slipped programme”
- R. Vance
Strong piece. Section three asserts a 12% recovery rate — can you attribute that, or shall we cut the number and keep the argument?
- You
It’s from our own portfolio, not published. I’ll cut the figure and rewrite the paragraph around the mechanism.
What this screen calls
| Endpoint | Status |
|---|---|
GET /api/world/contributor/me | Built |
POST /api/world/contributor/apply | Built |
GET/POST /api/world/contributor/articles | Built |
PATCH /api/world/contributor/articles/{id} | Built |
POST /api/world/contributor/articles/{id}/submit | Built |
POST /api/world/contributor/articles/{id}/messages | Built |
Publishing
Editor’s queue
proposed — /world-admin → Editorial
The editor’s side, and the refusal that matters most on this whole tour: the third manuscript below was written by the reviewer, under a different account — and the system knows, because the link between the two accounts was declared.
Enforced by the real server
- A contributor can never approve or publish their own article
- The check spans two account systems — the hard part of the whole feature
- Every decision note is kept; a later note never overwrites an earlier one
Waiting for review
| Manuscript | Contributor | Waiting | State | Action |
|---|---|---|---|---|
| Recovering a slipped programme without lying about the date | D. Okoro | 2 days | In review | |
| Contingency drawdown in practice | P. Raman | 5 days | Approved | |
| What a good estimate basis contains — part two | R. Vance You | 1 day | In review |
Contributor applications
-
T. Nowak Applied
“Fifteen years in rail planning. I want to write about what actually happens to a programme after sanction.”
Forum standing: 34 accepted posts · 0 upheld reports
Forum standing is evidence for your decision. It is never the decision — an earned-only gate is something an abuser can play for.
What this screen calls
| Endpoint | Status |
|---|---|
GET /api/world-admin/editorial/contributors | Built |
POST /api/world-admin/editorial/contributors/{id}/decision | Built |
POST /api/world-admin/articles/{id}/approve | Built |
POST /api/world-admin/articles/{id}/publish | Built |
| this screen | Not built — API only today |