# Moving tables: five-case reader

Original educational illustration for GTO Gecko, September 15, 2026. Open `case-reader.html` in a browser. The file works offline with no external scripts, styles, fonts, tracking, storage or network requests. Source links require a connection.

## Scope and method

Five fixed constructed examples compare two procedures: tournament table balancing and moving from a broken table. Scope: no-limit Hold'em with more than two players, timely arrival before the next deal, and dealer-resolved next-hand positions. Conceptual relative positions are BTN (button), a gap strictly between BTN and SB, SB (small blind), and BB (big blind). These are not complete physical tables, an ongoing hand, an action-order diagram, a seating algorithm or live adjudication.

All cases exist in static HTML. JavaScript adds Previous, Next, Reset and Show all controls. Without JavaScript all five cases remain visible. With JavaScript the first case is initially shown. The JSON is source data rather than a runtime dependency.

Build the HTML from the reviewed cases with `node build.mjs`. The standalone HTML includes its own CSS and JavaScript. No probabilistic model, solver or player data is used. Exact numerical blinds, chip stacks, antes and rake are irrelevant to these seat-assignment examples and are intentionally unspecified.

## Sources

Primary source: Poker TDA, **2026 Rules Version 1.0, September 6, 2026**, Rule 11-A/B (New Players and Players from Broken Tables) and Rule 12-A (Balancing Tables and Halting Play). Official release and rule files: https://www.pokertda.com/forum/index.php?topic=1759.0 . Access date: September 15, 2026. This casebook uses that version; confirm the rules adopted by your event.

The five fixtures distinguish:

1. **Balancing — Rule 12-A:** last hand BTN1/SB2/BB3 and all players still present implies next hand BTN2/SB3/BB4. Confirm that the case moves seat 4 (the next BB), then uses a floor-confirmed destination BB.
2. **Balancing — Rule 12-A:** verify that the apparent SB assignment is a suspected conflict, not a valid destination or permission to self-seat. The stated response is to ask the floor.
3. **Broken table — Rule 11-A:** verify that a player assigned SB can receive a hand.
4. **Broken table — Rule 11-A:** verify that the new BB assignment is not excused by having posted BB before moving.
5. **Broken table — Rule 11-A:** verify that the position is strictly between BTN and SB. The immediate result is no hand dealt; the dealer confirms when the player enters. No exact waiting duration is specified.

For manual verification, open the official 2026 v1.0 longform document, compare each numbered fixture above with its cited rule, then open `case-reader.html` and use Next through all five cases. Confirm the destination tag and response match `cases.json`. Rule 11-B establishes the separate random table-and-seat assignment process for a broken table; the reader intentionally does not simulate that assignment.

## Accessibility and layout

Semantic headings and ordered position lists, persistent explanatory text, visible keyboard focus, at least 44px button height, no hover-only information, no autoplay or motion, and text labels alongside all color cues. Narrow screens stack the four positions in the same order. Print layout exposes all cases. These implementation checks do not constitute a full accessibility audit.

## Limitations

The examples do not calculate the worst position, resolve multiple possible destinations, identify the player to move from a live table, or override event staff. Local house rules and the event’s adopted rules may differ.