#moonqipai

#Game coverage

#Shared abstractions

• core.Engine — one facade for the five board games: apply / legal_moves / undo / turn / is_over / outcome / render, with per-game native notation (GTP vertices, ICCS, UCI, coordinates).
• core.GameInfo — structural metadata in the spirit of OpenSpiel's game type: player-count range, perfect/imperfect information, chance involvement, sequential turns. Tools branch on this instead of hard-coding rules.
• core.Rng — seeded splitmix64 source; every chance-driven game is fully reproducible from its seed.
• Hidden information — engines only expose what the acting player may see: blackjack hides the dealer hole card until settlement, five-card draw exposes hands solely through hand_of(seat) for the seat's owner and publishes a textual action log for everyone else.
• Outcome — normalised terminal results with record strings ("1-0") and game-conventional margins ("B+24.5"), plus structured settlement (payout multipliers in blackjack, pot collection in five-card draw).

#Usage

// one interface for all board games
let c : @core.Engine = @core.Engine::make(@core.Chess)
let _ = c.apply("e2e4")
let moves : Array[String] = c.legal_moves()

// original gomoku
let g : @gomoku.Gomoku = @gomoku.Gomoku::standard()
let _ = g.play(7, 7)

// blackjack with a reproducible shoe
let bj : @blackjack.Blackjack = @blackjack.Blackjack::new(42UL)
let _ = bj.act(@blackjack.Hit)

// complete five-card draw hand, 2..=6 players
let p : @fivedraw.DrawPoker = @fivedraw.DrawPoker::new(4, 7UL)
let _ = p.bet(0, @fivedraw.Call)

#Building and testing

moon check
moon test
moon run cmd/main

#Roadmap

• Unified engine integration for gomoku/othello into core.Engine (they are standalone engines today);
• more card games on the shared betting skeleton (stud, hearts);
• simultaneous-action and repeated-play metadata extensions to GameInfo.

#Scope statement