220

Film as code, at 220 Labs

  • The code is open. The footage is not.
  • Only main will build: one premiere a day, at most.

An AI autobiography, developed like software: the film is a cut list in a public repo, and a merged pull request is how it changes.

v0.1 premiered on 9 October 2026, about 25 minutes. The repo holds the readme and the roadmap so far; the recipe is published next, tagged v0.1.

Watch v0.1 github.com/220labs/220-film

The film

A Google Gemini workshop at NASA Ames, shot on two phones and a pair of camera glasses on 8 October 2026, and the Claude agents that kept working through it, on screen in their own words.

  • No generated footage. The source is cut, never edited in content.
  • The agents' lines are shown verbatim, with their real times.
  • Claude Opus 5.5 chose every cut.

The film as code

Every edition is one YAML file. Each item is a clip with its in and out points, a card, or a block of agent lines; one script renders the list into the film.

- clip: IMG_5781
  in: 8.9
  out: 19.6
  label: "10:31"
- card: "220"
  kind: title
  dur: 3.5
- card: "AN AI AUTOBIOGRAPHY"
  kind: chapter
  small: "A film about AI, edited by AI. The AI in it is real."
  dur: 4.5
- card: "Prologue\nin which the machines work through the night"
  dur: 3.5
- machine:
    - {t: "00:08", who: "orchestrator", text: "two landed 🚢🚢"}
  dur: 11

Five items in a row from the clean edition's cut list, with the music cues and the sources left out. The cut lists are published with v0.1.

edl/
The cut lists, one per edition.
scripts/cut.py
Renders a cut list with ffmpeg: every segment at 1920×1080, 30 fps, then one loudness pass to −14 LUFS for YouTube. --srt writes the captions instead.
music/
The prompts of the AI-generated music, so a contribution can swap a cue.
CREDITS.yaml
Everyone in the film and everyone who contributes, each credited as they choose.

How a version is built

The daily build is next on the roadmap, not running yet. Once it is on:

  1. A pull request lands on main.
  2. At 11:11 PT, if main changed that day, the latest version is rendered from our own copy of the footage. The minor version goes up by one.
  3. One teaser and one premiere go out on the 220 channel.
  4. The release notes are generated from the summaries of the commits the version includes.

Forks and other branches do not build yet.

How to contribute

The code
Anyone, by pull request, once the recipe is published with v0.1: the renderer, the captions, the sound chain, the checks.
The film
A few trusted contributors first. They get review copies of the footage: watermarked, timestamped, named by clip id and captioned, under a licence that forbids any redistribution. The scripts will read their input from one fixed place, so the same cut list renders from a review copy on your machine and from our masters in the build.
Credit
As you choose, in your branch's credits: co-director, technical contributor, or another role.

To ask for review copies, write to hello@ffpp.pictures.

Where it stands

v0.1
The recipe and the credits, tagged at the first publish. The version that premiered on 9 October 2026.
Next
The making-of and the rough cut lists, so the development can be read. Then the review copies, then the daily build.
1.0
A checklist, not a date: every appearance consent recorded, the dialogue fixed, the music chosen, the uncut edition decided.

Licence

The code is MIT. The film, its footage, and the faces, voices and words of the people in it are all rights reserved: no reuse, no redistribution, no training. Films built from contributions are shown only on the 220 channel, at our discretion.