A game board needs to report game over, while one game loop decides what runs next. Direct coupling lets the board call Game explicitly rather than routing that relationship through an interface or event. Game can likewise control when the board is shown, hidden, or ticked. section 5.1.1
if (gameOver)
Game.Instance.GameOver();The game-over call makes Board’s dependency on Game visible at the call site. section 5.1.1
This is a deliberate trade-off, not a rule for every component. Direct dependencies can make objects harder to reuse or change independently, but hiding a real orchestration relationship can make data flow harder to follow. Keep the boundary firm: Unity-facing Game, Board, and menus may communicate directly; gameplay Logic must use only its supplied GameData, Balance, and input values, without a singleton or other hidden state. section 5.1.1
