Skip to main contentSkip to footer
ExamplescriptintermediateRunnableguided-flow

Sora Sequence

Runnable example (intermediate) for script using openai, pillow.

Key Facts

Level
intermediate
Runtime
Python • OpenAI API
Pattern
Inspectable flow with visible system boundaries
Interaction
Live sandbox • Script
Updated
14 March 2026

Navigate this example

High-level flow

How this example moves from input to execution and reviewable output
Sora Sequence -> Render the visible result -> video

Trigger

Sora Sequence

Runtime

Render the visible result

Outcome

video

Why this page exists

This example is shown as both real source code and a product-facing interaction pattern so learners can connect implementation, UX, and doctrine without leaving the library.

Visual flowReal sourceSandbox or walkthroughMCP access
How should this example be used in the platform?

Use the sandbox to understand the experience pattern first, then inspect the source to see how the product boundary, model boundary, and doctrine boundary are actually implemented.

UX pattern: Inspectable flow with visible system boundaries
Source references
Library entry
models-openai-08-video-6-sora-sequence
Source path
content/example-library/sources/models/openai/08-video/6-sora-sequence.py
Libraries
openai, pillow, pydantic, python-dotenv, requests
Runtime requirements
OPENAI_API_KEY
Related principles

6-sora-sequence.py

python
import os
import subprocess
import tempfile
import sys
from pathlib import Path


# --------------------------------------------------------------
# Find most recent sequence folder or use provided path
# --------------------------------------------------------------

# Check if a valid path was provided (not a Jupyter kernel argument)
if len(sys.argv) > 1 and not sys.argv[1].startswith("-"):
    sequence_path = Path(sys.argv[1])
else:
    folders = sorted(
        Path("./output").glob("sequence_*"), key=os.path.getmtime, reverse=True
    )
    if not folders:
        sys.exit("No sequence folders found. Run 5-sora-remix.py first!")
    sequence_path = folders[0]

# --------------------------------------------------------------
# Find shot videos
# --------------------------------------------------------------

video_paths = [str(f.resolve()) for f in sorted(sequence_path.glob("shot_*.mp4"))]
if not video_paths:
    sys.exit(f"No shot videos found in {sequence_path}")

print(f"Stitching {len(video_paths)} shots from {sequence_path.name}")

# --------------------------------------------------------------
# Create concat file and stitch
# --------------------------------------------------------------

with tempfile.NamedTemporaryFile(mode="w", suffix=".txt", delete=False) as f:
    f.write("\n".join(f"file '{path}'" for path in video_paths))
    temp_path = f.name

output_file = sequence_path / "sequence.mp4"

try:
    subprocess.run(
        [
            "ffmpeg",
            "-f",
            "concat",
            "-safe",
            "0",
            "-i",
            temp_path,
            "-c",
            "copy",
            str(output_file),
            "-y",
        ],
        check=True,
    )
    print(f"Done: {output_file}")
finally:
    os.unlink(temp_path)
What should the learner inspect in the code?

Look for the exact place where system scope is bounded: schema definitions, prompt framing, runtime configuration, and the call site that turns user intent into a concrete model or workflow action.

Look for output contracts and validation
Look for the exact execution call
Look for what the product could expose to the user
How does the sandbox relate to the source?

The sandbox should make the UX legible: what the user sees, what the system is deciding, and how the result becomes reviewable. The source then shows how that behavior is actually implemented.

Read the implementation summary.
Step through the user and system states.
Inspect the source code with the highlighted doctrine decisions in mind.
SandboxInspectable flow with visible system boundaries
Interaction walkthrough

Use the sandbox to step through the user-visible experience, the system work behind it, and the doctrine choice the example is making.

UX explanation

The sandbox explains what the user should see, what the system is doing, and where control or inspectability must remain explicit.

AI design explanation

The page turns raw source into a product-facing pattern: what the model is allowed to decide, what the product should expose, and where deterministic code or review should take over.

Interaction walkthrough

  1. 1Read the implementation summary.
  2. 2Step through the user and system states.
  3. 3Inspect the source code with the highlighted doctrine decisions in mind.

Visible to the user

A script demonstrating openai + pillow.

System work

The product prepares a bounded model or workflow task.

Why it matters

The interface should make the delegated task legible before automation happens.

Used in courses and paths

This example currently stands on its own in the library, but it still connects to the principle system and the broader example family.

Related principles

    Runtime architecture

    Use this example in your agents

    This example is also available through the blueprint’s agent-ready layer. Use the For agents page for the public MCP, deterministic exports, and Claude/Cursor setup.

    Define triggers, context, and boundaries before increasing autonomy
    Make control, observability, and recovery explicit in the runtime
    Choose the right operational patterns before delegating to workflows