One direction of travel. A premise gets promoted to a draft when you commit to it; a draft gets published when it ships — and then it's immutable.
```
The point is to keep the friction where it belongs. Capturing an idea should cost one line. Drafting should feel like writing, not file management. And publishing should be a deliberate step that freezes the piece — to revise later, you copy it back to a new draft rather than editing history.
Essayists and newsletter writers get a frictionless place to capture premises before good ideas escape. Drafting with an AI collaborator happens on the actual piece, every revision in the timeline, instead of scattered across chat windows. And shipped work stays separate from work in progress — a clean record of published pieces with canonical URLs and channels.
## The flow
```
ideas/ one-line premises, headlines, fragments — kept short on purpose
↓ commit to writing it
drafts/ active prose; frontmatter tracks status, word count, parent idea
↓ ship
published/ shipped work; carries published_at, canonical_url, channel — immutable
```
The pack ships an `idea`, `draft`, and `published` template. Structure only — the meaning of each stage lives in the folder guidance the agent reads, so your prose stays uncluttered.
## The scenario
A thought hits you on a walk: *"the best abstraction is the one you didn't write."* You drop it into `ideas/` as a single line. Two weeks later you commit to it:
> Promote the "best abstraction is the one you didn't write" idea into a draft. Pull the premise into the draft template and set status: drafting.
You write it with your agent over a few sessions — every revision captured in the [timeline](https://openknowledge.ai/docs/features/timeline-and-recovery), no manual versioning. When it's ready you publish, and the piece moves to `published/` with its canonical URL filled in. The draft's full history stays intact; the published copy is frozen.
## What's in your project after seeding
Pick **Writing pipeline** in the starter-pack picker, or run:
```bash
ok seed --pack writing-pipeline --root writing
```
The picker pre-fills the `writing/` subfolder; `--root writing` does the same from the CLI (omit it to scaffold at the project root):
```
your-project/
└── writing/
├── ideas/ one file per premise, flat
├── drafts/ active prose; status: drafting | review
└── published/ shipped, immutable
```
Each folder carries its `.ok/frontmatter.yml` guidance and templates. If a draft needs research notes, the agent creates `drafts/