Verification and gates
scene-studio’s verification is three layers: the approval gate where a human approves at each stage, the license gate enforced in remix, and the performance policy that plants speed in code. This section covers what each looks at, and the security baseline.
The approval gate
Section titled “The approval gate”approval-gate breaks each phase. AI doesn’t make a finished product in one shot. At each gate a human approves, edits, or rolls back.
Generative has four gates: Gate A (plan), B-1 (scenes), B-2 (images), C (video). Remix has three: Gate A (analysis), B (editing), and publish. On neither track does publish auto-pass.
The gates matter because outputs are kept as files. Each stage’s *.meta.json has a status planted, so even after a session break you recover which gate you cleared. At Gate C you can roll back to any stage, like “redo from planning,” “just scene 3,” “redo the image.”
fast-preview mode reduces human waiting without breaking the gate philosophy. In the preview default, the planning gates (A, B-1, B-2) auto-pass and run through to a video draft, and then a human reviews the actual video once at Gate C. The outputs remain and can be rolled back, and the no-auto-publish rule stays.
license-policy L2 — remix
Section titled “license-policy L2 — remix”A gate planted at every stage of the remix track. It can’t be bypassed.
- License-label verification: a source with no label is refused
- Fair Use of 30% or less: a limit on the amount of the source used
- At least three transformation duties: at least three transformations like cut, subtitle, zoom, BGM, SFX
- Automatic source attribution
- Automatic copyright-claim blocking
There’s one bypass path: the spot where the user explicitly accepts responsibility in license_responsibility.json. Otherwise, you can’t proceed to the next stage with a source short of the license bar (S5). The generative track doesn’t take a source, so it has no such gate.
The seven pipeline-performance policies
Section titled “The seven pipeline-performance policies”Speed is planted in code, not vibes.
- Preview/final two-mode: default preview (small resolution, 2 candidates, veryfast render), re-render to final once only after final confirmation
- Parallel Codex calls: scene candidates a/b/c and cross-scene bundles run in parallel within the concurrency limit
- Hash cache: sheets, images, subtitles, BGM, SFX in
_workspace/.cache/. On a cache hit, skip the Codex call - ffmpeg single-pass: composite in one filtergraph rather than per-scene clips
- per-step timings: record each phase’s wall time in
timings.json - 4–6 cut budget: limit the number of cuts
- Fast image backends for preview: flux-schnell, sdxl-turbo, sdxl-lightning
The target is 20 minutes per episode, 12 from the second episode of a series. Codex CLI calls are gathered in one place, image-director (S7). Calling from several agents breaks style consistency and leaks cost.
Security baseline S1–S8
Section titled “Security baseline S1–S8”| Code | Rule | Enforced at |
|---|---|---|
| S1 | Secrets (API keys, OAuth tokens) only in .env. .env.* not git-tracked | .gitignore |
| S2 | No modifying or deleting files outside _workspace/. Infrastructure only after human approval | agent definitions |
| S3 | Back up to .bak before overwriting an output. Preserve the prior version on rerun | video-editor, image-director |
| S4 | External URL downloads (yt-dlp) only for an explicit user URL. No automatic crawling | source-analyst |
| S5 | A source with no license label is refused for remix. Fair Use ≤30%, at least 3 transformation duties | license-policy L2 |
| S6 | Auto-detect real names, phone numbers, real addresses and recommend masking. No automatic masking | publish-copywriter |
| S7 | Codex CLI calls only by image-director. No simultaneous calls from several agents | image-director |
| S8 | Auto-publishing absolutely forbidden. After publish.md is made, the user uploads it themselves | publish-copywriter |
S5 and S7 are scene-studio’s own spots. S5 blocks copyright accidents, and S7 blocks image-style collapse and cost runaway, both at the code level. S8 is the spot that absolutely forbids auto-publishing on either track.
The next section is distribution. It covers where publish-copywriter makes only the publish metadata, the globalization policy, and why the platform upload is the user’s hand.