USE WHEN
Use this manual when
- Teams moving from tests to weekly or daily output
- Productions using multiple models, accounts or local nodes
- Producers comparing workflows rather than advertised unit prices
PRODUCTION MANUAL · Production management
AI short-drama cost and rework ledger: measure cost per approved shot
Combine model spend, queue time, operator time, retries, rejects and post repair in a shot-level ledger instead of budgeting from one generation price.
DO NOT USE AS
Do not use it as
- Projects without one shot-approval definition
- Equating credits or subscription fees with total production cost
01
VERIFIED FACTS
What the evidence currently establishes
- 01
Hosted model capabilities, versions and access change over time, while open models transfer hardware, dependency and operations costs to the team; both need one delivery-cost method.
- 02
ComfyUI's JSON workflows and output metadata can help recover configuration, but reproduction still requires model, nodes, inputs and environment.
02
REQUIRED INPUTS
Prepare before starting
- Shot ID, target duration, complexity class and reviewer
- Model/workflow version, run count, spend or local compute use
- Queue, generation, download, operator and post-repair time
- Failure reason: narrative, character, physics, audio, compliance or technical
- Approved version, accepted seconds and delivery date
03
WORKFLOW
Execution workflow
- 01
Define an approved shot and revision taxonomy before production.
- 02
Write shot ID, version, time, spend and output location for every job.
- 03
Require a standard failure reason; notes may elaborate but cannot say only “looks bad.”
- 04
Include preparation, review, download, edit and audio repair in the same shot record.
- 05
Calculate first-pass rate, retries, cost per approved shot and cycle time by shot class.
- 06
Compare routes only with aligned assets, versions, periods and approval conditions; review outliers weekly.
04
DELIVERABLES & QC
Deliverables and acceptance
Required deliverables
- Shot-level cost and rework CSV
- Failure-reason taxonomy
- Weekly summary by shot class
- Model/workflow version log
- Outlier-shot postmortem
QC checklist
- Every cost maps to a shot and version
- Operator and post time are included
- Failure reasons use one taxonomy
- Cost per approved shot includes rejected runs
- Comparisons lock assets, period and approval method
EVIDENCE BOUNDARY
What this manual does not prove
AniVerse does not publish an industry-average cost detached from team, territory, plan and shot class. This guide defines the data structure and calculation boundary; real budgets must come from the project's own reproducible ledger.