--- title: "Posts and statuses" description: "The six current states a post moves through, the three author modes, the freshness review queue, and the views figure on a published post." updated: "2026-08-25" verifiedAgainst: - packages/shared/src/index.ts - packages/shared/src/posts-helper.ts - packages/shared/src/content-freshness.ts - apps/web/app/app/posts/page.tsx - apps/web/lib/post-list-presentation.ts --- Every article is a Post, and a Post carries two facts that are easy to confuse: **status** is where it is, **author mode** is who produced it. ## Status | Status | Meaning | | ---------------- | ------------------------------------------------ | | `idea` | Recorded, nothing written | | `researching` | Research is running | | `draft` | A real draft exists and can be edited | | `needs_approval` | Waiting at its Content Direction's approval gate | | `scheduled` | Approved and waiting for its publication slot | | `published` | Live on your blog | The full table with what each status allows is in the [post status reference](/reference/post-status). ## Author mode | Mode | Meaning | | ----------- | ------------------------------------------------------------------ | | `Autopilot` | Produced by Autopilot running in Full mode | | `Assisted` | Produced by Autopilot running in Assisted mode | | `Human` | The words are yours: an import brought in with `polish_preserving` | Author mode is not a quality signal. It is provenance: it answers who to ask about the article, and which parts of the pipeline touched it. ## A status worth understanding Not an error. It means the post reached its Content Direction's gate and the gate is closed to automation. A Direction set to `review` puts every one of its posts here. See [review and approval](/autopilot/review). Freshness is a separate assessment, not a Post status. A `published` Post stays published while a Knowledge change, qualified traffic decline, competitor signal, repeated negative reader feedback, or editorial interval waits for review. ## The freshness queue Because freshness is not a status, it gets a filter of its own beside the status filter, and working it is how you keep live articles honest without unpublishing anything. | Filter | Shows | | ------------------------ | ------------------------------------------------------ | | Needs freshness review | Every article with an open review, whatever its reason | | Verified fact changes | A fact the article leans on has moved or is disputed | | Review due | The editorial interval or another prompt came round | | Refresh in progress | A refresh draft is being generated | | Refresh ready for review | That draft is written and waiting for you | A count of open reviews sits above the table and flags itself when it is not zero, and every row in the queue carries a badge naming its state and shaded by how serious the finding is. The filter appears once the Project's first verified assessment has finished, and on a Project with more than a thousand open reviews the counts and filters cover the first thousand. Every one of these leaves the Post's status alone. A `published` article in this queue is still live and still `published`. What each reason means, what evidence sits behind it, and what to do about it are all in [freshness and conflicts](/knowledge/freshness). ## Views A published post carries its view count in the row, beside its word count and the date it was last updated. These are privacy-respecting views Blogged recorded itself, so they start when the post went live under Blogged and do not include history from wherever the article lived before. Posts that are not published carry no figure, because there is nothing to count yet. ## Finding posts The Content workspace lists them with filters for status, Direction, freshness and Google indexing, plus a search across titles and content. Opening one takes you to [the editor](/content/editor).