Cross-repository workflows

Capture and match

sequenceDiagram
  participant W as Windows WBF
  participant A as WBF adapter / CBiometricDevice
  participant V as niseCore VFM
  participant S as Sensor + PAL
  participant F as Sensor firmware
  participant M as Matcher
  participant T as Storage
  W->>A: capture / identify / enroll request
  A->>V: initialize and request biometric operation
  V->>S: configure and acquire image
  S->>F: packed firmware commands
  F-->>S: capture/result payload
  S-->>V: normalized image/result
  V->>M: extract or match feature set
  opt enrollment/template update
    V->>T: persist or update template
  end
  M-->>V: quality/match result
  V-->>A: operation result
  A-->>W: complete request exactly once

Evidence: WBF BiometricDevice.cpp, CaptureImage.cpp, vfmCoreEntry.*; niseCore common/include/vfm*.h, sensor/matcher/storage trees; firmware structures in vcsfw_v4*.h. Firmware handlers are external; see driver–firmware integration for update/command ownership and evidence requirements.

Customer build and release

sequenceDiagram
  participant C as customers.json
  participant O as all-customer orchestrator
  participant R as release-driver
  participant B as build-driver/action
  participant S as signing service
  participant G as GitHub release/history
  C->>O: matrix rows
  O->>R: one call per customer
  R->>R: resolve three refs to SHAs
  alt source changed
    R->>B: exact refs + project + target
    B->>B: compile and validate
    B->>S: sign package
    S-->>B: signed artifact
    B-->>R: artifact + evidence
    R->>G: release and exact SHA row
  else no source change
    R-->>O: no build needed
  end
  O->>G: reconcile any missing owed rows

Test generation and execution

The utest dev pipeline resolves the target ref to a variant, extracts source functions, overlays compatible types/mocks, builds a focused executable, runs it and parses individual case results. This ties test evidence to a target source revision instead of a copied stale function.