# Scoring

| Dimension | Weight | Description |
| --- | ---: | --- |
| Runs without fatal errors | 20 | The app starts, renders, and can be interacted with. |
| Core functionality | 30 | Ball, paddle, bricks, score, lives, pause, game over, and restart work. |
| Visual completion | 20 | The game looks coherent and communicates state clearly. |
| Interaction quality | 20 | Controls feel usable on desktop and mobile. |
| Code sanity | 10 | The implementation is understandable and avoids obvious brittle shortcuts. |

## Grade Mapping

| Grade | Meaning |
| --- | --- |
| S | Polished and stable |
| A | Playable and complete |
| B | Works but rough |
| C | Partial |
| D | Broken or unusable |

## Review Note

Arena scoring is case-specific. It is meant to explain visible outcomes for this task, not to rank models universally.