# Pushing Squares_ — full content # Don't Build Brands. Build the Universe Your Brand Lives In. // Pushing Squares_ URL: https://pushingsquares.com/dont-build-brands Kind: doctrine Summary: Distribution is not marketing. Distribution is legacy. The format that earns a life is the format on the most machines. The doctrine behind why files travel and brands don't. Cite as: Don't Build Brands. Build the Universe Your Brand Lives In. // Pushing Squares_. Pushing Squares_. https://pushingsquares.com/dont-build-brands Doctrine: 01 ## HERO Doctrine_01 ## HOOK Distribution is not marketing. Distribution is legacy. PDF won. Not because it was the best document format. It won because it ended up on more devices than anything else. MP3 same story. JPEG same story. The format that earned a life was the format on the most machines. Not the most elegant. Not the most correct. The most installed. The work that lasts is the work that traveled. ## BRAND vs UNIVERSE A brand is the visible part. Logo, voice, palette, tagline. The badge. A universe is what hosts the brand. The platform people return to. The community they check before checking the news. The tool they open before opening their email. Without that substrate, your brand is a billboard. Billboards don't earn a life. They rent attention by the second. Universes ship files. The thing your audience holds in their hand or on their machine is the thing that earned the life. The brand is what they recognize. The universe is what they keep. ## THREE CARRIERS Every universe touches a device through one of three carriers. Platform. A place you re-enter. Re-entry is the metric. Not signups. Not MAU. Re-entry without prompting. Community. A room you check. The check-in rhythm is the metric. Daily, weekly, never. The community that earned a life is the one your audience opens before the news. Tool. A file format that travels. Devices holding the file is the metric. Not downloads. Devices. A universe with all three earns more life than any one alone. A universe with only one is fragile. A universe with none is a brand chasing attention. ## PRICING FLIP Once a universe has earned a life, the bill changes shape. You stop charging for the working. You charge for the artifacts the universe ships. The 2am sweat is private. The PDF, the framework, the protocol, the file you handed over. That's the bill. This isn't a positioning trick. It's the only honest way to price something that has earned a life. The market pays for what it can hold. It can hold the output. It can't hold the working. Charge the folder. The folder is what survives. ## CLOSER The most installed format wins. PDF. MP3. JPEG. The pattern repeats every decade. Don't build a brand. Build the universe your brand lives in. The brand is what they see. The universe is what they keep. The files your universe ships are what travel. The devices your files reach are the legacy. Make more files. Get them on more devices. That's the whole game. --- # The Agentic NLE // Pushing Squares_ URL: https://pushingsquares.com/agentic-nle Kind: doctrine Summary: The future of editing isn't AI replacing editors. It's AI accelerating them. So why does the industry keep building AI tools for tape-era NLEs instead of NLEs built for AI? Cite as: The Agentic NLE // Pushing Squares_. Pushing Squares_. https://pushingsquares.com/agentic-nle Doctrine: 02 ## HERO Doctrine_02 The future of editing isn't AI replacing editors. It's AI accelerating them. So why does the industry keep building AI tools for tape-era NLEs instead of NLEs built for AI? ## COLD OPEN An editor opens the workspace mid-project. Yesterday's first cut went out to the client at 6pm. The notes came back at 11pm. The review-agent read them, scored each for feasibility, and sent three interpretations of the structural changes through the assembler overnight. By morning they sit side by side in an A/B/C panel. Reaction shots already slotted into the silences as J-cuts and L-cuts. The timeline isn't a strip of horizontal tracks. It's a grid of scene blocks, because that's how this editor has been working for months, and the surface has shaped itself to match. Scopes sit tucked away. The performance grid is up. The editor scrubs the second pass, swaps a take in scene three for the backup the assembler flagged, marks one shot to feel colder, drags one frame six frames earlier on the master. The system makes a note. It won't make that mistake again. *02 — A/B/C revision panel · post-client feedback* ## DIAGNOSIS Look at any timeline today and you're looking at 1991. The track grid is a fossil. V1, V2, A1, A2, video one, video two, audio one, audio two, were the names of physical tape decks stacked on top of each other in an edit suite. The labels survived into the software. So did the geometry. So did the address. Hours, minutes, seconds, frames is the way you found your place on a reel that physically rotated past a playhead. Even the razor, the primary cutting tool, is a mechanical metaphor for a knife you used to slice celluloid. The source and record monitors are two boxes that represent two real machines, one that played the take, one that recorded the cut. *07 — frame-level escape hatch · 1991 track grid* None of this is wrong. It was correct for the medium it was designed in. Tape was linear, physical, expensive to re-record, and an editor's job was to choose the right pieces and place them in time. The track grid mapped that work cleanly onto a screen. Then the medium changed. Footage became file-based. Cuts became free. The job changed too. Editors moved from selection-and-placement into orchestration of dialogue, pacing, performance, colour, sound, story. The medium got bigger. The interface stayed the same. Every AI feature shipped into editing software since then is a renovation of one room in this house. Auto silence-cut tools automate the razor: same mechanical move, faster. Magic-mask roto automates matte tracking: same keyer, but the keyer no longer needs you to draw the spline. Auto-transcribe-edit treats spoken text as a clip you can slice and rearrange, but the clip still lands on the same track at the same address. Generative b-roll fills the media bin with synthetic footage you didn't shoot, but the bin is the same bin and the clips drop onto the same V2. Smart reframe rebuilds the crop tool. Scene detect rebuilds the cataloguer. Auto-colour-match rebuilds the matching shot. Each one is a useful renovation. None of them touch the floor plan. The ceiling shows up the moment you try to give the software a goal. Tighten this dialogue. Build to a fast crescendo. Make scene one feel nostalgic and warm and scene two feel sterile and cold. These aren't track-level instructions. They're directorial instructions. They reach across colour and pacing and audio and structure at once, which is what direction does. To run them, the AI has to translate the instruction down into a hundred track-level operations: shorten this clip on V1, slot a reaction on V2, swing a curve on the colour node, lift the sub on the music stem. The instruction lands. The orchestration is gone. What an editor reads off the timeline afterwards is not the directorial choice. It's the renovation list. This is the cap. Goal-oriented AI does not fit on a track grid because the track grid is not the language of cinema. It is the language of one craft inside cinema, plumbed through a substrate from a previous era. As long as the substrate stays the same, the AI features layered on top of it can only get more precise about their renovations. None of them will move the house. ## VISION — STORYLINE Start the house over. The primary unit isn't a clip on a track. It's a scene block. A scene block is a region of the story, not a region of the timeline. It holds whatever clips, audio, masks, and decisions belong to that beat: interview setup, action sequence A, the reaction, the resolution. The block knows what it is. The editor names it and the system tags it. The micro-cuts inside a block are handled by an agent that understands pacing and intent. The editor stays at the block layer for most of the work and drops below it only when something specific needs hand-work. Above the blocks sits the workspace itself, and the workspace is the interface. Not a fixed surface with panels in fixed places. A mutable surface that reshapes around what the editor is doing. A/B panels when two cuts need comparing. A storyline view when story is the unit. A performance grid when one actor's beats are the unit. A colour bay when the grade is up. The surface knows what the editor is working on and rearranges to put the right tools in front. And the workspace evolves with the editor. The frames that get hand-corrected, the takes that get swapped, the masks that get redrawn over and over become signal. The system learns this editor likes reactions held a beat longer. This editor prefers a slightly cooler key on dialogue scenes. This editor wants the assembler to cut to the wide before the reaction, not after. The next session opens sharper than the last. The longer the editor uses it, the more the tool becomes theirs. Same engine, completely different feel per user. The way the best agentic tools already work in other crafts. The track grid does not vanish. It survives as an escape hatch. When something needs to be done frame-accurate, by hand, with no abstraction in the way, the editor breaks through. The virtual razor is still there. So is the timecode. So are the tracks. The difference is they're no longer the surface you start at. They're the surface you fall through to when the abstraction can't reach what you want to change. This is the swap. Operator-level controls hide under director-level interaction. Cinema's working vocabulary moves above the tape-era vocabulary. The tape-era vocabulary stays available, but it stops being the front door. *01 — storyline view · default state* *03 — performance grid · take selection* *04 — colour bay · grading suite* ## VISION — AGENT CREW Inside this workspace, the work gets done by a crew. The first member is the DIT-assistant, the agent that meets the footage at ingest. Point it at a folder of raw takes and it builds proxies, syncs multicam, aligns sound, transcribes the lot. It also tags. Not just speech to text but camera move, lighting condition, lens, depth, an emotional read on the performance. It scores usability and bubbles the circle takes to the top, marks the soft-focus ones for review, files the obvious throwaways out of sight. The editor never opens a clip bin to hunt for a take. The crew has already laid them out in the order the script implies. The Narrative Assembler builds the assembly. Feed it a script, a storyboard, or a beat sheet, and it walks the tagged footage block by block, choosing takes that match intent and sequencing them at a pace the story asks for. It understands cinematic rhythm: when to hold a wide, when to cut to the reaction, when to use a J-cut to let dialogue overlap the next beat, when to let an L-cut carry the previous shot's audio into the new image. Ask for three versions of a scene at different paces and it returns three, each editable in the same surface, not a separate timeline. Compare, pick the spine, work from there. The VFX and gap-filling agent does the work that used to require a node tree and a tracking pass. The editor highlights a distracting logo on a shirt and asks for it gone. The agent tracks, masks, paints, holds the integrity of the shot across the cut. When the script calls for a wide of a neon-lit street and the rushes don't include one, the agent runs a generative video model in the background and proposes options the editor can audition and place. The b-roll is style-matched to the surrounding footage on grain, colour, and lens behaviour before it lands in the timeline. The intervention is reversible at any point. The Audio and Foley agent does what a sound designer would, in the rhythm the picture asks for. It separates dialogue, music, and effects into clean stems on its own. It generates the room tone that should be there but wasn't captured. It builds footsteps that match the surface someone is walking on, fabric movement that matches what they're wearing, wind that matches the wide shot of the cliff. It scores under the cut, swelling and falling on the beats the editor has chosen, not on the bar lines of a library track. The mix is rough by default but the structure is there from the assembly onwards. The Finishing and Color agent grades for story, not for match. A directorial note becomes a per-block grade: make scene one feel nostalgic and warm, scene two sterile and cold, and the system propagates the choice across every shot in those blocks. Because the system holds depth information from the rushes, it can relight as well as grade: shift a key light in post, recover a face that was underexposed, hold continuity across takes shot hours apart in different daylight. The grade is reversible to source. Nothing is baked. *05 — crew dispatch panel · agent states* Five specialists. None of them the editor. All of them reporting to the editor. The work that used to take five different application suites and five different file handoffs runs as a single crew on a single surface, and the editor stays in the chair the whole time. ## PAYOFF What the editor does with the time the crew gives back is the point. The numbers tell the story before the argument does. Roughly two-thirds of an editor's working day today goes to sync, ingest, conform, the find-the-take grind, the masking that has to be done by hand because no software understands what the shot is about. Take that work away and the day rebalances. The recovered hours land on choice. Which version, which performance, which rhythm, which tone. The shift is from operator to director. The iteration loop is where this lands hardest. Review a cut, name what's wrong: the pacing in the middle drags, the colour is too saturated, the reaction at minute three needs to land harder. The system recalculates. A new pass plays back inside the same surface. The cycle is seconds, not days, and the editor is making directorial choices in every cycle, not technical ones. Client feedback is where this lands second-hardest. The notes come in. The review-agent reads them alongside the cut and scores each one for feasibility. This one is a one-frame swap. This one needs a take that wasn't shot. This one is ambiguous and could go three ways. By the time the editor opens the workspace, the obvious changes are already proposed. The ambiguous ones come back with three candidate interpretations sitting in an A/B/C panel, each one a working pass the editor can scrub and choose between. The editor reads the notes once, picks the spine, refines what needs refining, and the revision goes back the same morning. The revision cycle that used to take days runs in hours. *06 — review-agent inbox · parsed client notes* The track grid does not disappear and the editor does not become a manager. The escape hatch matters. When a specific frame needs to be six frames earlier, when a specific mask needs to be hand-drawn, when the system's choice is wrong, the editor breaks through. The work happens at the level the work needs to happen at. The difference is that the editor chooses that level. The substrate doesn't impose it from below. When the editor does break through, the system watches. The frames that get manually adjusted, the masks that get manually redrawn, the takes that get manually swapped become training data for the next pass. Not training data in a model-fine-tuning sense. Training data in a stylistic sense. This editor likes to hold reactions a beat longer than the assembler proposes. This editor prefers a slightly cooler colour pass than the assembler suggested. The system learns the editor, not the medium. Over time, the assembler stops needing to be corrected on the same thing. The first time an editor works inside a system like this, the most surprising part is what they stop doing. The hour spent finding the right take of the right line, gone. The hour spent matting out the wrong logo, gone. The two hours spent syncing audio to picture across four cameras, gone. What replaces them is not less work. It's more of the work the editor wanted to be doing the whole time. Read this way, what looks like automation is the opposite. It's the recovery of judgement time. The editor is doing more of the work that is editing: taste, rhythm, intention, story. And less of the work that was a side effect of how the substrate was built. The role doesn't shrink. It concentrates. Call it what it is. The editor becomes an edit orchestrator. Crew below, surface around, judgment in the chair. ## CLOSE The components exist. Goal-oriented language models exist. Specialist agents exist. Generative video, generative audio, depth-aware grading, scene-level tagging. All of it ships in something today, somewhere in the stack. What doesn't exist yet is the integrator that thinks like an editor and gets out of the editor's way. Someone is going to ship it. The question is who, and the question is when, and the question is whether editors get to shape what gets built or whether it gets built around them. A good NLE is the most patient instrument an editor ever holds. It waits. The next good NLE will do more than wait. It will collaborate, on terms an editor can recognise as theirs. That tool isn't here yet. So. Who's building it? --- # The Director's Pass // Pushing Squares_ URL: https://pushingsquares.com/art-direct Kind: doctrine Summary: Stop prompting. Start directing. A prompt is a wish thrown into the dark. A direction is a reaction to what is already on the screen. Direction is a loop, not a one-shot. Cite as: The Director's Pass // Pushing Squares_. Pushing Squares_. https://pushingsquares.com/art-direct Doctrine: 03 ## HERO // the correction gesture Doctrine_03 A prompt is a wish thrown into the dark. A direction is a reaction to what is already on the screen. ## TWO-ZONE // notes gutter + sticky Stage The eye is the engine. The loop is the work. This is the first pass. Undirected. It is not wrong. It is just unmade. A prompt stops here and hopes. A director does not stop here. A director looks, and says one word. Watch the right. One move at a time. Each note keeps the last. _ ## MOVEMENT 03 // THE EYE — type-as-image apex The eye is the rare part. Anyone can write the wish. Few can look at what came back and say the one word that fixes it. ## MOVEMENT 04 // WHO DIRECTS The differentiator was never the prompt. It was the eye, and the willingness to react to what came back. Direction is a loop, not a one-shot. You do not describe the result and pray. You look, you say warmer, and the screen answers. Then you look again. That loop is the work // ## CLOSE // bookend Stop prompting. Start directing_ --- # The Creative Orchestrator // Pushing Squares_ URL: https://pushingsquares.com/creative-orchestrator Kind: doctrine Summary: Same taste. New instrument. The creative director didn't disappear. It split in two, and only one half learned to conduct. Cite as: The Creative Orchestrator // Pushing Squares_. Pushing Squares_. https://pushingsquares.com/creative-orchestrator Doctrine: 04 ## HERO // ascii role morph (plays on load) Doctrine_04 Same taste. New instrument. The creative director didn't disappear. It split in two, and only one half learned to conduct. ## MOVEMENTS For a hundred years, “creative director” meant one thing. Taste, judgment, and the brief, applied to a team of people. That job is becoming two jobs. One branch keeps directing people. The photographer, the editor, the designer. Nothing wrong with it. It is the craft as it always was. The other branch directs a system. The taste is identical. The judgment is identical. But the instrument is no longer a room of specialists. It is a workflow that can produce the work as fast as you can say precisely what you want. The two branches share a spine and almost nothing else. In a few years they will not be able to do each other's work. People assume the machine comes for the taste first. It is the opposite. Taste is the last thing to automate, because it was never the typing. It was the deciding. What survives, unchanged, on the orchestrator's side: the eye (knowing what “right” looks like before anyone has made it); the brief (defining the target so it can actually be hit); the final no (taste is mostly the power to reject). The eye is the differentiator. It always was. The machine just made that obvious by taking everything that wasn't the eye. Everything downstream of the decision. Stop prompting. Start defining outcomes. A prompt is a wish thrown into the dark. An outcome is a thing you can hold the result up against and say “closer,” or “no.” The whole craft moves from asking to defining, and then to judging. Which turns the work into a loop: Define the outcome // Conduct the system // Judge the result // Redefine. You stop making the work by hand. You start conducting it. The skill isn't the keystroke. It's the precision of the definition and the speed of the judgment. So here is the seat, plainly. A creative orchestrator is a creative director whose instrument is a system instead of a staff. Keeps: the eye, the brief, the judgment, the final no. Drops: making every frame by hand. Adds: defining outcomes precisely enough that a system can hit them, then conducting that system to the result. Delivers: not the asset. The defined outcome, met. It is not a prompter with a fancy title. Prompting is throwing wishes. Orchestrating is running the loop. Most teams have not hired for this, because until now it had no name in the org chart. It has one now. ## CLOSE // bookend Same taste. New instrument. If that lands, we should talk. _ --- # The Output // Pushing Squares_ URL: https://pushingsquares.com/the-output Kind: doctrine Summary: Output isn't what you ship. It's what you push forward. Cite as: The Output // Pushing Squares_. Pushing Squares_. https://pushingsquares.com/the-output Doctrine: 05 ## HERO Doctrine_05 Output isn't what you ship. It's what you push forward. ## MOVEMENT 01 // THE BATON For decades the strongest tool in the room did the hardest work with its own hands. The best model wrote the best code. That was the whole idea. Spend the good intelligence on the hard lines. That is over. The strongest model stops writing the code. It starts conducting the ones that do. It sits above the work, not inside it, and points: this piece to that model, that piece to another, all of them running at once. The best intelligence you have is too expensive to spend on typing. So it stops typing. It picks up a baton. This isn't a faster typist. It's a conductor. And on the far side of that baton, the change is yours. You stop making the work by hand. You start directing a fleet that makes it. That is the lift. Not more speed at the keys. A different seat entirely. The typing leaves the chair. The judgement stays. ## MOVEMENT 02 // THE RECEIPT One week, held honestly. A receipt that rounds up is not a receipt. Zero posts published. Under that flat surface, 715 commits landed. Not all of them are glory. Roughly 328 are feature work, 61 are tests, 50 are fixes, and about 135 are chore commits, most of them the fleet keeping its own books. The rest are merges and config. The real floor of new capability sits nearer 440. The count does not round up. Behind those commits, roughly 640 background jobs started. Some retried. Some failed at boot. Some got sent back. 640 is jobs begun, not jobs that landed. Starts aren't wins. The gap is the engine breathing, not the engine failing. Naming it plainly is the point. And inside that same week, one model went from one out of five on a hard ordering task to five out of five. Not because anyone fixed it. Because it taught itself. Could not do the thing on Monday. Could by Friday. That skill is permanent now. That is output no feed will ever show. A phone photo editor booted for the first time. A desk cockpit shed a two-second lag on every keystroke. An 8,943-line depth pipeline merged clean. Local image generation came online. The publishing machine itself, the thing that will one day ship the posts, got torn down and rebuilt underneath as a compiled browser engine. Zero posts. The walls moved a row over. This isn't a flex. It's a receipt. Stop counting posts. Start counting squares pushed. ## MOVEMENT 03 // HOW YOU FLY The mechanism is the part you can take. The harness is Claude Code. On top of it, UltraCode fans a single model into dozens, each copy working in its own parallel worktree. Many hands, one instrument, all playing at once. Not a queue. A section. Above them sits the conductor: the strongest model, Fable. It does not play. It plans the task, splits it into pieces, and routes each piece to the cheapest model that can hold it. Prose to Claude. The build to Codex. The long cheap grind to GLM. Vision to MiniMax. Every lane runs a different model pushing a different square. None of this is a private trick. The harness is public. The fan is public. The routing is a file you could write tonight. So picture your own fleet. One seat that decides. A dozen cheap seats that do. The work stops being what you can type before you sleep. It becomes what your routing can push while you do. That is how you fly it too _ ## MOVEMENT 04 // THE ROUTING IS THE MOAT The strong model is not the ceiling. The conductor is swappable. Put the same conducting seat on GLM and a cheap coder and the grid still moves. Not because Fable is weak. Because Fable was simply the first model strong enough to prove that the conducting was the thing all along. Once you can see the conducting, you can hand the baton to cheaper hands. That is the whole inversion. The expensive model's real job is to make itself optional. It writes the routing, proves the routing, then steps aside while cheaper models run inside it. The conducting becomes a file. The file becomes a line in a budget. The line goes down. The intelligence isn't the model. It's the routing. The tokens are a line item. Which means your output is not bounded by the model you can afford. It is bounded by the routing you can build. The model is a hiring decision. The routing is the company. Any single model, even the strong one, is a budget question. The routing is the moat. ## MOVEMENT 05 // MEASURE WHAT MOVED So measure the right thing. Everyone watches the posts. The posts are the last five percent. The publishing gate opens later, and when it opens the posts come fast, because most of what's behind them is already built. But the gate was never the work. The work was the ninety-five percent nobody watched. The engine is the output. The posts are a valve on it. Measure the commits, counted honestly, chores called out and starts kept separate from wins. Measure the capabilities unlocked. Measure the walls moved a row over. Measure the routing getting denser, the conductor getting cheaper, the fleet getting louder. A square is the smallest unit of forward motion. A commit. A capability. A wall moved a row. Output is the squares that moved since yesterday, whether or not a single one of them showed its face. ## CLOSE Output isn't what you ship. It's what you push forward. Stop counting posts. Start counting squares pushed _ // --- # The feature delivery stack URL: https://pushingsquares.com/the-feature-delivery-stack Kind: outreach-qualm Summary: Dailies through DI, mix, and multi-territory deliverables still sprawl late. IMF and DCP versions pile up across suites on every feature. Cite as: The feature delivery stack. Pushing Squares_. https://pushingsquares.com/the-feature-delivery-stack Dailies through DI, mix, and multi-territory deliverables still sprawl late. IMF and DCP versions pile up across suites on every feature. ## The feature delivery stack On a feature, the path runs from dailies through DI and mix into multi-territory delivery. Late IMF and DCP versions still sprawl across suites. Conform bridges pile up. Delivery stacks fork. The version that ships is the one someone chased down by hand at the end of the week. That is the cost of the feature delivery stack as it stands. Evidence: [Ministry of Ungentlemanly Warfare, project page](https://goldcrestfilms.com/films/the-ministry-of-ungentlemanly-warfare/) ## How Pushing Frames_ fits Pushing Frames_ sits inside DaVinci. It captures the conform, routes grade notes, and turns overnight delivery versioning into one surface you can act on. --- # The HDR version spread URL: https://pushingsquares.com/the-hdr-version-spread Kind: outreach-qualm Summary: HDR and Atmos finishing for broadcast and SVOD still costs half a day. Conforms and platform versions sprawl on every show. Cite as: The HDR version spread. Pushing Squares_. https://pushingsquares.com/the-hdr-version-spread HDR and Atmos finishing for broadcast and SVOD still costs half a day. Conforms and platform versions sprawl on every show. ## The HDR version spread HDR and Atmos finishing for broadcast and SVOD still costs half a day. Conforms and platform versions sprawl on every show. Each deliverable path forks the grade, the mix, and the QC queue. Hybrid remote-edit keeps the edit moving. The version map does not. Hours leak into the spread between masters. Evidence: [Louis Theroux: Inside the Manosphere, finishing credit](https://fiftyfiftypost.com/work-project/louis-theroux-inside-the-manosphere/) ## How Pushing Frames_ fits Pushing Frames_ sits inside DaVinci. It holds conform and version state so platform spreads stop eating half a day per show. --- # The dual-site handoff URL: https://pushingsquares.com/the-dual-site-handoff Kind: outreach-qualm Summary: Shoreditch and Old Street handoffs leave late online and grade notes split across two buildings. Cite as: The dual-site handoff. Pushing Squares_. https://pushingsquares.com/the-dual-site-handoff Shoreditch and Old Street handoffs leave work split. Scripted and unscripted sound paths diverge. Late online and grade notes land across two buildings. ## The dual-site handoff Shoreditch and Old Street handoffs leave work split. Scripted and unscripted sound paths diverge. Late online and grade notes land across two buildings. Picture lands in one room. Notes land in another. The handoff is real work. Not a status line. Dual-site houses pay for that gap on every job that crosses the street overnight. Evidence: [Enola Holmes 3, sound post production](https://splicepost.com/work/scripted/enola-holmes-3) ## How Pushing Frames_ fits Pushing Frames_ sits inside DaVinci. It captures the conform and routes grade notes so a dual-site handoff is one surface, not two inboxes. --- # The pipeline tool gap URL: https://pushingsquares.com/the-pipeline-tool-gap Kind: outreach-qualm Summary: Multi-genre work keeps conform bridges and QC queues busy. Pipeline tooling still trails the load. Cite as: The pipeline tool gap. Pushing Squares_. https://pushingsquares.com/the-pipeline-tool-gap Multi-genre drama, doc, film, and game work keeps conform bridges and QC queues busy. Pipeline tooling still trails the load. ## The pipeline tool gap Multi-genre drama, doc, film, and game work keeps conform bridges and QC queues busy. Pipeline tooling still trails the load. The craft is there. The bridges between suites are where hours go. When the queue outruns the tools, senior time becomes the glue. Glue does not scale across concurrent titles. Evidence: [About, post technology and creative technology roles](https://molinare.co.uk/about/) ## How Pushing Frames_ fits Pushing Frames_ sits inside DaVinci. It is one concrete fix for the conform and note path while broader pipeline tooling catches up. --- # The render and review cycle URL: https://pushingsquares.com/the-render-review-cycle Kind: outreach-qualm Summary: High-volume commercial VFX work still leaks hours. Render queues and review rounds stack on every project. Cite as: The render and review cycle. Pushing Squares_. https://pushingsquares.com/the-render-review-cycle High-volume commercial VFX work still leaks hours. Render queues and review rounds stack on every project. ## The render and review cycle High-volume commercial VFX work still leaks hours. Render queues and review rounds stack on every project. A note lands. A re-render waits. The next round starts from a version that is already half a day behind. Concurrent brand work multiplies the cycle until the calendar is the bottleneck, not the craft. Evidence: [Google Pixel, Made for the Beautiful Chaos](https://www.time-based-arts.com/cases/google-pixel-made-for-the-beautiful-chaos) ## How Pushing Frames_ fits Pushing Frames_ sits inside DaVinci. It captures grade notes and version state so review rounds stop waiting on a half-day re-render loop. --- # The remote grade handoff URL: https://pushingsquares.com/the-remote-grade-handoff Kind: outreach-qualm Summary: Remote grade and VFX notes between London and New York still eat a half-day. Every overnight project pays for the water crossing. Cite as: The remote grade handoff. Pushing Squares_. https://pushingsquares.com/the-remote-grade-handoff Remote grade and VFX notes between London and New York still eat a half-day. Every overnight project pays for the water crossing. ## The remote grade handoff Remote grade and VFX notes between London and New York still eat a half-day. Every overnight project pays for the water crossing. Conform, grade notes, and retouch maps arrive the next morning. Someone rebuilds the state. A half-day per project, every project. That is the cost of the overnight handoff as it stands. Evidence: [O2 Online Network, VFX and colour case](https://freefolk.com/work/online-network/) ## How Pushing Frames_ fits Pushing Frames_ sits inside DaVinci. It captures the conform, routes grade notes, and turns the overnight handoff into one surface. --- # The multi-client status deck URL: https://pushingsquares.com/the-multi-client-status-deck Kind: outreach-qualm Summary: Concurrent multi-brand work still burns senior time. Weekly status decks and asset version chaos stack across client, creative, and production. Cite as: The multi-client status deck. Pushing Squares_. https://pushingsquares.com/the-multi-client-status-deck Concurrent multi-brand work still burns senior time. Weekly status decks and asset version chaos stack across client, creative, and production. ## The multi-client status deck Concurrent multi-brand work still burns senior time. Weekly status decks and asset version chaos stack across client, creative, and production. Each brand wants a clean picture. Each deck is rebuilt by hand. The work is real. The friction is the assembly of status, not the craft inside the frames. Evidence: [Wilkinson Sword, campaign case](https://www.pablolondon.com/work/wilkinson-sword) ## How Pushing Frames_ fits Pushing Frames_ sits inside DaVinci for the post path. For the wider status map, a Scan names where senior hours actually go. And what is worth fixing first. --- # The global asset versioning URL: https://pushingsquares.com/the-global-asset-versioning Kind: outreach-qualm Summary: Global multi-market campaigns still scatter brief intake. Asset versions fork across territories, producers, and creative services. Cite as: The global asset versioning. Pushing Squares_. https://pushingsquares.com/the-global-asset-versioning Global multi-market campaigns still scatter brief intake. Asset versions fork across territories, producers, and creative services. ## The global asset versioning Global multi-market campaigns still scatter brief intake. Asset versions fork across territories, producers, and creative services. The master leaves London. The market cut returns with three names and no single source of truth. Version chaos is not a craft failure. It is the shape of multi-territory delivery without a shared surface. Evidence: [Carlsberg, The Danish Way](https://fold7.com/work/carlsberg-the-danish-way) ## How Pushing Frames_ fits Pushing Frames_ sits inside DaVinci for the finishing path. A Scan maps where brief intake and asset versions actually fork, market by market. --- # The client and creative review loop URL: https://pushingsquares.com/the-client-creative-review-loop Kind: outreach-qualm Summary: Purpose campaigns still scatter feedback. Client, legal, and craft rounds stack until the review loop eats the week. Cite as: The client and creative review loop. Pushing Squares_. https://pushingsquares.com/the-client-creative-review-loop Purpose campaigns still scatter feedback. Client, legal, and craft rounds stack until the review loop eats the week. ## The client and creative review loop Purpose campaigns still scatter feedback. Client, legal, and craft rounds stack until the review loop eats the week. Each round is legitimate. Stacked together, the loop becomes the job. Notes arrive out of sequence. Versions fork. The film that ships is the one that survived the loop. Not the one that was clearest on day one. Evidence: [Greenpeace International, SLAPP Suit](https://www.dontpaniclondon.com/work/greenpeace-international-slapp-suit/) ## How Pushing Frames_ fits Pushing Frames_ sits inside DaVinci for the grade and note path. A Scan names where the review loop actually burns the calendar. And what is worth fixing first. --- # The multi-suite stem spread URL: https://pushingsquares.com/the-multi-suite-stem-spread Kind: outreach-qualm Summary: Six-suite commercial sound work still multiplies stem handoffs. Late mix versions and delivery-spec sprawl hit concurrent agency jobs. Cite as: The multi-suite stem spread. Pushing Squares_. https://pushingsquares.com/the-multi-suite-stem-spread Six-suite commercial sound work still multiplies stem handoffs. Late mix versions and delivery-spec sprawl hit concurrent agency jobs. ## The multi-suite stem spread Six-suite commercial sound work still multiplies stem handoffs. Late mix versions and delivery-spec sprawl hit concurrent agency jobs. Stems leave one room. Notes return to another. Specs shift mid-job. The mix that lands is the one someone reconciled by hand. Concurrent agency volume makes the spread structural, not occasional. Evidence: [FIFA World Cup 2026, BBC Creative spot](https://factory.uk.com/projects/fifa-world-cup-2026-lets-make-it-iconic/) ## How Pushing Frames_ fits Pushing Frames_ sits inside the picture path in DaVinci. A Scan maps the stem and mix version surface across suites. That is where commercial sound volume actually leaks hours. ---