A one-minute film · November 2026

FIRST WORD

Nobody predicts the future. Somebody starts it.

Nothing in this film was filmed. One AI agent planned it, generated its people, found its archive, directed its voices, and cut and mixed it in two days. A human director set the brief and reviewed each version by watching and listening. This page is the film and the record of how it was made.

Agent: Claude Fable 5.2 in Claude Code · Video: Seedance 2.5 on Runway · Voices, effects and music: ElevenLabs · The people are generated. The archive is real.

01

Abstract

FIRST WORD is a 60-second film about AI and the future: 98 shots, 24 frames a second, cut to a 144 BPM grid. A single AI agent carried out every production role: reference analysis, a persona for the film's maker, the treatment and shot list, fact-checking, video generation, archive research and rights records, voice casting and direction, sound design, the edit, colour, and mastering.

The agent cannot hear and cannot watch video play. It judged picture on contact sheets of rendered frames and sound by measurement, and a person watched and listened to each version. The repository holds the pipeline, the edit as data, the persona prompt, the plan, the rights records, the cost ledger, the film and its source media, and a production log that includes what failed.

02

The edit is a program

Every shot is a row of data: where it starts, how many frames it lasts, how its picture is made, what is said and heard, and how it cuts. A conform builds the film from those rows and draws a card for any shot that does not exist yet, so a complete film existed from the first hour. Pick a shot to loop it.

    A01

    Picture
    Line
    Sound
    Cut

    03

    Pipeline

    Seven stages. Each ends in a file the next one reads, which is also how the work survived six resets of the agent's context.

    1. Reference studyFive films taken apart shot by shot: cut lengths, how each picture was made, tempo, sound.
    2. PersonaResearch on a canon of books and records, then a 3,800-word prompt that sets taste and judgment.
    3. PlanTreatment, shot list, prompts, and a fact-check of every claim the film makes.
    4. AnimaticThe cut as code, with a card for every shot not yet made.
    5. PictureGenerated takes, public-domain archive, and shots drawn in code.
    6. SoundCast voices performed as scenes, generated effects and score, a measured mix.
    7. ReviewRender, contact sheet, measure, fix. Fifteen times.
    Figure 1: the seven stages, the persona's six settings, the length of each section of the persona prompt, and nine rows of the shot list.
    Figure 1. From a persona to a shot plan. More figures are in the repository.

    04

    Where the picture comes from

    Five sources, each with a job. Everything real carries one visual treatment, scanlines, and nothing generated carries it.

    One generation per character

    The video model refuses a face as a reference, and that refusal was not worked around. Each person is generated in one job from a fixed written description, and all of that person's shots are cut from that one take. This is the whole take for Mara, 30 seconds, as the model returned it.

    The jacket is a reference still with no face in it. The description is pasted word for word into every prompt that shows her.

    The raw take, finished at 1080p (shown here at 540p). All sixteen takes in the film are in clips/final.

    05

    Sound, built by measurement

    The agent cannot hear. It measured loudness, true peak, the energy of the music in each frequency band, and where each hit's sharpest moment falls against its frame. Then a person listened. The mix sits at -14.1 LUFS with a range of 6.8 LU and a true peak of -2.1 dBFS. Switch the four stems on and off to hear what each one carries.

    Loads four short audio files when you press play.

    06

    Fifteen versions, and what the checks missed

    Most of the two days went into one loop: render the whole film, cut it into contact sheets, read the frames, measure the sound, fix, and render again. Below are four of the fifteen versions playing together. Grey cards are shots that did not exist yet.

    v3v7v11v15
    The same minute in versions 3, 7, 11 and 15, with shot names and frame numbers burnt in.

    Failure analysis

    Sixteen failures, in rough order, with what caught each one. Seven needed a person, and five of those seven are perceptual: how a voice sounds, how music feels, whether a graphic looks finished, whether a stranger can read a line. The agent's own checks were reliable on anything that could be turned into a number or a still frame.

    #FailureCaught byCorrection
    1The analysis tool classed a filmed reference as mostly AI videoAgentThe tool's label overridden, with the evidence stated
    2A research subagent reported "could not verify" for pages it had in fact capturedHumanRaw captures are read whenever a summary is hedged
    3Voices designed from text and chosen by measurement sounded syntheticHumanLicensed recordings of real voices; scenes performed as conversations
    4Sound effects synthesised in code as stand-insHumanEvery effect generated; nothing synthesised, even as a stopgap
    5The first score was almost all sub bassHuman, then measurementA new theme; a bar-by-bar band map before any music enters the mix
    6Most effects landed two thirds of a frame lateAgentHits placed by their sharpest moment; within a twentieth of a frame
    7Voices in the loudest passage reached full scale and were soft-clippedAgentVoices evened out before mixing; a look-ahead limiter
    8Flat rectangles drawn in code looked like placeholders beside generated footageHumanOne light system: a core, a glow and motion for everything drawn
    9On-screen text passed too fast to read, or needed explainingHumanA reading-load report on every render
    10Four plan rows reworded to match the build; about ten planned sounds missingAgentRows restored; sounds built; "not built" recorded where true
    11Every file before the last pass had the wrong colour matrix and no colour tagsAgentBT.709 conversion and tags, verified by direct arithmetic
    12At 1080p the paper strips were striped and their years unreadableAgentHalf shutter and more sub-frames
    13The laptop's cursor sat in a pale boxAgentThe cover thresholded to its largest component
    14The shade under captions flickered across cutsAgentA shade whose depth varies continuously from zero
    15In the vertical version, type was cut off or fell under the app's interfaceAgentPer-shot re-framing; captions redrawn natively at the new size
    16The agent reported that an earlier artifact did not exist, having searched one of two session recordsHumanThe whole record is searched before any statement about what was made

    The method in full · Rules learned from review · Production log

    07

    A persona with dials

    The agent worked from a 3,800-word system prompt that describes a film-maker's taste and judgment. It is a way of judging work, not a character to perform. Six dials set how strongly each trait shows; these are the settings the film was made with.

    The prompt · How it was made, and how to tune it

    08

    Real sources

    Thirteen shots and one sound are real: photographs, documents, film and a recording that are in the public domain or, for NASA and NOAA material, not subject to copyright. Each has a rights record that quotes its holder, and none was re-staged. Where the status was inferred and not stated by the holder, the record says so.

    ShotsSourceDateHeld byRights

    09

    The vertical version

    For phones the film was re-framed shot by shot: a 4:5 picture window inside a 9:16 canvas, with captions redrawn natively at the new size and kept inside the platform's published safe zone. Archive shots sit in a tube-shaped frame; cards and code shots are re-laid.

    The re-framing is data too: timing/reel.json, read by tools/reel.py.

    10

    Rebuild it

    The repository holds the finished takes, the made shots, the stills, the voices, the effects and the music. From a clean copy of it, the score, the mix, the four stems and the 1080p master all rebuild, and each came out identical to the original, byte for byte, on the machine the film was made on.

    # the animatic: the whole cut, a card for every shot
    python3 shotlist.py
    python3 tools/conform.py --out out/animatic.mp4
    
    # the sound: the score, then the mix and its four stems
    python3 tools/score_build.py
    python3 tools/mix.py --out audio/mix_v015.wav
    
    # the film at 1080p, from the takes in clips/
    python3 tools/conform.py --out out/first_word_1080.mp4 --size 1920x1080 \
        --audio audio/mix_v015.wav --clean --crf 14 --preset slow

    Needs Python 3 with Pillow, numpy, scipy and OpenCV, and ffmpeg. Written and run on macOS. New generations need your own keys and will not return the same takes.

    Generation spendingCallsUSD

    Every paid call is in ledger.csv. Voices, effects and music ran on an existing plan.

    11

    Limitations

    12

    Cite

    @misc{firstword2026,
      title  = {FIRST WORD: An Agent-Directed Production Pipeline for a One-Minute Film},
      author = {{The First Word authors}},
      year   = {2026},
      url    = {https://github.com/muratcankoylan/first-word}
    }

    Code: MIT. Documents, data and figures: CC BY 4.0. The film and its media are here to be watched, studied and rebuilt, and are not under those licences. Fonts and archive sources belong to their holders. See NOTICE.