Operations applied to content
Pipelines
Four cross-cutting operations — repurposing, search and answer optimization, voice enforcement, and performance feedback. Operations, never categories.
Semi-manual
Not a kind of content
These are things done to content rather than kinds of content. That distinction is doing real work: treating repurposing as a category would put it alongside case studies and onboarding emails, which are triggered differently, read different things, and pass different review standards.
An operation applies across all of them. A category is a shape of work. Mixing the two produces a taxonomy that cannot be automated because its members do not behave alike.
The four
Repurposing turns one substantial piece into the several smaller ones it can support. This is why social posts and a newsletter cost close to nothing once the underlying work exists — and it is the only one of the four currently in the first phase.
Search and answer optimization covers structure, internal linking and machine-readable markup, so a definition can be recognized as a definition.
Voice enforcement applies house style at drafting time and checks it at the gate.
Performance feedback takes what happened and routes it back. It depends on measurement, which is not built.
Each has a product face
The same work looks different from outside the system. Voice enforcement, offered on its own, is a checker. Search optimization, offered on its own, is a schema generator and a link optimizer. That is not a coincidence — an operation inside a system is a product outside it.