How a request becomes a video

A request moves through a fixed sequence of stages. Skipping or reversing a stage is refused by design, and each stage writes a signed receipt linked to the one before it, so the path from your instruction to the finished file can be verified after the fact.

1. ReceivedYour instruction is accepted and a reference is issued.
2. PlanningThe instruction is compiled into a structured production plan and checked against rights and safety policy.
3. CreatingThe plan, never your original text, is sent to a commissioned video model.
4. Safety scanEvery generated shot is scanned before release; a refused shot stops the request.
5. Final reviewAn independent check re-derives its verdict from the finished file and the receipt chain.
6. ReadyThe video is available from your account, with a signed receipt for every stage.

What can hold a request

A request is held, not silently dropped, when a safety, rights, budget, capacity or provider condition is not met. A held request is reported as held in your account, with the reason by name.

What is recorded

The structured plan, the stage receipts, the finished files and their hashes. The original instruction text is not included in those records; a one-way digest of it is.