Handbook

Example — games

Use game_engine for rules and JSON-safe state; use governed game_move_* / board_game_* tasks for LLM-facing moves.

Updated

Use case

Use game_engine for rules and JSON-safe state; use governed game_move_* / board_game_* tasks for LLM-facing moves.

Source layout

Location Role
examples/games/ Runnable demos (tic-tac-toe, connect-four-like, replay).
Games architecture Layering vs game_lcdl.
Task catalog — Games Links to contract.md specs.

Commands

PYTHONPATH=src python3 examples/games/play_tic_tac_toe.py

(Use the script’s --help if available; behavior may evolve.)

Expected output

Deterministic engine play where the script uses stdlib-only engine paths; LLM paths require credentials elsewhere.

Failure modes

  • Expecting full LCDL task runs from examples/games alone — many scripts exercise engine only; wire tasks per GAMES-LCDL-LAYER.

Next steps