Build the show once.

The show lives in one place

Today, Rundown already holds the show: songs, order, per-song MIDI actions. On song change it fires recall at every sibling app — Breakbeat loads the kit, Cycle loads the performance, Pit loads the patch. That works now, on one machine.

Next: Rundown as the armed master In progress

The approved plan promotes Rundown to the suite’s master set organizer. Arm a show and Rundown drives the whole rig over your LAN: apps discover each other, load the named setlist from the shared show file, and follow next/prev/goto — with panic always one press away. The acceptance test is the demo of the whole idea: build a show on machine A, arm it, and watch Breakbeat and Pit follow on machine B.

The simple Rundown stays simple. The master-organizer features build on top of it, not into it — a sub who runs one setlist never sees them.

Midiable — the Ableton bridge In Design

Every song in a setlist as a standard .mid clip (that part works today). A complete .als Live Set generated offline — tracks, clips, locators per song — with no Ableton plugin or runtime dependency, verified against a real Live 12.4.3 golden file. And the two-way live mirror between Rundown and Live. Plain files on purpose: they work in every DAW, forever.

Backline — the tech side of the stage In Design

Patch recall for amp modelers: Kemper and Quad Cortex first. The side-stage tech gets a big-button Performance View — tap the song, every device gets its patch change. Wire it to Rundown and it happens automatically on song change. And the setlist exports straight into a Kemper performance list: the thesis, made literal.

Why you can believe the roadmap

The integration layer underneath all of this is already frozen as a contract: shared show files, a common recall trigger format, one OSC namespace, per-app ports, and a prime rule that never softens —no app ever fails, nags, or degrades because a sibling is missing. The vision is additive. The standalone apps are the product either way.