You Are the Artist

Not "user." Not "developer." Not "musician" or "visual artist" or "creative technologist."

You are the artist. You have ideas. You have intuitions about what should exist. You have frustrations with what currently exists. You dream about possibilities.

MayaFlux exists to let you build those dreams without compromise.

This Isn't About Learning MayaFlux

We're not teaching you a tool. We're inviting you to imagine freely in computational space, and showing you that MayaFlux can handle whatever you imagine.

The persona documents that follow aren't tutorials. They're invitations to think differently. Each one starts from a familiar place (musician, visual artist, game developer) not because those categories matter, but because you need somewhere to stand before you leap.

Don't read them to "learn the API." Read them to see what kinds of thinking become possible when you stop accepting the limitations of existing tools.

The Tool Serves You

MayaFlux doesn't convert your ideas into "its" paradigm. It provides computational substrate that bends to your vision.

You want audio and visuals on the same timeline? No conversion needed. They're already the same data. You want rhythm from chaos? Logic from amplitude? Time that speeds up and slows down based on musical conditions? These aren't "features." They're just what numbers can do when nothing stops them.

The boundaries you've learned ("this is audio software," "this is graphics software," "I'm a musician not a programmer") are artifacts of commercial tool design, not computational reality. MayaFlux removes them.

Imagination First, API When Needed

You don't need to understand coroutines or lock-free atomics or C++ templates to use MayaFlux. You need to imagine what you want to exist.

When you have that vision clear, then you look for the mechanism. The examples scattered through these documents already cover enough API surface to invoke your imagination. When you need more, the documentation exists. When the documentation isn't enough, you ask.

Start with the dream. The implementation comes after.

Most people do it backwards: learn the tool, then try to have ideas within its constraints. That's how tools control artists instead of serving them. We're suggesting you reverse that relationship.

Transcend

In digital space, you are more than where you came from.

The tools you currently use have trained you in certain patterns: "oscillators are separate from envelopes," "audio and video are different pipelines," "control is separate from data," "I make sound, someone else makes visuals."

None of these boundaries are necessary. They exist because physical hardware had those limitations, and software inherited them out of familiarity or laziness or market segmentation.

In computational space, data is data. Audio samples are numbers. Pixel colors are numbers. Logic states are numbers. Time is numbers. Once you accept that, all the disciplinary separations dissolve.

A musician can drive particle system. A visual artist can generate rhythm. A game developer can treat sound as sculptural material. Not because they "learned programming," but because they imagined something that required it, and the substrate let them build it.

You will outgrow whatever category brought you here. That's the point.