# Production Workflow

## Status

Draft

## Goal

Define how a `ContentItem` is planned, created, revised, and prepared before or during approval.

This feature is intentionally separate from approval workflow. Approval workflow decides whether content is approved for publishing handoff. Production workflow describes how content gets made.

## Reviewable Object

Production work happens around a `ContentItem`.

Assets, revisions, comments, assignments, due dates, channels, notes, and content metadata are part of the production context.

## Initial Scope

Production workflow may eventually cover:

- draft creation
- copy/caption preparation
- media production
- asset linking
- revision history
- internal comments
- assignments and ownership
- due dates
- readiness for review

## Relationship To Approval Workflow

Production workflow can prepare a `ContentItem` for approval, but it does not define who must approve it.

A `ContentItem` may require production work before it can enter review, especially for content formats such as video where work includes planning, filming, editing, revisions, and asset delivery.

## Initial Business Rules

- Production history must remain attached to the `ContentItem`.
- Revisions must not overwrite prior work invisibly.
- The latest asset or revision must be clear.
- Production collaboration should support both simple posts and more involved media work.
- Approval decisions should remain distinguishable from production comments or internal readiness signals.

## Open Questions

- Which production states are needed beyond the fixed `ContentItem` lifecycle states?
- Should production have assignments or owners in v1?
- Should production readiness be required before approval can start?
- How should asset revisions be compared or marked as current?
- Should different content types have different production requirements?

