Skip to content
Fluxx

Whitepapers

Fluxx’s whitepaper streams: the Near-Time VFX whitepaper (v0.1, canonical thesis as of S125), the Pipeline Architecture Whitepaper (v0.1, technical companion), the Operating System Around the Wall thread (v2 → v3 → v4, archived historical per S125), and the in-progress “Cost of Filmmaking” whitepaper (Phase 1, S139 — the cost-claim research base). The relationship between the first three was the “two-whitepapers question,” resolved at S125 (below).

Each whitepaper has a distinct purpose, distinct audience, and distinct framing posture. They are not lockstep versions of the same document; they are independent canonical bodies.

Operating System Around the Wall (v4 archived, superseded by Near-Time v0.1 per S125)

One-sentence pitch. Fluxx is the operating system around the wall, made deployable: a single, production-owned workflow from camera sensor to final composite that fixes the structural mismatch where virtual production is priced like a stage, sold like a technology, and operated like a production system.

Structure (8-section argument essay).

  1. Our purpose (S46 add). VFX is broken in ways the industry cannot fix from inside. Billing model depends on the waste it creates; technology floor is shifting under everyone at once. Fluxx is the path through both. (Note: this reproduces the retired Q-G19 “VFX-fixer” purpose framing, superseded by Q-G57 on 2026-05-04 — Fluxx is the new-category creator, not a VFX-fixer. Preserved here as the archived OS v4 wording.)
  2. The wall is not the business model. Govaere named the missing operating model from the outside in April 2026; Fluxx had finalized the same architecture from the inside the same week. The whitepaper specifies the working model, not the technology.
  3. What’s actually broken. Three failures sharing one root cause. Billing model (vendor margin depends on keeping non-creative artists on the timesheet). Real-time claim (physics doesn’t support cinema-quality rendering in the camera’s 20ms exposure window). Vendor handoff (production loses control of its own pipeline at wrap). Root cause: nobody owns the operating model.
  4. What the working model actually is (six pieces). Production owns the pipeline. Infrastructure travels. Fit profile is narrow on purpose (workflow shape, not budget tier). Cost structure separates stage cost from infrastructure cost. The 50-artist reality is the economic core. The system has a system of record (provenance for EU AI Act).
  5. Why it works now and not five years ago. USD open standards settled; cloud compute rentable by the hour; sustained studio cost pressure; consolidation of production-tracking tools into Autodesk / Backlight / Adobe creating an independence neighborhood.
  6. Where the model does not work. Genuine misfit is comp-only 2D shows. Three “fits with friction” categories: sub-$5M productions; productions where late creative iteration is the central method; producers who prefer outsourced pipeline ownership.
  7. What we are asking investors to read. Technology side is solved; business side is not. Industry has converged on the question over the last twelve months; Fluxx is one specific working answer. Demo 2 (June 2026) is the first end-to-end test under production conditions.

Audience. Production-operator reader (investor and partnership distribution under NDA). Sibling to the Company Overview, not derivative of it.

Framing posture. “Operating system around the wall” (Govaere’s phrasing, retained verbatim in v4 because Govaere is preserved as cited authority in this document). Argument-essay register. Govaere positioned as peer-level voice arriving at the same conclusion from the outside.

Status. Shipped 2026-04-28. v4 supersedes v3. Archived as historical snapshot at S125 (2026-05-20) when Near-Time v0.1 was locked as the canonical thesis document per Kevin’s S125 review (see “Two-whitepapers question resolved” section below). The April 2026 OS v4 NDA-distributed copies remain valid for reference and for audiences already in the Govaere-converging conversation, but Near-Time v0.1 is the canonical thesis document going forward. Tracked in Notion Current Versions database.

Files.

  • 02_Working/Strategy/Whitepaper/Fluxx_Whitepaper_Operating_System_DRAFT_v4.md (current source)
  • 02_Working/Strategy/Whitepaper/Fluxx_Whitepaper_Operating_System_DRAFT_v4.pdf (PDF)
  • 02_Working/Strategy/Whitepaper/Fluxx_Whitepaper_Operating_System_DRAFT_v3.md (historical)
  • 02_Working/Strategy/Whitepaper/Fluxx_Whitepaper_Operating_System_DRAFT_v2.md (historical)

Near-Time VFX (v0.1) — canonical thesis document as of S125

Title. “The Two Pipelines and the Bill That Doesn’t Add Up.” Kevin-authored, about 10-page argument essay.

Structure.

  1. Why this paper exists. Productions run two pipelines simultaneously for one finished picture.
  2. Where the VFX dollar goes. The 50-of-450 reality, the taxi-cab analogy, the $3-5K-per-shot setup floor, the structural trap.
  3. Where the VP dollar goes. Pixomondo Toronto and Vancouver closures, the GPU render ceiling, the in-camera image fails at scale.
  4. The category replacement: Near-Time Visual Effects. Pre-production where the picture gets built, the shoot where Fabrixx takes over, ComposiTrack, Fluxx Automate, two finishing tracks, vendor recast, hybrid bounded AI, agentic deferred.
  5. Why this works now. USD landed, cloud compute rentable, industrial distress, Warp retrofit.
  6. Phased roadmap.
  7. What this means for the studio. Fluxx Vault as compounding asset graph.
  8. What this paper is not.

Audience. Producers, executives, and investors who know film production but aren’t deep VFX specialists. Built per Session 58 audit architecture and Session 61 sequence reorder. Drafted as v4 NotebookLM Source 3.

Framing differences from OS v4.

  • Different posture. OS v4 frames Fluxx as “the operating system Govaere named, made deployable”, peer-level convergence with Govaere as cited authority. Near-Time v0.1 explicitly removes Govaere as cited authority and states the structural failures from inside the work, on Fluxx’s own ground. No rebuttal frame, no co-diagnosis frame.
  • Equal weight on VP and VFX failures. OS v4 treats VP as the entry point and uses Govaere’s “missing business model” framing to ladder in. Near-Time v0.1 treats VP failure and VFX failure as parallel first-class diagnoses.
  • Different category claim. OS v4 names the company answer (Fluxx). Near-Time v0.1 names the category: Near-Time Visual Effects, a structural replacement for both VP and traditional VFX. The wall is “a high-end peripheral the production plugs in when the day calls for it.”
  • Taxi-cab analogy is load-bearing in Near-Time v0.1, foregrounded as the explanation of why VFX won’t fix itself from inside. Not present in OS v4.
  • The $3-5K/shot setup multiplier × 1,000-shot show = $3-5M floor is the load-bearing economic claim in Near-Time v0.1. Not present in OS v4 (which uses the more general “50-artist reality” framing).
  • Pre-shoot Viz cascade (TechViz → LightViz → CompViz) and Fluxx Automate chain are named operationally in Near-Time v0.1. Not present in OS v4.
  • ComposiTrack methodology described in patent-canonical detail in Near-Time v0.1 (chroma shift to average background, mathematically perfect matte, no spill). Not present in OS v4.

Status. DRAFT v0.1, Session 61, 2026-05-04. Build notes for v0.2 already itemized: reconcile $3-5K/shot setup number against internal Master Budget; cross-check ComposiTrack chroma-shift phrasing against patent v2; confirm Warp 5-flight-case spec; decide whether to name Aquaman explicitly; potentially add concrete workflow-uniformity example.

Files.

  • 02_Working/Strategy/Company_Overview/Fluxx_White_Paper_Near_Time_VFX_DRAFT_v0.1.md (filed in Company_Overview/ rather than Whitepaper/, a small inconsistency flagged S94 audit)

Pipeline Architecture (v0.1)

New whitepaper output from the S123 pipeline research package. Targets the AYON Port / Reject framing, the five Fluxx-native primitives, and the dev plan v0.3.

Structure.

  • Executive summary of the five Fluxx-native primitives (capture-time clean key, split compute, content-addressed Vault, two-track finish, pipeline-owned VM lifecycle)
  • AYON Port catalogue plus AYON Reject catalogue with per-item rationale
  • Cross-mapping table (Fluxx terms × standard pipeline conventions)
  • DCC bridge architecture (6 surfaces with AYON analogs plus 2 Fluxx-native)
  • Plugin SDK comparative
  • Open architectural decisions gating v0.2

Audience. Engineers, vendors integrating, counsel evaluating patent surface. Tier 2 visible.

Status. v0.1 shipped S123. Companion to the dev plan v0.3 and the financial model v2.0 as the technical-substrate description.

File.

  • 02_Working/Pipeline_Research/Fluxx_Pipeline_Architecture_Whitepaper_v0.1.md

The Cost of Filmmaking (in progress — Phase 1, S139)

Purpose. The research-base whitepaper for the S139 cost-claim broadening (Q-G57 §5): demonstrate that the whole-film cost comes down, not only the VFX line, and that the combined case clears the 50%-on-VFX floor. Variant G Line 2 (Q-G20, Cameron-anchored) is effectively its thesis sentence.

Audience. Investor / cold (Hallstone-tier and VC rooms); the document that backs the “platform brings down the cost of the whole film” claim.

Status. Phase 1 in flight as of S139 (2026-05-29). Kickoff brief: 02_Working/Strategy/Whitepaper/Cost_of_Filmmaking_Whitepaper_Kickoff_2026_05_26.md. Feeds the August Series A pitch deliverables track.

Cross-refs. Q-G20 Variant G · Q-G57 §5.

Two-whitepapers question resolved (S125, Kevin)

Status: resolved 2026-05-20 (S125). Near-Time VFX v0.1 is the canonical thesis document going forward. Operating System Around the Wall v4 is archived as historical snapshot — preserved for reference, NDA-distributed copies from April 2026 remain valid for audiences already in the Govaere-converging conversation, but the canonical thesis document of record is Near-Time v0.1.

Why Near-Time supersedes:

  • The S58 audit (2026-05-04, six days after OS v4 shipped) explicitly called for “remove Govaere as cited source, equal weight VP+VFX, no rebuttal frame, taxi-cab analogy preserved, automation foregrounded, agentic deferred.” That was a thesis pivot.
  • Near-Time v0.1 was built to implement that pivot directly. It removes Govaere as cited authority, frames the structural failures from inside the work on Fluxx’s own ground, gives equal weight to VP and VFX failures, names the category (Near-Time VFX) rather than the company, and loads the taxi-cab analogy plus the $3-5K/shot setup floor plus Viz cascade plus Fluxx Automate plus ComposiTrack methodology as canonical material.
  • Keeping both as parallel-canonical would create messaging ambiguity, with two thesis documents pointing at different anchor sources. The audit pivot was clear; Near-Time v0.1 is its implementation; that document is canonical going forward.

OS v4 remains in the file system at 02_Working/Strategy/Whitepaper/ as historical reference, and copies already distributed under NDA remain valid for the recipients who have them. New distribution defaults to Near-Time v0.1.

Pipeline Architecture v0.1 stays separate from this supersession — it is a technical companion document targeting engineers / vendors / counsel, not a thesis document. Three streams collapse to two living + one archived: Near-Time v0.1 (canonical thesis), Pipeline Architecture v0.1 (technical companion), OS v4 (archived historical).

Cross-references

Q-G entries the whitepapers depend on:

Audience visibility

industry, investor, counsel, vendor.