Recipes
A recipe is a situation, a named slice, then the questions you asked next. It is not a cheat code for a prepared landing.
If the only lesson is “say this to get the timeline,” the recipe failed. The useful part is what you asked after you had a here — especially when there was no official view.
Each recipe below is a short worked loop. The large map of questions, including ones people talked themselves out of, is the question atlas.
How to read one
- When it is for
- A subset you named
- What the post-focus summary is for
- Questions that are yours — several wordings, same intent
- A common miss (usually: still on the whole battlefield, or the Analyst moved)
Worked loops
| Recipe | What it teaches |
|---|---|
| Open a battlefield | The first summary is a door |
| Cut any subset | Custom criteria; no prepared view required |
| Ask your own question | Asking on the current focus is the system |
| Compare inside a focus | Comparisons are asks, not modes |
| One keep, then questions | A timeline is a landing, not the finish |
| One player, then questions | A series or defenses, then your follow-ups |
| Team rallies of one type, then questions | A table landing, then drill or stay |
| Effectiveness on the current focus | A measure on a slice |
| Train more on a defense slice | Defense focus, then which troops to build |
| Define a measure | Plus, minus, times, divided by, constants — your column |
Add a recipe
If you ran a loop others can reuse, describe it on Discord. Prefer a battlefield you actually ran. Do not send other players’ screenshots or identifiable report dumps without consent.