Skip to content
Fluxx

Capture to Delivery Workflow

Retired 2026-09-24 (ledger A12, the second pass). This page walked five primitives and two finishing tracks under names since retired; its prior body is kept whole at 02_Working/Archive/Wiki_pre_second_pass_2026_09/process/capture-to-delivery.md. What follows is the current chain, from 02_Working/CLI_Briefs/THE_FRAME.md §1, 02_Working/Strategy/Company_Overview/FLUXX_DESCRIPTION_2026_09.md and 00_Canon/Q-G/Q-G31 as rewritten 2026-09-23. The present tense is the chain as designed; the description §4 says what is proven when.

The chain in one line

Build the world once; shoot real actors in front of it; keep the record; see the shot on the floor in minutes; finish from the record, at full quality, in the cloud. That whole chain is the product. Not the capture, not the tracker, not the interface. The chain.

Before the shoot: build the world, do not preview it

The scene package is built once, like a set, and approved before the first take: geometry aligned to the surveyed stage, lit to match the practical light, the compositing script prepared. It runs the week before the shoot, aligned with the prelight week. See Viz Cascade.

On the stage: the record

Real actors, real set, real light, the environment on the wall for the light and the reference, never the finished picture. The collector, the unit on the cart, listens to every device on the set: the camera through the capture card, the lens, the tracker that knows where the camera is and its verifier, the clock. When the camera rolls it opens the take on its first trigger; when the camera cuts it closes one complete record of the take, camera pose, lens, timing, the state of every source, with one verdict on whether the data can be trusted, and writes the temporary footage beside it, a ProRes plate for every take. A silent tracker or a wrong clock is a red light on the truck panel at nine in the morning, while it can still be fixed. The reference recorder on the stage is the safety and the reference record, checked against, never depended on.

The identifier is production-defined at setup and locked; the product ships with no hierarchy of its own. The take lands on the stage store as one immutable directory closed by one rename.

Minutes after the cut: the floor render

The watcher indexes the take, Fluxx Automate pairs it to its scene package by the production’s own identifier, and the stage render node renders it at half or quarter resolution, so the director sees the shot with its world around the actors and decides there, with the set and the crew still in place: go again, or move on. Nothing is locked in the camera. See On-Set Operations.

Then: finishing from the record

An agent reads every take’s verdict, the raises and the render’s own log and flags what a person should look at; nothing blocks. Which takes go forward is decided by the show, from the script supervisor’s notes, the calls made at the monitor, the reference recorder’s marks, the supervisors’ updates, and once it exists the edit, which is the authority. A selected take gets its full-quality footage, a 2K version and the finished render in the cloud, with no time constraint, and the deliverable replaces the placeholder in the edit without the edit ever waiting. Files are truth; the database is a view. See Cloud-Side Operations and Two Finishing Tracks.

After the day: refinement, not reinvention

Colour and the final polish happen against a foundation rendered from the record. A change to the world behind the actors, its time of day, its weather, a building that should not be there, is made in the finishing without shooting again. The performance is what is locked, which is what the director came to get.

What is deterministic and what is agentic

Opening and closing the take, the verdict, the offload, the pairing and the renders are deterministic automation on the record. The checking of renders is agentic: an agent writes a flag and a reason, and nothing blocks. Automation only works on correct data; without the record it is a person pointing at things faster. That is why collection comes first, and why the record is what ships first.

Cross-references

Audience visibility

industry, vendor, production, sales, director, investor.