Skip to content
Fluxx

Process Docs

Process Docs are the synthesized end-state descriptions of how Fluxx actually works in operational terms. These pages do not capture “what we believe about question X” (that’s Q-Gs) or “the industry voice on Fluxx” (that’s Tracks); they capture how the system runs.

The Q-G layer extracts canon one question at a time. The Tracks render that canon in voice registers for different audiences. The whitepapers make the argument. Process Docs synthesize the operational story: how the parts actually fit together when you’re running the system.

This page is the landing index. The 7 planned process doc pages are the next-phase synthesis output; this page lists what they will contain and points at the source canon for each.

Planned process doc pages

Capture to Delivery Workflow

How the five Fluxx-native primitives work end-to-end. Pre-production viz cascade (TechViz → LightViz → CompViz) builds the lighting recipe and the Nuke script. On shoot day, Warp drives the wall and the camera captures three ComposiTrack sub-frames. Fluxx Automate absorbs the capture into the Vault. Fabrixx renders at quality, applies the pre-comp recipe, returns Near-Time PostViz to set in 30 to 60 minutes. Overnight high-res render produces final pixel. Per-shot finish-track assignment routes to Near-Time or Near-Time VFX.

Sources: Q-G31 Capture To Delivery Workflow, Compute_Architecture_Source_2026_05_03.md, Finishing_Workflow_Source_2026_05_01.md, Near-Time VFX Whitepaper v0.1 §4.

On-Set Operations

Stage architecture (large sound stages 15,000 sq ft+ with smaller modular sets that strike in hours; 3-5 sets pre-built and pre-lit in parallel; leapfrog cross-stage or to location). Crew model. Ari’s role (Executive Director). Shoot day flow. Warp setup. ComposiTrack capture mechanics.

Sources: Q-G51 Stage Design Modular, Q-G37 Volume Utilisation Architecture, Stage_Architecture_Source_2026_05_03.md.

Cloud-Side Operations

Compute architecture (Q-G49). GPU stack. Render queue. Vault sync. VM provisioning lifecycle. Per-tenant cost attribution.

Sources: Q-G49 Compute Architecture, Compute_Architecture_Source_2026_05_03.md, Automation_System_Source_2026_05_14.md, AYON Architecture Deep Dive.

Two Finishing Tracks (final state)

Final landed naming: Near-Time track and Near-Time VFX track. Both ride the same Fabrixx pipeline upstream (same render, same metadata, same Vault). Near-Time track is the bulk-runtime deliverable path (light comp finish, ship). Near-Time VFX track is hero finishing on top of the same render (heaviest creative work). Type of show and type of shot decide which track a shot rides on, not shoot type and not budget. Shots flip between tracks mid-pipeline without leaving the system.

Sources: Q-G45 Two Finishing Tracks, Q-G47 Two Finishing Tracks, Finishing_Workflow_Source_2026_05_01.md, Gap_6_Finishing_Workflow_Draft_2026_05_01.md.

Viz Cascade (final state)

Final landed form: TechViz → LightViz → CompViz. Three sequential bounded pre-shoot phases. TechViz (industry term, Fluxx structural application) handles geometry alignment so the VAD and the practical set are one from camera POV. LightViz (Fluxx first-use) handles lighting alignment; virtual lights match on-set practicals; produces the lighting recipe Fabrixx renders against. CompViz (Fluxx first-use) handles compositing automation; the Nuke script that assembles render passes during the shoot is built pre-shoot, so at runtime when Fabrixx returns passes the script auto-runs and produces Near-Time PostViz. The cascade is plumbing, not the pillar. The shoot-day Fabrixx takeover is the load-bearing pillar.

Sources: Glossary_Source_2026_05_03.md, NotebookLM v4 Build Brief 2026-05-04, Near-Time VFX Whitepaper v0.1.

Vendor Integration Path

How a vendor like Norman / GlassBox writes a Fluxx plugin and what they get out of the box. Three modes for vendors who plug into a Near-Time pipeline:

  1. Lead vendor inside Fabrixx. Vendor’s artists log into the production’s Fabrixx virtual machines. Work happens inside the production’s perimeter. The brand stays on the show; the pipeline and the data don’t.
  2. Loan-out of named artists. Specific senior artists join the production’s core team on the call sheet for the show, then return to their home vendor at wrap.
  3. Scope-defined builds. Vendor delivers a near-final specialized asset across the wall into Fluxx Vault. The production’s team takes it from there.

What the model doesn’t preserve is the administrative middle layer, which is most of the headcount at the legacy houses. State factually, not as attack.

The plugin SDK surfaces are documented at Plugin SDK > Vendor Integration Story.

Sources: Vendor_Recast_Source_2026_05_01.md, Near-Time VFX Whitepaper v0.1 §4, Q-G44 VFX House Role Recast, Gap_5_VFX_Role_Recast_Draft_2026_05_01.md.

AI Provenance and Human Likeness Policy

How Fluxx handles AI-generated content tracking. Vault carries provenance as a first-class field at every Version: prompt, seed, model, model_version, LoRA, generation_timestamp, generation_tool, parent_asset_id, plus C2PA Content Credentials pass-through. EU AI Act Article 50 disclosure met by default (August 2 2026 deadline).

Policy (locked Q-G50 plus Q-G18). Generative AI is used for crowds with performer scanning and payment (faces in crowds scanned from real performers, performer paid, likeness rights honored, AI generates body and motion). Never for performance (lead, named, supporting; no AI synthesis, no face-swap, no deepfake). Narrow disfigurement exception: a face being destroyed in-shot (blowout explosion, disintegration, creature transformation) can use AI fabrication because no performance is being delivered through that face. The line between AI as labor automation (allowed) and AI as performance synthesis (not allowed) is the line between extending what artists can do and replacing what performers do. Final delivered pixels still pass through V-Ray, Nuke, and Houdini, not through generative AI.

Sources: Q-G18 AI Provenance Stance, Q-G50 AI Human Likeness Policy, AI_Provenance_Source_2026_04_28.md, AI_Human_Policy_Source_2026_05_03.md.

Why this layer exists (Kevin S124 framing)

Q-G entries are the extraction mechanism that pulls context out of Kevin’s head one question at a time. The wiki is the synthesis surface where canon entities plus whitepapers plus Tracks plus NotebookLLM context get composed into actionable process documentation that vendors, investors, and operators can use.

Q-Gs are canonical for their job. The wiki is canonical for the operational story.

Source layers

NotebookLLM raw transcripts (inbox, not yet processed):

  • _Inbox/NotebookLLM/2026 Fluxx Overview/v2 With Gaps Filled/kDubz Notes/ (4 meeting transcripts from 2026-05-02)
  • _Inbox/NotebookLLM/2026 Fluxx Overview/May 3rd round 3 Notes/ (5 meeting transcripts plus summaries from 2026-05-03 / 05-04)
  • _Inbox/NotebookLLM/Near-Time VFX White Paper/ (v1 plus v2 transcripts)
  • _Inbox/NotebookLLM/BTS Business Case/ (v1 with Kevin feedback plus v2 transcripts)

NotebookLLM refined outputs (already in 02_Working/Strategy/):

  • Company_Overview/NotebookLM_Podcast_Brief_2026_04_30.md
  • Company_Overview/NotebookLM_Podcast_Transcript_v1_2026_05_01.md
  • Company_Overview/NotebookLM_v3_Audit_Notes_2026_05_04.md
  • Company_Overview/Fluxx_NotebookLM_v4_Build_Brief_2026_05_04.md
  • Industry_Research/Govaere_Compilation_for_NotebookLM_2026_05_04.md
  • Industry_Research/Jason_Myers_BTS_NotebookLM_Compilation_2026_05_05.md

Whitepapers: see Whitepapers. Tracks: see Company Overviews. Source canon: 02_Working/Strategy/Company_Overview/*_Source_*.md (15 files, dates 2026-04-27 through 2026-05-14).

Synthesis status

Process doc pages queued for next CLI session. The S124 kickoff brief flagged the 7 process doc pages as secondary deliverables (after the 15 scaffolded wiki pages). Time did not permit authoring them in S124 alongside the primary 15-page synthesis. They are first priority for the next CLI session.

Refinement note (Kevin S124): capture end-state only. Refinement history (viz cascade rename, two finishing tracks rename, vendor recast, engine direction shift to Unreal) feeds the CLI session as context-to-understand so it doesn’t synthesize stale versions, but the rendered wiki page shows the final state.

Audience visibility

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