SALSA in one sitting

Bob kept hearing the word SALSA in every output tooltip and finally asked what it was. Tau pushed his horchata aside and thought for a second about how much to say.

Bob came in holding his phone, tab open on the Strategy page. The waiter was halfway to the booth with the combo menu. Tau lifted a hand without looking.

Bob: Every tooltip on this app says "SALSA this" and "SALSA that." What is it, actually?

Uncle Tau: The simulator. You give it your posterior over your skill, it gives you a distribution over how you finish in a tournament. Every position, from first to last. That distribution is what becomes the ROI bands you see on the Strategy tab and the markup quotes in Package Builder.

Bob: OK. How does it do that?

Uncle Tau: It picks the unique distribution that's consistent with what your data forces and adds nothing else. No smuggled-in assumptions, no hidden parameters, no guesses about your ICM awareness or your bubble instincts. Just the shape that has to be true given your inputs.

Bob: How do you know that shape is right?

Uncle Tau: Because of a theorem. The KL divergence from that shape is minimal by construction. In plain English: SALSA's answer is the least biased forecast your data actually supports. Anything tighter and you're lying about what you know.

Bob: That's it? That's the whole pitch?

Uncle Tau: That's the whole pitch. The proof isn't short and it isn't something I'm going to sketch on a napkin at a taquería. It's been written up. You don't need to read it to use the app, the same way you don't need to read Black-Scholes to trade an option.

Bob: But you'd rather I didn't read it.

Uncle Tau: I'd rather the twelve other operators in this industry didn't read it. The framework is what the app is for. The framework is the edge. Once the framework is public, the edge isn't.

Bob: Everybody's a hypocrite.

Uncle Tau: Everybody's a hypocrite. But there's a version of that conversation for subscribers who want more than "trust me, there's a theorem." That's a call, not a wiki page.

What you actually see in the app

Bob: Fine. What do I see when I hit run on the Strategy tab?

Uncle Tau: You pick a tournament, SALSA takes a few thousand samples from your posterior, and for each sample it draws the finishing distribution against that specific tournament's payout structure. Averages the results, gives you a band. The band is your ROI distribution for that exact tournament — its field size, its payout curve, its rake. Narrow band means tight posterior and confident structure. Wide band means less data or a variance-heavy structure.

Bob: That's why different tournaments come back with different ROIs even at the same buy-in.

Uncle Tau: Yes. The payout table matters. SALSA is honest about which tournaments your edge converts best into dollars.

Bob: And the posterior side — that's the priors-and-posteriors thing.

Uncle Tau: Priors and Posteriors is the backward side — outcomes to skill. SALSA is the forward side — skill to outcomes. Together they're a closed loop. You feed your results in, the app infers who you are, SALSA predicts what that person does in any tournament you point it at, and the bands on screen are the result.

Bob: And if the app is wrong about who I am?

Uncle Tau: The posterior widens, SALSA's bands widen, the engine tells you it's not sure. That's the whole point of the machinery you CAN see. The part I'm not walking you through — that's the part that makes the forecast optimal instead of just reasonable.

Bob: Got it. Thanks, Uncle Tau.

Uncle Tau: Go estimate your shapes, kid. And stop reading forum posts that try to explain how SALSA works under the hood. Nobody outside the app knows. That's the point.

What's next

• Archetypes — where the starting beliefs come from before your data shows up.
• Rake is linear — why rake is a flat shift, not a compounding tax, and what that means for how SALSA's output compares across sites.

Further reading

• The closed form and the proof are in an internal paper. For depth — the actual math, the construction, the objects — that's a subscriber call, not a wiki page.
• Priors and Posteriors — the backward side of the same loop.