Custom intersections
Most of the power is here. The famous landings (one keep, team ranged rallies, one player’s series) are common because lots of people want them. The night you actually fought is usually an intersection that will never have a button.
If you can say the pile in comms, try it. If the Analyst cannot form it, it should say so or ask. That is still the system working.
Focus
Examples of piles that are first-class even with no prepared show:
- Main-defender fights against incoming siege
- Our attacks that went negative
- Only battles where a named teammate appeared as a rein
- Solos in the late window
- Ranged rallies on one keep after they had healed (if you can say the time or the hit index)
- Defenses with more than one incoming rally in a short span
- Joins that were already dust
- A troop type missing on our side
Combine naming a subset. Path B in the loop is this family.
Why this used to die as a daydream
There is no folder in the mailbox named “main vs siege.” Creating it by hand is a filter pass over every report. People do not do a filter pass. They do the fights they remember.
Questions (any wording)
Once you have the custom pile — any of the step-4 shapes:
- Table of points given up by defending troop type on these.
- Who reinforced these, and which rows were thin?
- Do the bad exchanges share a target or an incoming type?
- Effectiveness of a named band on this intersection only.
- List the worst three and open layers.
The questions are ordinary. The pile is what you could not build before.
What a good answer looks like
A post-focus summary that matches the criteria you said (count, side, names). Then the analysis you asked for. No apology that this is not an official report.
Common miss
Waiting until you find a prepared landing that is “close enough,” then analyzing the wrong pile. Close enough is how you teach the team the wrong lesson.