# Fixed-brief production study kit

**Status: illustrative example, not a completed study.** ContentX publishes this planning material about its own service. No client, operator, production provider or reviewer is represented by the assumptions. No video has been rendered and no savings or quality advantage has been measured.

Download example.json, cost-model.mjs and verify.mjs into one folder. With Node.js 22 or later run `node verify.mjs`. The deterministic example totals $182: 3 attempts × $4 + 2 hours × $50 + 1 revision hour × $50 + $0 rights + $5 delivery + $15 overhead. All failed attempts are included. This is neither a quote nor typical production cost. Zero rights cost assumes the text-and-shape brief uses no licensed assets; verify that for the actual run. Taxes, distribution spend and revenue are outside the model.

## Editable approval workflow

1. Brief owner freezes audience, output format, script, permitted assets, budget and acceptance rubric in example.json. Record an immutable brief version.
2. Producer records provider/model/tool versions, prompt/config revision, timestamp, every attempt (including failure), output hash, actual provider charges and active labor. Preserve invoices and permissioned source records.
3. Editor records each manual change against an output version. The v1→v2 script in the example is a hypothetical edit: remove unsupported claims, correct captions and add a review step. It is not evidence of a human editor having reviewed a render.
4. Reviewer checks factuality, source/likeness/audio rights, text readability, captions, timing, format and brand fit. For each criterion record pass/fail and a reason; any failed or untested criterion prevents approval.
5. Named decision owner records approval date and exact output hash. A revised output needs a new review. Rejected attempts and their cost remain in the ledger. Publish the permissioned output and rubric with limitations.

## Brief → qualified inquiry

Use the Studio brief at https://content-x.ai/studio#lead. Include business/use case, intended audience, required format and quantity, timeline, approximate budget, rights available, decision owner and success criteria. HTTP acceptance is a received submission, not a qualified lead. Qualification requires an authorized reviewer to confirm service fit, permissioned inputs, feasible scope/budget/timing and a reachable decision maker. Track accepted, needs clarification, declined and duplicate separately, with reasons and actual timestamps. Do not use this example as a real submission.

## Result record to complete

Production date: not run. Actual cost: unavailable. Render/output URL and hash: unavailable. Producer: unassigned. Reviewer: unassigned. Rights verification: pending. Failed attempts: unmeasured. Quality rubric: unreviewed. Approval: not granted. Independent comparison: not conducted.

Use production-review-record.md for the itemized actual-run ledger, localization review and exact-version human sign-off. It is blank until completed with evidence.