Project overview
Scope
This Wiki covers the Windows/WBF fingerprint delivery represented by the 13 rows in sw-driver-biometrics_driver/.github/customers.json. It includes the exact niseCore, WBF and include refs selected there, the build/release orchestrator, relevant utest branches, bounded HDRFP issue evidence, configured-branch commits and GitHub Actions outcomes.
Repository and external-system boundaries
| Boundary | Owns | Does not own |
|---|---|---|
| niseCore | Biometric runtime, sensor, matcher, storage, PAL, VFM, host-side firmware command/update processing | Windows WBF packaging, release matrix or firmware implementation |
| WBF wrapper | Windows WBDI/WBF driver, adapters, power/capture lifecycle, firmware/IOTA request orchestration, customer props | Core algorithms, firmware implementation or release scheduling |
| driver-build | Customer/ref matrix, build, validation, signing and release orchestration | Runtime driver or firmware behavior |
| utest | Test specs, extraction/variant/build/run pipelines and focused suites | Production runtime or firmware implementation |
| biometrics-include | Shared host/firmware command ABI and device IDs | Host orchestration or firmware implementation |
| Firmware team (external) | Sensor firmware command handlers, state machine/algorithms, bootloader and released firmware/configuration artifacts | Windows host driver implementation |
Explicit exclusions
- Removed historical niseCore submodule repositories are not followed; selected customer branches contain the source snapshot used here.
- Other wrappers such as bcmush, Android and UEFI are outside the repository baseline except when Jira, build/test infrastructure or firmware-boundary evidence references them. UEFI issues are project-direction evidence, not an assertion that an extra repository was ingested.
- Firmware source implementation is excluded by ownership; the driver-owned command, update, status/error, compatibility and integration contract remains in scope.
- QMAutoTrain’s legacy external Git dependencies are not treated as part of the driver runtime baseline.
- Jira ingestion is currently a bounded project-direction snapshot (2026-07-12 through observation on 2026-08-12), not a claim that all historical requirements are complete.
Product variants
The same project is assembled into HP, Dell and Lenovo deliveries using branch pairs and CustomerProjects names. See customer variants and per-repository branch differences.