CREATIVEPRODUCTION OS
Prototype

Prototype · For small creative studios

From product brief
to reviewed launch video.

A local workspace for short product-launch videos. Keep references, shot instructions, revision history, generation costs and asset provenance connected from brief to assembled cut.

Explore the walkthrough Hosted product walkthrough.
Production runs in the local app.
Brief→Plan→Generate→Review→Deliver
Creative Production OS / Prototype

01 / The mechanism, in plain sight

Your brief becomes a plan.
Your selected takes become a cut.

Follow the inputs and outputs below. References, shot context and production records stay connected along the way.

  1. 01

    Brief

    FROM / Your idea

    A clear production brief

    Audience, duration, format and budget.

  2. 02

    Plan

    FROM / The brief

    A shot-by-shot plan

    Script, references and camera instructions.

  3. 03

    Generate

    FROM / Planned shots

    Media candidates

    Configured providers, estimates and job records.

  4. 04

    Review

    FROM / The candidates

    Selected takes

    Compare results and record continuity decisions.

  5. 05

    Deliver

    FROM / Selected media

    A cut + source manifest

    Assemble video and keep its production history.

Carried through the projectReferencesShot contextJob & cost recordsAsset provenance

02 / See the decisions, not just the promise

One product film.
A connected production.

Illustrative walkthrough
Original diagrams show how a project is organized. These are not generated takes or a customer result.

SHOT 01 / PLANNED FRAME
01

Establish the silhouette

Wide composition. Hold the shape against the dark world.

SHOT 02 / PLANNED FRAME
02

Show the material

Close framing. Preserve the geometry and surface finish.

SHOT 03 / PLANNED FRAME
03

Reveal the product

Hero composition. Match the reference before selecting a take.

REFERENCE → SHOT INSTRUCTIONS → CANDIDATES → REVIEW → CUT

When a take drifts, compare it with the reference and record a decision before carrying it forward. This example has no generated candidates, recorded production spend or completed export. End-to-end output quality remains unverified.

03 / Control the expensive decisions

Know the route.
Before the request runs.

Use the provider and model that fit the job. Local execution depends on installed capabilities; paid generation depends on configuration, estimates and budget limits.

THE REQUEST

A planned shot.
A defined capability.

Modality + references + model preference

L

Local route

When installed tools support the task.

Capability first
P

Configured paid provider

Selected provider, model and known estimate.

Budget checked
!

No eligible route?

Unknown pricing or a hard-budget breach stops routing.

Visible stop
YOUR DECISION

Choose the provider policy.

Use one provider, an allowed set, or an exact model preference.

YOUR BOUNDARY

Set the budget.

Routing uses project limits and per-job confirmation thresholds.

YOUR RESPONSIBILITY

Judge the actual output.

A completed job still needs creative review. Consistency is not guaranteed by generation.

04 / A deliverable with a history

Keep the cut.
Keep the context.

Export the assembled media and its manifest. Return to the shots, provider records and assets behind the result when you need to revise or audit it.

Build your first production
DELIVERY DOSSIERIllustrative structure
▶
production.mp4Assembled from selected video assets
MEDIA
≡
production.manifest.jsonMachine-readable production record
CONTEXT
Creative structure
Scenes, shots & characters
Generation history
Providers, models & jobs
Asset trail
Sources, hashes & licenses
Recorded spend
Production cost records

Source and license records support review; they do not replace a rights check.

Prototype / Integration status

A creative workspace.
Human decisions stay central.

Creative Production OS is being developed for small studios making short product-launch videos. The local prototype connects planning, provider jobs, review and assembly. Paid-provider output quality and customer adoption remain unverified.

CLAUDE INTEGRATION PLANNED

Planning adapter implemented.

The server-side adapter has fixture tests; live Claude API verification and workspace UI integration are pending. The hosted walkthrough does not call Claude.

INTENDED CLAUDE ROLE

Plan, instruct and revise.

Convert briefs into structured shot plans; later produce provider-specific instructions, interpret feedback and assist review of supplied frames.

EXPLICIT LIMITS

Review the actual media.

Claude is not the video renderer. Frame assistance cannot certify a whole video, guarantee continuity or clear rights. People approve plans and paid media generation.

Hosted walkthrough / Local prototype

Explore the workflow.
Production stays local.

This website explains the prototype. It does not create or store projects. The application requires Node.js, local SQLite storage and system FFmpeg for video assembly, with separately configured generation providers.

No hosted project storageNo API keys requested hereNo generation from this page
View the illustrative walkthrough ↗

The diagrams explain a planned product-launch workflow. They are not a completed production or customer case study.

Creative Production OS / Business contact

Talk about your production workflow.

founder@shotcut.biz ↗

Business website: shotcut.biz ↗

A prototype for small creative studios. Claude integration and evaluation are planned; the hosted walkthrough does not call Claude.

Recorded engineering evidence / Not business traction

What was checked.
What it does not prove.

2026-10-07 · RECORDED VERIFICATION

Local project entry, persistence and retry

One project after replay; persisted after restart; failure retained input and released button; creation recorded zero jobs and zero cost.

Windows loopback Next.js / SQLite; Chromium · Source b59a74d

Method: Browser double-click, refresh, server restart, same-ID replay and stopped-server retry; startup-entry.test.ts

Limits: Recorded local verification, not hosted project storage, customer usage or media-quality acceptance.

Safe evidence summary ↗
2026-10-07 · RECORDED VERIFICATION

Structured Claude planning adapter — fixture verification only

11 entry/boundary/planning tests passed. Synthetic plan and usage persisted; repeated request did not call provider twice.

Vitest, mocked first-party API response; no network API usage · Source b59a74d

Method: startup-entry.test.ts: schema, approval/cost limits, replay, usage ledger, bounded response and sanitized failures

Limits: Not live Claude integration or verified provider pricing. Workspace UI integration remains planned; no paid call.

Safe evidence summary ↗

No verified product-launch export or paid-production manifest published. Illustrative dossier is not export evidence. These checks do not establish customers, revenue, autonomous operation or programme eligibility.