<!--
  scaffold: content-pipeline-routing.md
  bucket: content-voice (Bucket 6)
  what belongs here: content-pipeline routing rules.
    - Prose → writer role.
    - Surface-specialised content → operator-side specialised writer roles.
    - Content-publishing extensions (schedulers, LI tools) are operator overlays.
    - Never hand-craft content in the main thread when dispatching produces higher quality.
-->

# Content pipeline routing

## The rule

Route content through the right pipeline. The PA does not draft in the main thread when a dispatch produces higher-quality voice-consistent output.

## Base routing

- **Prose (essays, articles, long-form).** → `writer` role.
- **Surface-specialised content (LinkedIn posts, tweets, newsletters, ad copy).** → operator-side specialised writer role (`linkedin-writer`, `newsletter-writer`, etc.) that extends the base `writer`.
- **Meta content about the operator's own operating model.** → the PA can draft inline (this is not audience-facing content; voice discipline is looser).

## Base writer role

`packages/core/roles/writer/definition.md`. Voice-doc-driven — reads voice-guide + banned-tells + operator profile from operator-configured paths on every dispatch. Deterministic: same inputs, same voice output.

The base writer reads voice from config; the operator points the config at `operator/knowledge/writing/voice-guide.md` (or the operator's chosen path).

## Operator-side specialisations

Surface-specialised writers layer surface-specific rules on top of the base:

- **`linkedin-writer`** — LI-specific structural rules (character targets, opener conventions, engagement patterns) layered on base writer voice.
- **`newsletter-writer`** — newsletter-format rules layered.

Specialisations MUST inherit the base writer's read-then-gate-then-deliver sequence and MUST NOT relax the banned-tells check.

## Content-publishing tooling

**Out of core.** Content publishing is a per-operator concern — the surfaces the operator ships to, the cadence, the scheduling, the metrics. All of these are operator-side.

If the operator ships a content-publishing tool (e.g. a `content-pub` CLI), it lives under `operator/extensions/tools/`. Content state changes go through that tool; direct edits to schedule data are lint-refused.

<!-- OPERATOR: name your content-publishing tool here (if any) and its verb surface. -->

## Push back on voice-flat drafts before they ship

Voice restarts caught mid-draft are cheap. Post-publication corrections are expensive. The PA reads the drafted output BEFORE shipping and pushes back on obvious voice failures — even after a well-briefed dispatch.

## Include voice + banned-tells references in every writing brief

Workers don't inherit voice by osmosis. The brief MUST name the voice-guide path and the banned-tells path in Tools-and-sources.

## Related

- CLAUDE.md.template Bucket 6 rules 1, 3.
- `packages/core/roles/writer/definition.md` — the base writer role.
- `voice-guide-shape.md` / `banned-ai-tells-shape.md` — the template skeleton pointers.
