Failure Boundaries

TODO:

• [ ] Add page-specific notes for autonomy-stack/architecture/failure-boundaries.md after inspecting the real project files.
• [ ] Cross-link Failure Boundaries to the most relevant code, data, testing, and safety pages.
• [ ] Document the exact input entering this subsystem.
• [ ] Document the exact output leaving this subsystem.
• [ ] Map the subsystem to the owning runtime file or module.
• [ ] Describe the control priority when this subsystem disagrees with another subsystem.
• [ ] List the settings, constants, and flags that change this behavior.
• [ ] Add a failure-mode checklist for field testing.
• [ ] Add how to verify the subsystem on the bench before a driving test.
• [ ] Add how to verify the subsystem during a real outdoor run.
• [ ] 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.