Driver build and release 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
BLD-REQ-001	Treat customers.json as the authoritative configured customer/ref matrix for this Wiki and release fan-out.	Implementation-derived candidate	Open until approved requirement/acceptance evidence is connected
BLD-REQ-002	Resolve every configured source ref to an exact SHA before deciding whether a release is required.	Implementation-derived candidate	Open until approved requirement/acceptance evidence is connected
BLD-REQ-003	Build, validate, sign and upload without exposing source or signing credentials in artifacts or documentation.	Implementation-derived candidate	Open until approved requirement/acceptance evidence is connected
BLD-REQ-004	Support X64 customers and the configured ARM64 customer through explicit matrix inputs.	Implementation-derived candidate	Open until approved requirement/acceptance evidence is connected
BLD-REQ-005	Continue other customer builds after one matrix failure and reconcile release records after fan-out.	Implementation-derived candidate	Open until approved requirement/acceptance evidence is connected

See project requirements and traceability.