# Project brief

## Purpose and reader/user

State the small problem the project solves and who uses its result.

## Required behavior

Link named requirements with units, boundaries, invalid-input behavior, and expected outputs. Avoid describing the current implementation as the requirement by default.

## Scope

Name required software behavior and excluded work. State whether acquisition is synthetic, recorded, or physical. Physical work needs its own plan and observations.

## Environment and references

Link the dependency manifest, exact hardware reference, setup commands, and selected checkpoint.

## Acceptance and open questions

List the reproducible checks and the decisions still needed. Link actual results only after execution.