Skip to content
Fluxx

Technology

Rewritten 2026-09-24 (ledger A12, the second pass). The Technology section was written in May 2026 around a pipeline framework, a vault and a cloud product under names since retired; the prior body of every page in it is kept whole at 02_Working/Archive/Wiki_pre_second_pass_2026_09/technology/. The technical canon now lives in 02_Working/CLI_Briefs/: THE_FRAME.md first, then THE_ANSWER.md, THE_ANSWER_2.md, THE_ANSWER_3.md and THE_ANSWER_4.md, Collector_Spec/COLLECTOR_SPEC.md, System/SYSTEM_MAP.md, System/DEVELOPMENT_PLAN.md and System/UI_AND_FEATURES.md. Product copy comes from 02_Working/Strategy/Company_Overview/FLUXX_DESCRIPTION_2026_09.md; the canon in 00_Canon/Q-G/ carries its content, and Kevin’s view of the industry sits behind a barrier at 04_Fluxx_Shared/Industry_View/.

The rail running through every page: the product is not built around another product. The reference recorder on the stage is the safety, checked against, never depended on. Files are truth, databases are views. ComposiTrack is the canonical product name (Q-G88); ChromaTrack appears only in the filing. Velvet is the UI library (Q-G71, Q-G72). The product itself is “the Fluxx platform”, a placeholder; six name candidates sit in the description §6 and none is locked.

Pages in this section

  • Pipeline Architecture, current: the three things being built, the chain, the stack as it stands, what runs where, the two filings, what is open.
  • AYON Port / Reject, retired in place: the May 2026 read of AYON as a blueprint. AYON is not in the current stack.
  • DCC Bridges, retired in place: the bridge as decided in September 2026 replaces it, camera.usd and lens.nk into Maya and Nuke, and bridge services that supervise the applications from outside.
  • Cross-Mapping, retired in place: the vocabulary it mapped is retired; current terms live in the description and the glossary.
  • Plugin SDK, retired in place: no plugin SDK is in the current plan.

Audience visibility

industry, investor, vendor, counsel.