A grouped set of Plays representing one approach to solving a bottleneck within a single Loop.
A playlist groups multiple plays under one approach to solving a bottleneck. Playlists exist because no single hypothesis is enough.
The system needs portfolios of bets within a portfolio of intents — diversification at every level of the tree. In the V2 framework, a Playlist is a lightweight loop container: one Loop's worth of committed Plays for one Cell (the time-stable human–AI unit that executes).
Multiple Playlists can run in parallel under the same Intent if different Cells are working on different approaches. At the end of each Loop, the Plays within the Playlist are reviewed and a Scale/Deepen/Pivot/Stop decision is made for each one.
The Playlist itself does not carry a separate decision — it is simply the container for the work being done in that cycle.
Key principles
- A Playlist is one approach to fix one bottleneck.
- Multiple Playlists can attack one Intent over time.
- Re-drawn next Loop based on what Plays taught.
- Cross-Cell Playlists are an edge case, not default.