FrameoAI · #FutureVisionXPRIZE Entry

Breathless

When a space disaster threatens Earth with suffocation, a grieving ex-stuntman must pilot through a chaotic debris storm where navigation systems fail, rescuing his estranged daughter before time runs out.

2026 · 3 min · 16:9 · Seedance 2.5 · Nano Banana Pro · Frameo Studio

03:00runtime
5days to make
0frames filmed

The ProjectOverview

The film

Breathless is a near-future rescue thriller about a grieving ex-stuntman who flies into a debris storm no machine can navigate. His mission is to bring back the daughter who stopped speaking to him. The spectacle is the arena and the film is the relationship.

Beneath the high-concept surface it is not about scarcity of oxygen. It is about the suffocating weight of unspoken words between a father and a daughter — built for the audience to watch and revisit their fractured relationships.

The story

The world. The air is toxic all over the world. Engineer Mei Lau builds Atlas — an orbital network that breaks toxic molecules down to raw atoms and reconstructs them as pure oxygen. Her father is Kai, a former stuntman who failed to save her mother during a fatal accident years ago. They haven’t spoken since.

The choice. Kai retrieves the Atlas core. Meanwhile, Mei’s transponder dies in the dark. With eight billion lives at stake, Command orders him to abort the mission and come home.

The dive. He cuts comms and goes deeper. An impact strikes and fries his kinetic suit. Flying blind on muscle memory and a promise to keep up, he manages to find her, frozen in her suit, right before his oxygen level hits zero.

The rebirth. Shielding Mei with his own armor, Kai slams the core into the backup transmitter before passing out. The pulse clears the sky. He wakes in orbital medical to Mei at his bedside, taking his hand — the promise kept.

The world

Two machines hold the world together. Atlas is the planetary lung: an orbital network that continually strips toxic air to raw atoms and rebuilds it as breathable air. The Aero-Kinetic Exo-Suit is Kai’s companion in the storm: a high-tech suit whose neural array absorbs kinetic shock, regulates life support, and feeds sub-second hazard mapping straight into the pilot’s senses. When the storm outruns every algorithm, the suit supplies the data and the armor — Kai supplies the reflexes. That synergy is the premise. Man and machine in lockstep.

The characters

Kai Lau — the father. Aged 50, former stunt performer, living in self-imposed isolation since the breach that killed his wife. The only human whose reflexes qualify for the suit. His arc: a broken father becomes the storm’s equal.

Mei Lau — the daughter. In her 30s, chief orbital engineer. She built Atlas so no one would ever watch a loved one choke again. Her contribution to protect humanity is the same one that keeps her far from her father.

Director Amanda — the calculus. Head of UN Global Command. Not a villain, but a pragmatist who weighs one life against eight billion and orders the abandonment. Her cold calculations are exactly what Kai’s devotion defies.

The motif

One behavioral gesture tracks the whole relationship — the thirty-second breath count.

  • Past. Kai times ten-year-old Mei holding her breath in the backyard. It ends in laughter and a promise.
  • Crisis. Adrift and alone, Mei counts to thirty to stay calm as her life support plummets.
  • Climax. Kai holds his last breath for thirty seconds to dock the core home.
  • Resolution. Mei takes his hand as he exhales his first clean breath.
Kai kneels with ten-year-old Mei in a backyard — the breath-count promise
Scene one of the motif — the backyard breath count, and the promise

The brief

Breathless directly reframes a planetary crisis into a celebration of human-machine synergy. Instead of presenting artificial intelligence or orbital engineering as cold, destructive threats, the film highlights Atlas (an atmospheric reconstruction network) and the Aero-Kinetic Exo-Suit as triumphs of engineering that empower human devotion, physical reflex, and emotional reconciliation. By pairing hard orbital mechanics with an optimistic core, Breathless demonstrates that technology gives our deepest human values the armor and reach necessary to safeguard our shared future.

The numbers

The film runs 3 minutes. It was made in five days by a crew of five. Every character, location, and prop was locked as a still asset before a single shot moved. Nothing was filmed.

The crew

Five people, end to end. One wrote the story. One carried the entire pre-production and production — assets, prompts, generation. Three finished the film in post: an editor, a supervising eye over the cut, and one pair of hands on sound and music.

The main problem

Inconsistency: keeping complex objects exact across every shot. The exo-suit’s armor plates might morph slightly between angles, Kai’s face might change under different lighting setups, or the zero-gravity physics can occasionally glitch. Everything that follows in this document is the answer to that one problem.

The ultimate storyboard

  • Instant pre-visualization. Instead of spending millions of dollars and months on rough 3D animation, you can test complex camera movements, space debris speed, and lighting setups in five days.
  • A turn-key blueprint. It acts as a moving blueprint that shows studio executives, cinematographers, and VFX crews exactly what the final movie will look like before building a single physical set.

The greatest distance isn’t space. It’s the silence.

The disaster is the arena — the film is a father fighting through ten years of grief to keep a childhood promise.


01Assetsstills first
02Prompts30-sec scene chunks
03GenerationSeedance 2.5
04EditQC every take
05Postgrade + mix

Assets & WorldPre-Production

What an asset is

An asset is a dual-locked unit of consistency: a precise text prompt paired directly with a high-resolution visual reference image (e.g., Kai’s suit model turnaround, Mei’s facial reference, or the Atlas core architecture). In an AI-assisted storyboard workflow, an asset acts as the visual single source of truth. It defines the exact geometry, texture, lighting response, and physical boundaries of an object or character before any video generation begins.

Nothing enters a shot without a pre-defined asset pair — generative AI models naturally drift, morph suit details, or distort facial features between camera cuts. By forcing every single prop, suit component, character face, and environment element through a pre-anchored asset key, we lock down visual continuity across all shots. This eliminates model hallucination, guarantees character recognition across chaotic high-G sequences, and keeps the storyboard production-ready.

Character sheets

Every character is locked as a three-panel sheet — full-body front, full-body back, close-up — on neutral grey, so the model learns the person, not a lighting accident. The face lives in the close-up; wardrobe and silhouette live in the fulls.

The two timelines never share a sheet. Young Kai and present-day Kai are separate assets, as are young and present-day Mei — so the past cannot leak into the present, and a memory scene cannot age a face by mistake.

Naming, states, versions

Every asset carries a stable identity, and scenes reference identities — not descriptions. When an asset needs a variant — damage, a wardrobe state, a different lighting register — the variant becomes its own versioned asset rather than a prose adjustment. In other words, if two prompts share the same name, they must mean exactly the same thing — no name can refer to two slightly different meanings. The exact convention is part of the studio’s internal system; the rule it enforces is public: reference, don’t describe.

Locations

Locations are locked as plates, one per world register — orbit, command, the Earth surface, the past. A scene inherits its geography from the plate: the model is handed the place as pixels, so it cannot re-imagine the architecture between cuts. Interiors that matter to the story — like the pod, the ship — are plates too, not improvisations.

Look & color

Everything was visualized before a single video was generated. The look and feel of every scene was locked as stills in Frameo, exactly per the vision — desaturated ambers and claustrophobic haze on the Earth surface, cyan and obsidian for the technology, strobe-lit darkness in the debris storm, warm light in the past. Only when a frame looked like the film did it become a reference for one.

The color arc is the emotional arc. The grade moves from suffocating grey-brown to saturated blue as the Atlas core re-engages — planetary and emotional rebirth in the same shift. The frames below are examples of the vision, achieved before the camera ever moved.

From still to scene

First the setting is visualized as a still, after which the scene is generated from it. Every animatic starts life as an approved frame — the setting, the light, the character — and the first motion is generated directly from that image. The pairs below show the workflow: the still that locked the vision, and the scene it produced.

Pair 01 · The orbital relay
The orbital relay station — truss, ring, and solar panels over Earth
The setting — visualized as a still
The scene — generated from it
Pair 02 · The hospital
The hospital room — bed by the window, monitors glowing
The setting — visualized as a still
The scene — generated from it
Pair 03 · The riverside
Kai seated at the riverside under an amber hazy sunset
The setting — visualized as a still
The scene — generated from it
Pair 04 · The backyard promise
Kai kneels with ten-year-old Mei in the backyard
The setting — visualized as a still
The scene — generated from it
Pair 05 · Mei in the Atlas chamber
Mei at the Atlas core console, lit by the orb
The setting — visualized as a still
The scene — generated from it
More animatics
Animatic 02
Animatic 05
Animatic 08

The Prompt SystemPre-Production

The prompt skeleton

Every scene is a chunk. Using Frameo’s Seedance 2.5 prompt-enhancer skill, each scene is authored as one self-contained 30-second chunk prompt, cut into timecoded beats: a tag map binding numbered reference images to specific cuts, a format lock, camera moves called by name, and per-asset craft fields — subject, lighting, composition, storytelling. The skill is pipeline-aware: it reads the live episode state, knows which approved assets exist, and writes prompts that reference them by ID instead of describing them from memory.

The discipline is patch, not re-brief. When a shot fails, its chunk is edited and re-rendered, so a failure costs one prompt, and the rest of the film never hears about it.

The anatomy of a scene prompt

The full text of a production prompt is the studio’s working capital, so it stays in the vault. Its shape does not. Every chunk in the film follows the anatomy below:

Scene prompt — anatomyProprietary
Tag map@image1 — Cut 1
@image2 — Cut 2
@image3 — Cut 3
Format lockEXACTLY 30 SECONDS · 16:9 · AUDIO ON
Cut 1 · 0.0–3.0s
Cut 2 · 3.0–6.5s
Cut n · 27.5–30.0s
Cameraorbit · whip · dive · pull
Craft fieldssubject · lighting · composition
Audiobreath · SFX · score
Authored by Frameo’s Seedance 2.5 prompt-enhancer skill — one chunk per scene

Optics & camera

Camera moves are called by name, never described. The prompt vocabulary is a fixed set of named moves — orbit, decelerating orbit, whip, dive, pull, full-speed rush — each written with its motivation in the cut. Framings come from a searched preset library (full shot, close-up, and their kin), not from improvised adjectives. A move the vocabulary doesn’t name doesn’t go in a prompt.

Geography & continuity

Continuity is carried by the references, not by prose. Every cut is pinned to approved stills through the tag map, so the model inherits geography from images that already agree with each other instead of re-imagining the set each time. The assets — not the adjectives — hold the world together. A shot cannot drift from a place that is handed to it as pixels.


PerformanceDirection

Behavior, not feelings

Performance is never written using vague emotion adjectives like “terrified,” “grieving,” or “heroic.” Instead, acting is broken down into concrete, observable behavior chains — the exact physical actions, micro-expressions, and body mechanics a camera can actually capture. Panic isn’t prompt-written as “Kai is scared”; it is written as Kai’s knuckles whitening around the control stick, his pupils dilating against the HUD glare, and rapid, shallow breaths fogging the inside of his visor glass.

Writing performance as physical behavior prevents generic output. By anchoring shots to observable steps — a trembling finger tapping an air valve, a sudden drop of the shoulders, or eyes locking onto a dying battery counter — the storyboard maintains subtle, human performances that translate directly to a real actor’s mark on set.

Physics, not adjectives

Movement is specified as physics — weight, contact, momentum, recovery. In zero gravity that discipline is survival: a body that drifts must keep drifting until something stops it, and the prompt says what stops it. Adjectives animate nothing; forces do.

Signs of a living shot

  • The eyes lead. A living character looks before they move; a dead one moves first.
  • Weight exists. Bodies settle, tethers pull taut, impacts cost momentum — nothing glides for free.
  • Something breathes. Idle is never frozen: breath, micro-shifts, fabric — stillness with a pulse.

Sound & MusicDirection

The score contrasts organic sounds with electronic ones. Cello and soft woodwinds reflect Kai’s grief and vulnerability, while deep bass, synth pulses, and metallic percussion represent Atlas, the void, and the danger of debris in orbit. The music starts sparse and broken, builds into fast, chaotic rhythms during the storm, and ends with a full orchestral release as the sky reboots.

Sound design also works through contrast. Inside the helmet, we hear heartbeats, breathing against the visor, and the hiss of life-support systems. Outside the suit, there is complete silence.

The key sound is the Atlas thrum — a deep rhythmic pulse that feels like the artificial heartbeat of the planet.


ProductionGeneration

Organization & the log

The chunk was the basic unit of production. The film was built as a numbered set of chunk files, one for each scene. Changes were made through logged patches, with new takes added to each slot. Every save was timestamped and tracked, so nothing was lost in the conversation.

The toughest shots were rewritten multiple times, and the log recorded every change.

Fixes that saved generations

  • Patch the chunk, not the conversation. When a take failed, we edited the relevant chunk and rendered it again — no need to explain the whole scene from scratch.
  • QC before acceptance. Every render went through key-frame checks and a fixed review for characters, continuity, and sound before being approved.
  • Complaints become records. Model failures were logged as quality reports, along with a suggested fix, so the same problem was not repeated.
  • Dead turns lose nothing. If a turn stopped midway, it could simply be run again, because the work was stored in the state tree, not the chat.

Laws instead of requests

Rules became laws when scenes repeatedly failed without them.

01The format lock. Every chunk was exactly 30 seconds, 16:9, with audio on.
02The reference law. Every shot was tied to approved reference stills through a tag map, preventing faces or locations from changing.
03The identity law. Assets were referenced by identity rather than described again, reducing visual drift.
04The vocabulary law. Camera moves came from a fixed vocabulary. If a move was not defined, it was not used.
05The QC law. No take was accepted without key-frame checks and a full video-and-audio review.

The edit in parallel

Editing happened alongside generation in the same workflow. Renders went through ffmpeg for conforming and grading, while key frames were checked against approved references. Each take was also reviewed for picture and sound before the next chunk was written. This meant problems could be fixed while the shot was still fresh, instead of being discovered days later during the final assembly.


Post-ProductionFinishing

The final assembly happens in a non-linear edit, with cuts shaped to match the fast pace of the action. Since AI-generated clips can vary in contrast, gamma, and color, every shot goes through a color-unification pass. From close visor shots to wide orbital sequences, everything is brought into one consistent look, with cyan tones in orbit and desaturated amber on Earth.

Sound plays a major role in making the film feel cinematic. Suit breathing, metallic debris impacts, and deep sub-bass pulses build tension, while sudden cuts to complete silence create the feeling of space. Combined with the acoustic-electronic score and scratch dialogue, the sound mix drives the pace and emotion of the film.

Post-production can fix smaller issues like frame flickering, color mismatches, pacing problems, and visual noise through masking and temporal smoothing. Strong sound design can also help give generated movement more weight and impact.

But post cannot fix everything. If a character’s face changes between shots, the suit design shifts dramatically, or the physics of a scene completely break down, no amount of color grading or sound design can solve it. Post can improve consistency, but it cannot fix broken visual continuity or spatial logic.


What We LearnedConclusion

Five rules shaped the entire film.

01Lock every asset. Never rely on a text prompt alone. Pair it with a fixed visual reference to maintain consistent faces, geometry, and technology.
02Lock the environment first. Establish the lighting, color palette, and camera language before building the shots. Without a stable environment, locations can change shape and scale between cuts.
03Prompt actions, not emotions. Instead of asking for someone to look “scared” or “grieving,” describe visible actions like a fogging visor, clenched fists, or dilating pupils.
04Use sound to create weight. AI-generated visuals can sometimes feel light or floaty. Sounds like gas vents, metallic impacts, and heavy breathing help give the action more physical presence.
05Plan with AI, keep the human performance real. Generative video can be used to quickly pre-visualize camera movement and action. But the physical performance, emotion, and human detail are best captured with real actors on set.

Every rule here exists because a scene failed without it.

Three minutes took five people and five days — and the same assets, chunks, and laws that shipped this film are the blueprint for the feature the treatment maps.


DeliverablesWhat's Included

Breathless is not a one-off render. The IP foundation already exists as production-ready artifacts — the film above is the proof, and these ship with it to any prospective partner.

PDF
Breathless — feature screenplay
110 pages · complete
ART
Visual key-art deck
Exo-suit · Relay 4 · storm lighting keys
3D
Animatic / previs reel
90-second 3D pre-visualization
PDF
Feature film treatment
This document's source · complete

The world beyond the film

One idea holds the franchise: who controls the air we breathe?

02Rogue Sky — clean air becomes currency. A rogue faction hijacks Atlas to ransom cities; Kai and Mei fly up together to retake the grid.
03New Genesis — Atlas goes to Mars. A massive solar storm forces a coordinated two-planet rescue.
+Spin-offs — The First Pilot (the reckless test flight that proved the suit) · The Black Market (oxygen crime before Atlas existed).
TVSeries — UN Command (live-action political thriller) · Atlas: Year Zero (animated prequel — young Mei races to build the first prototype).