---
name: content-production-pipeline
description: Takes raw source material from intake through editing, derivative generation and per-channel task creation, tracking each asset's state so nothing is lost or double-processed. Use when the user asks to process content, run the content pipeline, prepare assets for publishing, or turn a long recording into channel-ready pieces.
metadata:
  version: "1.1.1"
---

# content-production-pipeline

> **Client-neutral reusable package.** No client names, tenant or workspace identifiers, account or
> resource IDs, customer records, credentials, or internal paths. All examples are synthetic.

| | |
|---|---|
| Live catalog name | Content Production Pipeline |
| Live category | Files & Content |
| Catalog entry | 11 |
| Internal capability ID | `CAP-FC-02` |
| Provider | Storage, editing and project systems |
| Availability | Candidate; validate in the active Workspace |
| Deliverable type | `limited_pilot_package` |
| Validation status | Candidate; local package validation only |
| Version | 1.1.0 |


## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant
bindings for the required inputs below; this public package supplies no client facts or authority.
Consume `ask-ollie-authority-core` for authority, `outloop-access-fallback` for recovery and
resource verification, `email-lifecycle-core` for recipients, approvals and stored-copy delivery
verification, and the bootstrapper Runtime Contract for ownership, scheduling and completion.
These owners govern execution; this Skill does not implement a competing runtime.

Select the relevant expertise below for the requested outcome. Runtime governs combining Skills,
partial use and completing missing steps with other authorized capabilities. This Skill's domain
scope does not limit the Operator's wider authorized task. Preserve domain safety restrictions.
Verify findings against source evidence and read back any resulting artifact or authorized change.

## Business outcome

Raw material becomes channel-ready assets on a predictable cycle, with the original never modified.

## Operating modes

Read · Analyze · Draft

## Prerequisites — what must be true before this runs

- Workspace Context (brand, references)
- Approved storage and project grants
- A channel matrix

## Required inputs

| Input | Source |
|---|---|
| Intake source and the approved asset library | Workspace configuration |
| Channel matrix — which derivatives each channel needs | Required |
| Brand and voice rules | Workspace Context — brand |
| Naming and versioning convention | Configuration |
| Named approver at the publish boundary | Configuration |

## Never edit the original

Duplicate the raw master and work on the copy. An in-place edit destroys the only source you have, and a pipeline
that cannot be re-run from source is not a pipeline.

## Only real supplied material

Use only assets the client actually supplied. Do not substitute a generated image or a synthesized clip for real
material in anything intended for publication, and never present generated content as captured footage.

## State tracking prevents double-processing

Each asset carries an explicit state. A pipeline that re-reads its intake without state will reprocess the same
asset every cycle — expensive, and it produces duplicate downstream tasks.

## Action classification

| Action class | This workflow |
|---|---|
| Read | Intake assets, existing library, pipeline state, downstream task status |
| Analyze | Classification by type and length, derivative planning, duplicate detection, state reconciliation |
| Draft | An edited master, planned derivatives, and a per-channel task with its brief |
| Write with approval | Creates downstream tasks. **Publishing is out of scope** — a channel workflow does that |
| Destructive | None. The raw master is duplicated, never edited in place |

## Approval and delivery

The Operator applies Authority Core and the active Workspace approval policy to any requested
mutation. Email Lifecycle owns recipient classification, sending and stored-copy verification.
The action table defines this capability's domain scope; it grants no permission by itself.

## Expected output

An edited master, a derivative set, and one task per target channel carrying the brief and the asset reference.

## Synthetic placeholders used in this package

These are illustrative only. Real values come from the client's own workspace configuration and are
never written back into this package.

| Placeholder | Meaning |
|---|---|
| `INTAKE_PLACEHOLDER` | Intake source |
| `CHANNEL_PLACEHOLDER` | Target channel |
| `LIBRARY_PLACEHOLDER` | Approved asset library |