The queues

GET /api/v1/articles/editorial/queue

Open to anybody who can manage questions — a moderator, or the holder of a category grant. A grantee sees only their branches. An article with no category is moderators-only, because an article in no branch is in nobody's branch.

Six lists, each capped at 100, all drawn from articles that are not in the bin.

Queue	Response key	An article is in it when
Waiting for review	awaiting_review	status == "in_review"
Drafts	drafts	status == "draft", most recently touched first
Generated but unread	machine_drafts	status == "draft" and generated_by is set — a model wrote it and nobody has been back to it
Published without sources	published_without_references	status != "draft" and references_json is empty
Published without questions	published_without_questions	status == "published" and nothing in question_article_links points at it
Barely written	thin	fewer than 2 sections — whatever its status

Two of those criteria are broader than their names

Published without sources matches status != "draft", so an article sitting in review with no references appears there too, not only a published one.

Barely written ignores status entirely, so a two-line draft shows up in both drafts and thin. That is deliberate — the queues are lenses, not partitions, and one article can want a person's attention for two different reasons.

Alongside the six lists the response carries counts — total, draft, in_review, published, trashed — where trashed is a count of everything in the bin. The bin is not one of the queues; it is reached from its own page.

Reading the queues

They are ordered by what a person can do about them, not by urgency:

• awaiting_review is somebody waiting on you.
• machine_drafts is work that exists but has never been judged.
• published_without_references and published_without_questions are articles that are live and incomplete — visible to learners while missing the thing that makes them trustworthy or useful.
• thin is the pile of good intentions.