Skip to content
Fluxx

Technology

The Technology section holds the canonical Fluxx pipeline architecture, the AYON Port / Reject framework that informs how Fluxx is built (and what gets explicitly rejected), DCC bridge specifications, cross-mapping between Fluxx primitives and standard pipeline tool assumptions, and the comparative Plugin SDK analysis.

This section is the technical canon that the Development plan executes against and the Pitch deck describes externally. When a vendor needs to integrate, an engineer needs the blueprint, or counsel needs to understand the patent surface, they land here.

The architectural rail running through every page: no third-party at the core of the stack. AYON is blueprint reference only. ftrack is reference design only (Q-G15 integration substrate). Production tracking is built in-house under Fluxx Automate (Cat 3). Vault is Fluxx-owned. Velvet is the canonical UI library name (Q-G71, Q-G72). ComposiTrack is the canonical product name (Q-G88); ChromaTrack appears only in the original patent filing. Fluxx-standalone canon throughout (Q-G89).

Pages in this section

  • Pipeline Architecture, Five Fluxx-native primitives that compose into a single workflow from camera sensor to final composite: capture-time clean key (ComposiTrack), split compute (Warp plus Fabrixx), content-addressed Vault, two-track finish through one workflow (Near-Time plus Near-Time VFX), pipeline-owned VM lifecycle. Each primitive is load-bearing; the combination is the moat.
  • AYON Port / Reject, Architectural inventory of AYON. Patterns Fluxx ports as blueprint reference (package.py manifest, plugin path taxonomy, Pydantic-with-scope settings, bundle abstraction, event spine split, leecher / processor / transmitter pattern). Patterns Fluxx explicitly rejects (LAN-and-file-system substrate, single-tenant data model, no-VM-lifecycle posture, local-launcher distribution, next-day dailies topology, AI provenance as separate product, Nucleus runtime dependency).
  • DCC Bridges, How Fluxx integrates with the major DCCs. v0.1 priority: Nuke plus Unreal plus Maya (working assumption). Eight bridge surfaces: six with AYON analogs (host bootstrap, plugin SDK shape, publish path, load path, event spine, headless mode); two Fluxx-native (VM lifecycle integration, domain extensions for ComposiTrack plus finish-track plus AI provenance plus cost attribution).
  • Cross-Mapping, Fabrixx description × tool assumption rosetta table. Where Fluxx-native primitives map to standard pipeline conventions (Pyblish, leecher / processor / transmitter, Omniverse topology), where they diverge intentionally (LAN-and-file-system substrate, next-day dailies, AI provenance as separate product, Nucleus runtime, worker-pool-only orchestration), and where each side has no equivalent at all.
  • Plugin SDK, Comparative analysis of plugin SDK approaches across AYON, ftrack, ShotGrid, OpenPype legacy, and Pyblish. Fluxx’s plugin path taxonomy: five categories ported from AYON (actions, create, load, publish, inventory) plus four Fluxx-native (provenance, track-assign, stage, cost-attribution). Six settings scopes (extending AYON’s four). VM lifecycle hooks (Fluxx-native). Vendor integration story.

Source files (pre-synthesis)

All in 02_Working/Pipeline_Research/:

  • Fluxx_Pipeline_Architecture_v0.1.md, Fluxx-native architecture (the five primitives plus Port / Reject catalogue)
  • Fluxx_Pipeline_Architecture_Whitepaper_v0.1.md, Whitepaper output
  • AYON_Architecture_Deep_Dive.md, 640-line centerpiece reference
  • DCC_Bridge_Framework.md, DCC integration blueprint
  • Cross_Mapping_v0.1.md, Fabrixx × tool assumption table
  • Plugin_SDK_Comparative.md, Plugin SDK approaches
  • sources/, 5 sub-agent stubs (AYON server, core, tracker addons, cloud / community adoption, OpenPype evolution)

Synthesis status

End-state populated S124. Each child page captures where things landed, not the refinement history. Refinement notes (viz cascade rename, two finishing tracks rename, vendor recast, engine direction shift to Unreal) fed the synthesis as context but do not surface on the rendered pages.

Audience visibility: industry, investor, vendor, counsel. Tier 1 and Tier 2 visible.