The editor surface
Three columns. Outline on the left (sections, headings, footnotes). Body in the middle (markdown with rich previews). Sidecar on the right (specialist annotations, asset library, schema fields).
Saving drafts
Studio saves on every keystroke; you do not click a save button. Each save fires content.draft.saved. Background workflows pick that up and start specialist runs.
Working with specialists
Fact-check
The fact-checker annotates each claim with a verification status. Three states: verified, uncertain, unverifiable. Hover a claim to see the source list it cited and the notes from the specialist. You can accept the annotation, dispute it, or replace the claim with a better-sourced version.
Copy edit
Inline suggestions appear as track-changes-style strikethroughs and additions. Accept, reject, or revise per change. The copy editor learns your house style across pieces.
SEO
The SEO optimizer runs on demand, not on every save. Click "run SEO" to get title and slug suggestions, internal-link opportunities, and a meta description draft.
Voice
The voice modeler is silent until it sees drift. If your draft strays from established voice, a soft chip surfaces in the sidecar with specific examples. You decide whether to recover voice or push the publication's voice intentionally.
Requesting review
Click "request review." Pick a reviewer, attach a note, and submit. The reviewer sees the piece, the specialist annotations, and your note. They can approve, request changes, or hand off.
Locked fields and unlock requests
Some fields lock at review time (slug, publish_at, hero image). If you need to change a locked field, request unlock from the reviewer in the same surface. Unlock decisions are audit-logged.