WBF wrapper 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
WBF-REQ-001	Translate Windows WBF sensor, engine and storage operations into niseCore operations and compatible results.	Implementation-derived candidate	Open until approved requirement/acceptance evidence is connected
WBF-REQ-002	Manage device initialization, pairing, capture, cancellation, completion, power transitions and wake notifications.	Implementation-derived candidate	Open until approved requirement/acceptance evidence is connected
WBF-REQ-003	Select customer-specific properties and package contents without mixing incompatible customer branches.	Implementation-derived candidate	Open until approved requirement/acceptance evidence is connected
WBF-REQ-004	Support configured USB/SPI/HID and optional service paths only when their customer features enable them.	Implementation-derived candidate	Open until approved requirement/acceptance evidence is connected
WBF-REQ-005	Build with the selected EWDK, platform, package type and engineering/production mode.	Implementation-derived candidate	Open until approved requirement/acceptance evidence is connected

See project requirements and traceability.