AYON Port / Reject

Retired 2026-09-24 (ledger A12, the second pass). This page catalogued which AYON patterns Fluxx would port into a pipeline framework and which it would reject, and framed the on-set review window under a name since retired; its prior body is kept whole at 02_Working/Archive/Wiki_pre_second_pass_2026_09/technology/ayon-port-reject.md. It is kept as a record of that research, not as the plan.

Where it stands

AYON is not in the current stack and neither is the pipeline framework this page was written for. The engine is Fluxx Automate, which exists and runs today: a visual graph that is both the design of the pipeline and the thing executing it, with a hub on the stage and a hub in the studio, service agents on the storage and render machines, and bridge services that launch and supervise the animation and compositing applications from outside them. The bridge from the set to post was decided on 2026-09-14 and is in 02_Working/CLI_Briefs/THE_ANSWER_3.md. Files are truth, databases are views: every take is one immutable directory closed by one rename, and Automate’s database is an index that can be dropped and rebuilt.

The one line from the old page that survives in the new plan, in different words: review happens on the floor, minutes after the cut, not the next day. The floor postvis renders on the stage’s own machine and the director decides there.

Cross-references

• Pipeline Architecture
• 02_Working/CLI_Briefs/THE_ANSWER_3.md, the bridge decided
• 02_Working/Pipeline_Research/AYON_Architecture_Deep_Dive.md, the research this page summarised, kept as research

Audience visibility

industry, investor, vendor, counsel.