Lifecycles
The statuses of pitches, stories and outputs, what each one means and what moves it to the next.
Pitches, stories and outputs each have a small set of statuses. They answer different questions, so they are kept separate: a pitch status is about an editorial decision, a story's status is about research, and an output's status is about writing.
Pitch
| Status | Meaning |
|---|---|
| Draft | A pitch you wrote yourself and previewed but have not sent to the desk. |
| New | In the review queue, waiting for a decision. A pitch Nuvelics writes starts here. |
| Approved | Accepted. A story has been created from it. |
| Dismissed | Reviewed and rejected. No story. |
What moves a pitch:
- Approve moves a New pitch to Approved and creates its story.
- Dismiss moves a New pitch to Dismissed.
- Reopen moves a Dismissed pitch back to New, returning it to the review queue. Approving a dismissed pitch directly is also allowed, and creates the story in one step.
- A manual pitch starts as Draft. It leaves the draft state when you create it, which sends it to the queue (New), when you create and approve it in one step, or when it is dismissed. Nothing moves a pitch back to Draft.
Approved is final. Approving creates a story an editor may already be working on, so un-approving would have to orphan or destroy it. Dismissing creates nothing, and a judgement that a pitch was not worth pursuing is the kind that turns out to be wrong once the story breaks. That is why a dismissed pitch can come back and an approved one cannot.
A draft is visible to the whole desk on the board, but it is not announced, delivered or counted in the pitch volume figures until it enters the queue. Only the person who created a draft can change it.
Story
A story is created the moment a pitch is approved, or when a story arrives from your newsroom system. Its status is its Enrichment status:
| Status | Meaning |
|---|---|
| Pending | Created and waiting to be picked up. |
| Running | Being researched. The story page fills in as it finishes. |
| Enriched | Researched, with claims, entities, a timeline and media. Outputs and pushes need this. |
| Failed | Enrichment did not complete. |
A story goes from Pending to Running to Enriched, or from Running to Failed. A failed story stays failed until an editor chooses Re-enrich; there is no automatic retry. Re-enriching an enriched story replaces its additional sources, claims, entities and media with a fresh run, and the original sources stay as they were.
A story that your newsroom system has archived or deleted counts as dropped: it cannot be enriched again or have outputs made from it.
Output
An output is generated, not filed, so its status says only how writing went:
| Status | Meaning |
|---|---|
| Queued | Added, waiting to be written. |
| Generating | Being written from the story's enrichment. |
| Ready | Written. You can read, edit, regenerate, check and push it. |
| Failed | Writing did not complete. Use Retry. |
Adding an output creates it as Queued; it is never written while you wait. A person has to ask for each output, and a paused spending cap stops new ones being queued.
Where an output has been sent is a separate fact. One output can be filed into two content management systems, so pushing never changes its status: Ready keeps meaning "written". The output's history lists each connection it has gone to.
Two more things sit beside the status:
- Edits and regeneration. What the model wrote and what an editor changed are stored separately, and the editor's version is the one you see. Regenerate writes a new draft that arrives alongside the current one; you keep or replace, and what you discard is gone.
- Claim checks. Findings never fail an output. An output with findings is still Ready. See Enrichment and fact-checking.
An output is marked as generated from an earlier version of its story when the story has been enriched again since; regenerate it to write it from the current story.