Driver build and release specifications

These statements describe current implementation at master / 5710513f98348f0353aae0fef1c8ade491c0523f. They are not approved product requirements.

Customer matrix

Selects customer project, niseCore/WBF/include refs, EWDK, method and target. Primary evidence: .github/customers.json.

Build workflow

Dispatches the reusable build action with explicit inputs and protected secrets. Primary evidence: .github/workflows/build-driver.yml.

Release workflow

Resolves exact SHAs, detects changes, builds, caches, packages, releases and records evidence. Primary evidence: .github/workflows/release-driver.yml.

All-customer orchestrator

Fans out one release per matrix row and reconciles missing release-history updates. Primary evidence: .github/workflows/release-all-customers.yml.

Signing/publishing

Supports package signing and publication paths; secret material must remain external. Primary evidence: Sign/, Pipeline_SynaSign*.bat, SynaSignService/.

Validation

Provides accuracy, HLK and security/compliance pipeline assets. Primary evidence: AccuracySuiteValidation/, AutoHLK/, BlackDuck/.

Legacy/Jenkins pipelines

Retains legacy build/deploy flows alongside GitHub Actions. Primary evidence: Pipeline_*.bat, niseBuild*.cmd.

Tuning/tools

Provides tuning, scoring, collection and analysis tooling outside the core driver build. Primary evidence: AutoFRRTuning/, IPLTuning/, QMAutoTrain/, FPCollection/.

Invariants

• Preserve interface/ABI compatibility unless all consumers move together.
• Keep customer/ref and test variant context explicit.
• Report absent evidence as a gap rather than assuming success or deployment.