Project specifications
These are current implementation specifications at the frozen revisions, not an approved product requirements document.
Assembly specification
A delivery is identified by:
customer name + customer_project + niseCore ref + WBF ref + include ref
+ EWDK version + build method + target + package type + build typeThe release workflow resolves all refs to SHAs before change detection. Release evidence records the exact source SHAs.
Runtime contract
- Windows WBF requests are accepted by sensor/engine/storage adapters or the WBDI driver.
CBiometricDeviceowns device initialization, capture/power state and asynchronous request completion.- niseCore VFM owns cross-module biometric sequencing.
- Sensor, matcher and storage behavior is selected through niseCore build features and WBF customer properties.
- Firmware traffic uses structures/constants from
biometrics-include.
Compatibility dimensions
- Source branch pair: niseCore and WBF branches are customer-selected together.
- Customer project: WBF and niseCore build properties select sensors, matcher, storage, services and packaging.
- Architecture target: current matrix contains X64 and ARM64.
- EWDK: current matrix feeds EWDK version to automation.
- Test variant: utest maps target refs to compatible type/mocking environments.
Failure semantics
Build, sign, package and test failures are distinct stages. Release fan-out has fail-fast: false; one customer failure must not hide other customer outcomes. Missing Wiki/release-history rows are reconciled from exact owed-row artifacts rather than reconstructed heuristically.