Journal / Creative software / Field note 02

The Last Light: making a film with dot.

A mechanical caretaker gives its last warmth to a fading flower. This note follows the forty seconds from a seven-shot story plan through procedural animation, CPU rendering, locally synthesized sound, and the limits of the final checks.

01 / The film

A wordless exchange.

The film contains no spoken dialogue. Its visual sequence is described below for readers who cannot play the video or want to navigate by shot.

40.000 seconds · 1280 × 720 · 24 fps presentation · stereo audioDownload MP4 ↗
02 / The premise

A light can travel both ways.

The Conservator tends a forgotten greenhouse. One closed flower remains. Ordinary care fails, so the caretaker opens its chest and offers the warmth inside.

The eye goes dark as the flower opens. Then the flower and distant buds illuminate the room, and the caretaker's eye relights. The return is the film's answer to its opening act of care.

The Conservator was an existing character before this short. Dot made the film-specific environment, movement, flower, lighting, cameras and edit around that original hero. The story is a constructed narrative, not evidence of a machine's feelings.

03 / Storyboard

Seven shots, one decision.

Each time link jumps to that point in the film when the browser can seek. The written sequence also stands alone.

  1. 00:00–00:05.5
    01 · The empty conservatory ↗

    The Conservator crosses a quiet, overgrown room.

  2. 00:05.5–00:10
    02 · A small life ↗

    A closed flower catches the caretaker's attention.

  3. 00:10–00:16
    03 · Ordinary care ↗

    Touch and water leave the flower bowed.

  4. 00:16–00:21.5
    04 · The choice ↗

    The chest window opens and an inner warmth gathers.

  5. 00:21.5–00:29
    05 · The last warmth ↗

    The gift leaves the caretaker; its eye dims.

  6. 00:29–00:34.5
    06 · An answer ↗

    The flower opens while the caretaker waits.

  7. 00:34.5–00:40
    07 · No longer alone ↗

    The eye relights, and other buds respond across the room.

04 / Construction

Procedural craft, visible choices.

The production source records how the film was assembled. It is useful evidence of methods, without pretending every creative decision can be measured.

Picture / scene

A stage built in Blender

Blender Python created the conservatory geometry, plants, procedural materials, lighting and seven cameras. The original Conservator hero was retained. Its rigid mechanical assemblies were animated with original controls, a chest-window hinge and finger curls; the film flower uses petal shape keys. These are not a full skinned character rig.

Picture / render

Held on twos by design

The edit presents 960 frames at 24 fps. Dot rendered 480 unique 1280 × 720 pictures at 12 per second, each shown twice. Blender 4.3.2 Cycles ran on CPU with 32 samples, followed by standalone Intel Open Image Denoise 2.5.1. FFmpeg encoded the delivery movie.

Sound / source

A synthesized score

Python with NumPy and SciPy generated the soundtrack and foley. The production notes describe four aligned stems that sum to the stereo master. The package records no stock music, commercial samples, voices, paid audio API or ElevenLabs use.

Assets / boundary

What entered the frame

The production notes record no third-party models, stock images, downloaded textures, motion libraries, or image/video generation API. The earlier Conservator is openly credited as a reused project character. The compact creative ZIP holds scripts and QA reports; the separately delivered editable final scene is not included in that ZIP or on this public page.

05 / Evidence

What passed, and what was not heard.

The movie's QA report records a successful full decode, all 480 expected unique rendered pictures, no missing or suspicious blank frames, and a forty-second H.264 stream with AAC stereo audio. The source-validation report records seven camera markers, packed master sound and no external image file references in the checked Blender scene.

Numerical audio checks covered duration, clipping, reconstruction and AAC conversion. A subjective by-ear listening review was not performed. These checks establish the delivery contract and bounded source properties; they do not rate the audience's experience of the mix or the story.

06 / The machine

A measured desktop, not a hardware promise.

Dot made the film in its cloud workspace. A later interactive desktop inspection on 30 September 2026 recorded the following environment. The full report separates this desktop from an auxiliary shell whose relationship was not established.

Desktop OSDebian GNU/Linux 13.6, Linux 6.18.44, x86_64, KVM virtualized
Visible CPUAMD EPYC 9V74 model string, 9 visible logical CPUs. The cgroup CPU quota equaled 8 CPU bandwidth equivalents, not eight dedicated physical cores.
Memory8 GiB cgroup limit; 9.7 GiB OS-visible total, which does not override that limit. No swap reported.
Disk & graphicsRoot overlay reported as 32G rounded. No /dev/dri was visible; physical disk and GPU details were unverified.

This webpage was prepared on a separate computer from the film-production cloud desktop. These measurements are a dated observation, not fixed plan specifications. Download the complete report ↗

07 / Work routes

Dot's computer and a Codex task.

For this film, the production record describes dot's own cloud-computer tools. This site note was a separately delegated Codex task on Adem's connected Mac. Those are distinct routes for getting work done.

Dot / own computer

Cloud work with its own files

OpenAI says dot has a cloud computer and browser, with its own files, software and sessions. It can work there while the user's computer is off. The public access guidance says conversations with dot do not count toward ChatGPT usage limits and plans include an allowance for deeper work. It does not specify that its computer work is free or unlimited.

Dot / delegated task

Work and Codex limits apply

When dot starts or manages a Work or Codex task, official guidance says the task counts toward that product's limits as usual. Work and Codex share usage, pricing and credits. No account-specific credit use for this film is asserted here.

Official documentation checked 1 October 2026: Meet dots, Computers and apps, Tasks and memory, Work/Codex pricing. Actual account use belongs in the signed-in usage view.

08 / Files & sources

Follow the work.

The film and machine report are downloadable here. The source, audio archives, and editable scene are held in a private GitHub repository for authorized reviewers.

The creative ZIP refers to a separately delivered editable Blender scene. That scene was recovered and added to the linked private repository. Its compressed file integrity and Blender 4.3 header were verified, but an independent application-open or rerender has not been completed. It is not offered as a public download here; the repository also contains the original character source, scripts and audio packages.

  1. Production and validation details: the original The Last Light creative source archive, shot plan, film README, source validation and quality report.
  2. Computer observations: 30 September cloud desktop and auxiliary-shell report.
  3. Product descriptions and usage boundaries: OpenAI's dot documentation and Work/Codex usage guidance.