The Theorem

Select 3 mathematical concepts from different domains. The selection should feel algorithmic — seeded by the current date, the state of the ecosystem, and what territory is uncovered.

The Mathematics Library

Selection Algorithm

• Use today's date as a creative seed — different days surface different domains
• Cross-reference against existing engines' implicit mathematical foundations to avoid redundancy (e.g., XOpal's granular synthesis already explores stochastic particle distributions)
• Prefer domains that complement existing sonic territory rather than echo it
• At least one selection should come from an unexpected or rarely-explored domain
• If the user provides a domain hint (e.g., "rooted in geometry"), constrain to that domain while still picking 3 diverse concepts within it

Output per Axiom

For each of the 3 selections:

• The Formula: The mathematical concept in its native language — name it, describe it in one sentence
• Core Property: The single most remarkable property of this concept (what makes it mathematically beautiful or strange)
• Why This One Today: Why this concept surfaced given the current ecosystem state and date

Stage 2: Organic Evolution — The Alchemist

For each mathematical seed, perform a creative metamorphosis. The Alchemist finds the bridge between abstract mathematical properties and physical/sonic phenomena. This isn't metaphor — it's translation. Every mathematical property has a sonic analog.

Translation Framework

The Alchemist's Work

For each concept:

1. Identify the 2-3 mathematical properties most relevant to sound generation
2. Translate each property into a specific DSP technique or synthesis approach — be concrete (e.g., "use the Lorenz attractor's three coupled differential equations as three LFO sources whose rates influence each other")
3. Describe the sound — not abstractly, but as a producer would hear it. What genre? What texture? What emotion? What does it remind you of?
4. Name the organism — in the XO_OX aquatic mythology, what creature or phenomenon does this concept become? Where does it live in the water column?

Stage 3: Design Vision — The Design Director

The Design Director shapes each evolved concept into a concrete XO_OX product vision. Detailed enough to evaluate and get excited about, open enough to explore further.

Output per Option

Identity Card:

• Name: XO + O-word that captures the essence (verify no conflicts with existing engines)
• Type: Engine / Tool / Feature / Preset Theme / Engine Suite / Expansion
• One-line thesis: What this IS in a single sentence
• Gallery Code: 4-8 char uppercase identifier
• Accent Color: Hex code (verified against existing palette — no conflicts)

Sound Character (2-3 sentences):

• What does this sound like to a producer sitting at an MPC?
• Target genres/contexts (2-4)
• What makes this irreplaceable — what can it do that nothing else in the gallery can?

Design Direction:

• Visual texture/material for the gallery card
• Aquatic mythology placement — water column depth, creature type
• feliX-Oscar polarity position (pure feliX ↔ pure Oscar, or the tension between)

Coupling & Ecosystem:

• Which 2-3 existing engines would couple well with this? Why?
• What gap does this fill in the current lineup?
• 3-5 preset theme names that evoke the concept

The Mathematical Through-Line:

• How does the original mathematical property remain audible in the final product?
• The proof — you should be able to trace the line from axiom to sound

Presentation

Present all 3 options clearly. At least 1 must be an engine concept. The other 2 should be whatever naturally unfolds from the mathematics — tools, features, preset themes, suites, expansions.

After the 3 options, add a Coupling Forecast: if the user pursues Option A, what does it unlock or connect to? Same for B and C. Help the user see downstream implications.

End with: "Which theorem would you like to prove?"

When the User Picks One

• If engine → flesh into a full concept brief, suggest /new-xo-engine
• If tool/feature → draft a functional spec
• If preset theme → draft the preset concepts with names and sound descriptions
• If suite/expansion → map the full scope
• Save the concept to memory for continuity across sessions

Steering

• Domain hint (e.g., "rooted in chaos theory"): Constrain Axiom Selection to that domain, still pick 3 diverse concepts within it
• Creative constraint (e.g., "something dark", "for ambient producers"): Let this influence the Alchemist's evolution, not the mathematical selection — the math stays pure, the creative direction gets steered
• Type constraint (e.g., "give me 3 engine ideas"): Override the "at least 1 engine" rule and make all 3 the requested type