1 files changed, 43 insertions, 20 deletions

diff --git a/docs/GAMES.md b/docs/GAMES.md
index cbe355e..52ab1bf 100644
--- a/docs/GAMES.md
+++ b/docs/GAMES.md
@@ -5,18 +5,40 @@
 | Game | Status | Notes |
 | --- | --- | --- |
 | Slots | Done | 5 reels x 3 rows, 5 paylines, 98.6% RTP |
+| Roulette | Done | European wheel, split bets, 97.3% RTP |
 
 ## Planned
 
 | Game | Shape | Main open decisions |
 | --- | --- | --- |
-| Roulette | One spin, many bets | European/French/American wheel; which bet types; 35:1 straight and other payouts |
 | Blackjack | Multi-step hand | Dealer hits/stands soft 17; double/split/insurance; blackjack payout; shoe persistence |
 | Crash | Real-time round | Crash-point distribution; cashout latency; provable fairness |
 
-Roulette fits the current one-request-settle model most easily. Blackjack needs
-server-side hand state and player actions. Crash needs a timed round loop and a
-cashout action, so it should come last unless we redesign the loop first.
+Blackjack needs server-side hand state and player actions. Crash needs a timed
+round loop and a cashout action, so it should come after blackjack unless we
+redesign the loop first.
+
+## Roulette
+
+- European wheel: 0-36, one green zero.
+- Bets: red, black, even, odd, and straight numbers.
+- Bets can be split across all of those; every winning bet is added together.
+- Straight pays 35:1 (36x returned), outside bets pay 1:1 (2x returned).
+- 0 loses all outside bets. RTP is 36/37 = 97.30%.
+
+Client controls inside roulette:
+
+```
+R / B / E / O   add the current chip to red/black/even/odd
+digits + Enter  add the current chip to that number
+C               clear all bets
++ or = / -      change the chip size
+SPACE           spin
+Q               leave the table
+```
+
+The result is shown as a CS:GO-style horizontal strip: the ball marker stays
+fixed and the wheel numbers scroll beneath it, ending on the winning number.
 
 ## Audit schema
 
@@ -35,35 +57,36 @@ plays (
 )
 ```
 
-`game_type` is the game that was played. `details` is a JSON object whose shape
-depends on the game:
+`details` is game-specific JSON:
 
 ```json
 // slots
 {"reels":"CCCCLLCLODGSDGS","win_type":"win","win_lines":"1","win_cells":"0,3,6"}
 
-// rumoured future examples
-{"player":["AS","10H"],"dealer":["9D","7C"],"outcome":"blackjack"}
-{"bets":[{"kind":"straight","number":17,"amount":10}],"winning":17}
-{"crash_point":2.41,"cashout":1.80}
+// roulette
+{"number":"17","color":"black","bets":"{\"red\":10,\"black\":10,\"even\":10,\"odd\":10,\"numbers\":[{\"number\":17,\"amount\":5}]}"}
 ```
 
-The balance updates and the `plays` insert happen in one transaction
-(`database::apply_play`). The slots-specific wire fields (`reels`, `win_lines`,
-`win_cells`) are still in `GAME_RESULT`, but the database no longer assumes
-them.
+The balance update and the `plays` insert happen in one transaction
+(`database::apply_play`).
 
-## Protocol gap
+## Wire protocol
 
-The current exchange is slots-shaped:
+Slots keeps its original exchange:
 
 ```
-PLAY_START <game> <bet>
+PLAY_START slots <bet>
 GAME_RESULT <session> <winnings> <bet> <balance> <reels> <win_type> <win_lines> <win_cells>
 ```
 
-Before blackjack, roulette, or crash can be added, the game session needs a
-generic state/action protocol. A possible shape:
+Roulette adds a compact bets payload and a roulette-specific result:
+
+```
+PLAY_START roulette <total> <bets-json>
+ROULETTE_RESULT <session> <winnings> <bet> <balance> <number> <color> <bets-json>
+```
+
+Blackjack and crash still need a generic state/action exchange, for example:
 
 ```
 GAME_START <game> <bet>
@@ -71,4 +94,4 @@ GAME_ACTION <action> [json]
 GAME_STATE <json>          # cards, bets, multiplier, legal actions, result
 ```
 
-That is a wire-protocol change and will be its own major version.
+That will be its own protocol change.