Biometrics include requirements
The following are repository responsibility candidates inferred from source and configured workflows. They link to project requirements but are not approved customer requirements.
| ID | Candidate responsibility | Evidence class | Approval/status |
|---|---|---|---|
| INC-REQ-001 | Keep host and firmware command IDs, payload layouts, flags and sizes ABI-compatible. | Implementation-derived candidate | Open until approved requirement/acceptance evidence is connected |
| INC-REQ-002 | Use packed structures and fixed-width types consistently across compiler/platform boundaries. | Implementation-derived candidate | Open until approved requirement/acceptance evidence is connected |
| INC-REQ-003 | Separate core, private, FIDO, module-test, tuning and sensor-family namespaces into discoverable headers. | Implementation-derived candidate | Open until approved requirement/acceptance evidence is connected |
| INC-REQ-004 | Keep device identity constants aligned with host-side sensor selection. | Implementation-derived candidate | Open until approved requirement/acceptance evidence is connected |
| INC-REQ-005 | Treat header changes as cross-repository contract changes requiring driver and firmware compatibility review. | Implementation-derived candidate | Open until approved requirement/acceptance evidence is connected |
See project requirements and traceability.