megaDecision-node explorer
The tree view covers every node that actually occurred, at a glance. The explorer, underneath it on the Lines tab, is the general-purpose tool: build any line by hand, click into any outcome, and keep going — flop, turn, or river.
How it works
A line is the ordered prefix of tokens that must already have happened. The node being measured is whichever token comes immediately after that prefix. Click any outcome token to drill one level deeper — the breadcrumb at the top tracks the full line, grouped and labeled by street, so it's always clear whether you're looking at a flop, turn, or river decision.
The explorer walks the full postflop line as one continuous sequence. A line like XB50CX lands its next decision on the turn exactly as naturally as it would on the flop — the hand-class range bar reconstructs the correct board (flop, flop+turn, or the full runout) automatically depending on which street the current node is actually on.
Reading a node
Every node shows, per outcome: the token, its frequency (% of hands that reached this exact node and took this action), and its sample size. When the outcome is Hero's own decision, a range bar shows what Hero actually held across every hand that took it — hover for the full breakdown. When the outcome is villain's decision, the row just says so; there's nothing to show a range bar for since Hero's holdings don't change based on what villain does.
Texture buckets and the GTO column
The filters row includes a board texture bucket — a saved rule (paired/suitedness/high card/contains-ranks, your own definitions, not a shipped taxonomy) that narrows every stat to hands whose flop matches it. When an imported solver aggregated report covers the node you're looking at, an amber GTO frequency column appears beside your own — computed over the same bucket, which is what makes the comparison meaningful: overall frequencies can agree while every underlying texture disagrees. Actions the solver takes that you never took render as explicit 0% rows, and a caption always states how many report flops the bucket covered.
Multiway hands
The explorer only supports heads-up lines — exactly two players seeing the flop, one of them Hero. "Who acts at index 2" only has one stable answer when there are two actors; a three-way flop doesn't have a single line to walk. Multiway hands are excluded from every decision-node and line-frequency query for this reason, not silently mismeasured.
Tagging from a node
Every outcome carries the full list of hands that produced it. Tag them directly from the explorer to build a reviewable list — see Tags.