# Creative Production Arm

*A validated creative package — scripts, scene plans, generated assets, and cost logs — built to hand off to another service. It never publishes externally.*

**Creative Production Arm** is a **connected "sister service"**: it produces a validated
`creative_production_package` (scripts, scene plans, generated assets, validation proofs,
storage + provider receipts, cost logs) and hands it to a parent marketing/sales/training
service. It does **not** schedule or publish externally itself.

## When to use it

When another service (or you) needs polished creative assets produced and validated, but
the publishing/approval happens elsewhere.

## What you need

| Setting | Notes |
|---|---|
| **Source URL** *(required)* | What the assets are grounded in |
| **Asset types** | short video, cover, static image, carousel, story asset |
| **Target duration** | 5–120s (default 30) |
| **Budget cap** | USD per run (default $25) |
| **Publish channels** *(optional)* | Passed through for the downstream service |

## How a run works

Every stage is **automatic** — this service produces an approval-ready package rather
than pausing for you:

1. **Normalize the request** — a typed brief (never inflates duration or budget).
2. **Media intake** — inventory the source media (no invented assets).
3. **Blueprint** — hook, scenes, narration, CTA, and asset mapping.
4. **Provider plan** — budget-aware provider selection and a cost estimate.
5. **Generate & validate** — produce assets with provider + storage receipts, then verify they're playable and within budget.
6. **Package** — assemble the final production package.

## Where you approve

Nothing internal — it emits an **approval-ready package** (with `approvalStatus` and
review/publish channels) that the **parent service** or downstream owner reviews and
publishes.

## What you get

A `creative_production_package`: the request, script, generated assets, a validation
report, the provider decision log, and a cost report — delivered over Tredy's service
**handoff protocol** so a downstream service can pick it up.