First opponent archetype tags
PokerTracker 4 will eventually feed archetype tags from a HUD. Until then, the manual workflow: at the end of each session, pick the three to five opponents you played the most hands against. Tag each one in `poker-coach opp tag` with one of the standard archetypes (nit, TAG, LAG, fish, whale, regfish). Note one specific exploit you would deploy against that opponent in the next session. Resist the urge to over-categorize; the archetype is a starting point, not a verdict.
Chapter focus Tag your first ten opponents with archetype labels in poker-coach, and note one specific exploit per tag.
Load-bearing idea
Population reading is the bridge between solver work and exploitative deviation. Every solver-deviation that is exploit-justified rests on a population-level claim: “This opponent or this stake’s typical reg folds river to a third barrel at higher than the GTO indifference frequency.” Without archetypes, you have no opinion to deviate from.
The simplest archetype scheme that compresses information enough to be useful:
- Nit — VPIP < 18, very tight ranges, folds to aggression, value-bets thin
- TAG — VPIP 20-26, tight-aggressive, balanced postflop
- LAG — VPIP 28-35, loose-aggressive, applies pressure on every street
- Fish — VPIP > 35, calls too much, doesn’t fold pairs
- Whale — extreme fish; calls everything down, opens any two
- Regfish — looks like a reg by VPIP/PFR but has specific population tendencies (e.g. overfolds river, under-bluffs turn)
Retrieval prompts
- What are the standard archetypes and what VPIP ranges separate them?
- What is one specific exploit against a nit?
- What is one specific exploit against a fish?
- Why is the regfish category the most valuable for exploit deviation?
Re-derivation log
After the first 1,000 hands logged through poker-coach, run poker-coach opp list --archetype regfish and review the matches. For each, note one specific solver deviation you would make and why. The deviation must be testable as a calibrated read.