Non Goals

TODO:

• [ ] Add page-specific notes for engineering-process/requirements/non-goals.md after inspecting the real project files.
• [ ] Cross-link Non Goals to the most relevant code, data, testing, and safety pages.
• [ ] State the engineering decision, requirement, or policy being documented.
• [ ] List the options considered and why the current choice was made.
• [ ] Connect the decision to field failures, metrics, or hardware limits.
• [ ] Add files, flags, datasets, and tests affected by the decision.
• [ ] Add what would make this decision need to change later.
• [ ] Add how a reader can verify the decision from evidence in the repo.
• [ ] Add the exact source path, artifact path, or hardware component name.
• [ ] Add the command or procedure needed to reproduce the result.
• [ ] Add expected inputs and outputs.
• [ ] Add the settings, flags, constants, or calibration values that control it.
• [ ] Add known failure modes and how they appear in logs, video, or field behavior.
• [ ] Add validation steps and pass/fail criteria.
• [ ] Add links to related pages that a public reader should follow next.