Start with fixed table rules

In Web table management, enable squid and confirm currency, value, supply and tiers. These settings belong to a table session, not every table in the account.

Duplicating a table carries fixed rules, not its active round, issued tokens or settlement history. Rule changes normally start next round; correcting an active round uses an explicit flow and must remain consistent with recorded holdings.

Maintain the round roster

A new round uses seated participants and explicitly starts at zero. Update holdings manually; complete distributions allow remaining supply and reference settlement to be calculated.

Someone folding before the flop still belongs to the squid round. Current seating and round participation are separate. A replacement player cannot inherit the previous occupant’s holdings.

Let a new hand inherit context

A hand associated with a table inherits its rules and, when present, active-round state. Edit holdings beside the existing hero and opponents; do not create a separate Hero/Villain roster.

Rules can be inherited even before a round has been started. Missing dynamic state does not turn the hand into a regular cash game. When recording partway through a round, correct input defaults to actual known holdings; missing historical values must not become confirmed zeros.

Preserve a hand snapshot

Save the pre-hand rules, identities and holdings independently. Later rounds must not rewrite old hands. Historical recording uses the information from that time, not today’s table state.

Saving a hand review is not a token-award command. Partial logging, repeated saves and old-hand edits must not repeatedly add tokens to the live round.

Export readable text

Copied or shared text should include natural-language rules, starting state and named player holdings. Internal JSON, database identifiers and model instructions do not belong in the visible hand history. Analysis distinguishes deterministic transfers from uncertain continuation EV.

Native app status

The independent app’s native squid workflow is in development. It will use its own seating and recording screens with the same rules/round/snapshot relationship. Product instructions here describe Web; they do not claim that the app already supports every operation.

Start by checking a table’s actual agreement and verifying that one new Web hand carries the intended rules and player counts.