Reading the rubric into code

Reading the rubric into your code. Every class FRQ rubric has the same five rows; aim your code at them:

1. Fields: correct types, private. One field per state variable the story names — no more, no less.
2. Constructor: every field assigned (parameters via this.), derived fields computed, nothing invented.
3. Transitions: each mutator implements exactly its rule sentence, guards included.
4. Accessors: computed from state on demand, no caching duplicates.
5. No extra public API: methods the story never named cannot earn points and can leak state.

Time plan for a 9-point class FRQ: 3 minutes reading/marking rules, 4 minutes writing fields+constructor, 8 minutes transitions, 3 minutes accessors, 2 minutes rule audit. The audit finds the missing guard — the single most common lost point.