Requirement traceability
| Requirement | Topic | Intent/problem evidence | Implementation path | Validation | Current assessment |
|---|---|---|---|---|---|
| FPS-REQ-001 | Fingerprint lifecycle | One-month enrollment/authentication bugs and feature requests | WBF → niseCore VFM/sensor/matcher/storage | utest plus customer/runtime scenarios | Active; recurring customer issues show behavior remains a moving target. |
| FPS-REQ-002 | Windows power/wake integration | Broadest Jira theme; current Lenovo/HP/Dell power and resume issues | WBF CBiometricDevice, power/wake; niseCore sensor behavior | virtual/unit plus hardware/OS power tests | Active; unresolved and blocked issues remain. |
| FPS-REQ-003 | Customer composition | HDRFP-12258/12268 and customer matrix | customers.json + project props + source refs | IOTA/matrix checks and exact customer build | Automation improving; latest all-customer run skipped actual builds. |
| FPS-REQ-004 | Firmware compatibility | IOTA/UEFI/EFI/command issues plus explicit project scope decision | WBF update/command → VFM → niseCore sensor → include ABI → external firmware | host tests + joint device/firmware evidence | Driver side documented; firmware source excluded; joint compatibility evidence incomplete. |
| FPS-REQ-005 | Targeted delivery | HP ARM64/UEFI and customer build issues | driver-build inputs + WBF/niseCore | X64/ARM64 customer builds | Configuration documented; full current matrix build not observed. |
| FPS-REQ-006 | Secure delivery | signing/release workflows | build/release/sign action | signed artifact/workflow result | Per-run evidence required; no blanket pass. |
| FPS-REQ-007 | Source-grounded testing | HDRFP-12248/12256/11807 | utest variant/extract/build/run and adapter workflows | parsed cases and run artifacts | Active expansion; successful bounded runs observed. |
| FPS-REQ-008 | Traceability | User-approved Jira→Git→Actions evidence model | manifest, ledger, commit keys, run SHAs | deterministic Wiki/checkpoint validation | Implemented structurally; 43/72 monthly commits lack HDRFP keys. |
| FPS-REQ-009 | Rust adapter parity | HDRFP-12243/12256 | WBF Rust adapter/policy service + C++ reference/replay + driver build | C++/Rust Actions, replay and hardware/customer tests | In Progress; direct issue linkage incomplete for many commits. |
| FPS-REQ-010 | Engineering feedback | HDRFP-12216/12258/12267/12268/12269 | IOTA, code-check, daily-build, AutoHLK, quality-system work | Action jobs with failure/skip semantics | Mixed maturity: automation implemented in parts; quality system remains planning. |
Evidence joins
- Jira → Git → Actions mapping
- Current project direction
- GitHub Actions evidence
- Driver–firmware boundary
Status rule
No row is “approved” or “complete” merely because code exists. Jira state, merged solution and passing validation remain separate facts. Completion needs applicable customer acceptance and, at the firmware boundary, exact joint integration evidence.