Line: Editorial¶
Enterprise analog: Newspaper / newsroom + web publisher.
Covers: Writing Pipeline (articles, research desks, releases).
Tracking: Notion Workstreams database — view: Editorial Work. Gatekeeper: Editor-in-Chief. See agent setup.
Not a renamed software SDLC.
Primary archetype: content-product. Editorial may add a Software workstream when software is needed to achieve the same Initiative outcome. A distinct market opportunity creates a related Product Initiative through Portfolio.
Production workflow¶
Assign → Report → Draft → Edit → Fact-check → Localize → Stage → Publish → Update
| Stage | Inventories |
|---|---|
| Assign | desk.journal \| perspective \| research \| releases; beat; priority |
| Report | research-depth; source-policy (research work occurs within Report) |
| Draft | voice/brand; time-model.frozen \| living |
| Edit | structure and quality gates under copy-edit policy |
| Fact-check | claim verification against sources |
| Localize | locales en\|es\|de; translations on/off |
| Stage | pre-publish readiness |
| Publish | channel hectorsanchez.eu; tool writing-publisher-mcp |
| Update | living vs frozen policy |
Archive is a disposition of the Editorial workstream or Initiative, not a compound stage ID with Update.
Editorial Publish is line production. Shared host health is the Operate line; writing deploy uses Editorial.Publisher with Operate standards (secrets, host).
The stage order is decided, but exact entry criteria, exit evidence, allowed transitions, and reopen behavior are not yet complete for every stage. Until those contracts exist in the corpus, Conductor must emit a gap rather than authorize a deterministic transition.
Roles (newsroom)¶
Editor-in-Chief, Desk Editor, Reporter, Researcher, Fact-checker, Copy editor, Publisher, Translator — see docs/roles-and-tooling.md.
Workspace examples¶
- Research:
04 - Writing Pipeline/staging/research/germany-daily-temperature-distributions/ - Journal:
staging/journal/why-i-write/ - Perspective:
staging/perspective/state-of-ai-industry/ - Live contract: articles + locales via writing-publisher-mcp
Cross-line coordination¶
- In: Portfolio adds an Editorial workstream for a content Initiative.
- Lab release narrative: A verified Lab URL adds or activates an Editorial
releasesworkstream on the same Initiative. - Tooling needed: Add a Software workstream with the Editorial requirements and evidence bindings; do not create a silent side project.
- Market opportunity: Create a separate Product Initiative linked with
derived_from. - Evidence: Publish and update outcomes are recorded on the Editorial workstream and may satisfy Product Ship-signal conditions.
Tooling: Production artifacts live in writing-publisher-MCP and the site repository. Notion owns the Initiative and Editorial workstream state and links to the slug and live URL; no separate Editorial project board is needed. See tooling-map.md.