Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

free-studio-flow

AI-native film factory and Studio flows on ProDocuX contracts.

License: Apache-2.0. See LICENSE.

Source version in this branch: 0.1.0rc3.

Latest verified PyPI release: 0.1.0rc2, published from tag v0.1.0rc2 at commit f53631d.

python -m pip install "free-studio-flow==0.1.0rc2"

Repository: github.com/freestudioflow/free-studio-flow. This tree is the FSF product. Machine-readable PDX freeze and pin records live under compatibility/. It does not ship the B-roll generator; that remains b-roll-library-generator.

Runtime pins: prodocux==0.3.0rc7, pdx-artifact-engine==0.3.0a8, pdx-adapter-media==0.2.0a3.

What this checkout contains

  • FSF-M1–M4 Spine: Word intake, execution plan compiler, authoritative resume invalidation, media conformance verification, and multi-executor abstraction
  • Plan Execution Runtime (fsf execute): Topological DAG execution engine for pdx_execution_plan_v1 plans, orchestrating tool steps, transform steps, and fail-closed QC conformance checks
  • Fast Assembly: Multi-shot video concatenation with external background music (BGM) mixing, embedded voice audio track mixing (amix), and subtitle policies (none, sidecar, burned)
  • Process Command Executor (process_cmd): Process adapter executing local CLI and script commands with isolated temporary output files, secret sanitization and atomic publication
  • FSF-S Skills: Fourteen Studio skills as CLI/skill (kaggle / api / local transports). No Studio desk in this release
  • Live Gate: Kaggle API ping + private job envelope + published PyPI pins + local transport shape. Live local-model ping is skipped when this machine has no useful Comfy/GPU. GPU kernel submit is opt-in (FSF_KAGGLE_SUBMIT=1) and off by default. Extra API/local/process backends: fsf-executors.example.json

Install

Python 3.11+.

python -m venv .venv
.venv/Scripts/python -m pip install -U pip
.venv/Scripts/python -m pip install -e ".[dev]"
.venv/Scripts/python -m fsf.cli check

Unix: .venv/bin/python instead of .venv/Scripts/python. Do not activate the venv and then use a bare python or fsf from PATH.

Verify

Same command for Cursor, Codex, Antigravity, and operators. See AGENTS.md.

.venv/Scripts/python scripts/agent_verify.py

That runs public hygiene, offline pytest, then live Kaggle/API pytest, then .venv/Scripts/python -m fsf.cli live-check.
Kaggle credentials: KAGGLE_CONFIG_DIR or ~/.kaggle/kaggle.json. The key is never printed. Missing credentials fail the live gate; do not skip.

.venv/Scripts/python -m fsf.cli run defaults to mock.studio.video (writes .mock.bin, not media). flow run requires --transport and --shape and refuses mock executors. Built-in kaggle/api/local shape adapters write .shape.bin; configured process adapters used by fsf execute can produce real media. verify on those files is expected to fail.

Vendor API / extra backends: put tokens in process environment variables only (FSF_VENDOR_API_KEY, or the key_env name in fsf-executors.json). Do not put secrets in JSON, git, or AGENTS.local.md. FSF does not load .env. See docs/FSF_LIVE_VERIFY.md.

CLI

Windows paths below; Unix: .venv/bin/python.

.venv/Scripts/python -m fsf.cli check
.venv/Scripts/python -m fsf.cli flows
.venv/Scripts/python -m fsf.cli intake path/to/sheet.docx --out output/job
.venv/Scripts/python -m fsf.cli plan path/to/sheet.docx --pipeline p0
.venv/Scripts/python -m fsf.cli plan path/to/sheet.docx --pipeline custom --skills storyboard,generate,dub
.venv/Scripts/python -m fsf.cli plan path/to/sheet.docx --pipeline p1 --media --assembly --bgm path/to/bgm.wav --out output/plan.json
.venv/Scripts/python -m fsf.cli execute output/plan.json --out output/execute
.venv/Scripts/python -m fsf.cli flow run studio.video.generate path/to/sheet.docx --transport kaggle --shape
.venv/Scripts/python -m fsf.cli run path/to/sheet.docx --executor mock.studio.video
.venv/Scripts/python -m fsf.cli verify path/to/clip.mp4
.venv/Scripts/python -m fsf.cli live-check
  • plan: Compiles the execution plan (pdx_execution_plan_v1). Supports --media (real media routing) or --shape (contract stubs), plus --assembly, --subtitles, and --bgm.
  • execute: Orchestrates the compiled plan DAG end-to-end, executing steps, assembly transforms, and QC conformance gates with authoritative resume support.
  • run: Single-step video generation runner (defaults to mock.studio.video writing .mock.bin).
  • flow run: Single Studio skill runner across kaggle/api/local transports (shape-only).
  • Full sequence: AGENTS.md.

Docs

Metadata

Release files for free-studio-flow 0.1.0rc3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for free-studio-flow 0.1.0rc3
File Size Uploaded
free_studio_flow-0.1.0rc3.tar.gz 123.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for free-studio-flow 0.1.0rc3
File Interpreter ABI Platform
free_studio_flow-0.1.0rc3-py3-none-any.whl Python 3 none any Details

Total release size: 204.7 kB

Release files / free_studio_flow-0.1.0rc3.tar.gz

Download URL free_studio_flow-0.1.0rc3.tar.gz
Size 123.5 kB
Tags Source
SHA-256 checksum
How to use checksums
98b2e89590aad57584af531af682fd6c4985b310294fe1bf2ac1efc2c8e972f9
BLAKE2b-256 checksum
How to use checksums
d05ee6b9b236e6b819e79e1189130d738f64397228ba46873057a5fea4ab6041
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.

Transparency log

Release files / free_studio_flow-0.1.0rc3-py3-none-any.whl

Download URL free_studio_flow-0.1.0rc3-py3-none-any.whl
Size 81.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e070ffbc2caf1b78fa1fb07408311f1d65f77f01ce86d72f7d0bab71c9506ab5
BLAKE2b-256 checksum
How to use checksums
f7e3ae355306b10590fcadda814fe6d091aac8d334f49852efc1e2705a681f40
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page