## How To Work In This Repo

- Read nearby code and tests before editing.
- Work in small steps.
- Start with one failing test or one failing executable check.
- Implement the minimum needed to pass.
- Refactor only after green.

## XP Expectations

- Preserve the red-green-refactor loop.
- Keep changes small enough that a human can review them quickly.
- Leave behind tests that protect the behavior you just added or changed.
- Prefer simple names and direct code over clever abstractions.

## OOP And Design Expectations

- Keep responsibilities explicit. One class or module, one clear job.
- Keep behavior near the data and invariants it uses.
- Prefer composition over inheritance.
- Reuse existing types and patterns before introducing new layers.
- If you see duplication in a business rule, remove it before finishing.

## Do Not Do These Things

- Do not patch over failing tests by editing the test without justification.
- Do not introduce a base class, adapter, or factory unless the surrounding code genuinely needs it.
- Do not spread one business rule across multiple files.
- Do not make unrelated refactors while working on a focused task.

## Definition Of Done

- Tests are green.
- Formatting and linting are clean.
- The diff is minimal, coherent, and easy to explain.