Sports Logic Utilities

2. Game-Play Logical Constraints

Validation must ensure the data represents a legal game scenario:

The Home Team Advantage

• Winning Home Team: If the Home Team leads at the end of the Visitor's half of the final inning, the Home Team does not bar in the bottom half.
  • Rule: Innings_Home_Batting <= Innings_Visitor_Batting.
• Losing Home Team: If the Home Team loses, they must have completed their final half-inning.
  • Rule: Innings_Home_Batting == Innings_Visitor_Batting.

Scoring Integrity

• Earned Runs: By definition, Earned Runs <= Total Runs.
• Defensive Synchronization: A team's "Innings at Bat" must always equal the opponent's "Innings on Defense."

3. Best Practices

• Regex Validation: Use /^(\d+)(\.([12]))?$/ to strictly enforce the .1/.2 format.
• Tolerance: When comparing sports averages (like TQB or ERA), use a tolerance of 0.0001 to account for irrational number comparisons.
• Signage: Always display averages (TQB/BA) with an explicit + or - sign to improve scannability in rankings.

Resources

• innings_converter.ts: Bi-directional conversion logic.
• game_rules_validator.ts: Template for validating legal game scenarios.