Definition: A parallel branch is one isolated candidate app generated by Taskade Genesis Quantum during a single user prompt. Interference merge is the structural diff that combines all branches into one final app — committing what every branch agreed on, asking the user about what they disagreed on, and discarding outliers. Together they let Genesis ship structurally robust apps by construction rather than by luck.
What Happens When You Prompt Genesis Quantum
- You write one prompt. Example: "Build a hiring tracker for a 5-person recruiting team."
- EVE fans out into N branches. The number is auto-tuned — 1 for trivial edits, 4 for a new space, up to 16 for Deep Think mode.
- Each branch generates a complete Workspace DNA blueprint — Project schemas, Agent prompts, Automation flows, Interface layout.
- The interference merge runs. Genesis compares branches not at the text level (where whitespace and naming break diff) but at the structural level: nodes, edges, types, IDs.
- The merge produces three buckets: invariants (commit), divergences (ask the user), outliers (drop).
- The final app ships. Plus a
branchTraceProject so you can revisit, fork, or share any branch.
Why Structural Diff (Not Text Diff)
Code-generation tools like Cursor and Lovable produce text. When two branches both add a "candidates table," one might call it candidates, the other applicants. Text diff sees two unrelated additions. Structural diff sees one logical entity with two name candidates — and asks you which name to keep.
Workspace DNA gives Genesis the alphabet for this:
- Project has stable ID and field types
- Agent has stable role + tool list
- Automation has stable trigger + action graph
- Interface has stable layout + binding contract
When merge runs on these primitives, agreement is unambiguous. That's why Taskade Genesis can do quantum-style interference and Cursor cannot.
Three Buckets, One Final App
Invariants (Commit Automatically)
Every branch produced the same thing → commit it. Example: "candidates table with Name, Stage, Resume, Applied On" appearing in 4/4 branches becomes the canonical schema. No questions asked.
Divergences (Surface to User)
Branches disagreed → ask the user. Example: "2 branches added a Slack notification when stage changes; 2 added a Gmail digest at end-of-day. Which?" The Ask-Questions tool surfaces this in chat; you pick one (or both).
Outliers (Discard)
One branch had a wild idea no other branch confirmed → drop it. Example: "1 branch added an AI cover-letter scorer; 3 didn't." Unless the user explicitly asked for it, the outlier is silently dropped — saving you from "creative" features you didn't want.
Auto-Tuned Branch Count
| Mode | Branches | When |
|---|---|---|
| Edit | 1 | Trivial in-place modifications (rename a field, change a button color) |
| Standard | 4 | New space generation, default for most prompts |
| Deep Think | 16 | Hard prompts where you want maximum redundancy |
More branches → more compute → more robustness. Genesis chooses based on prompt complexity; you can override with /deep or /edit slash commands.
Decoherence Shield (Why Branches Don't Contaminate)
Quantum computers shield qubits from environmental noise with cryogenic chambers. Genesis shields branches with overlay-only sandboxes: each branch writes to its own overlay; the parent workspace is read-only from the branch's perspective. No branch can see another branch's intermediate state. This prevents the LLM equivalent of decoherence — an outlier idea leaking into multiple branches because of shared scratchpad.