Files
SilverMetal/windows/drivers
sysadmin 3a30a0421e docs(windows): add ISO-builder design + scaffold the windows/ tree
Add windows/iso-builder.md: reproducible custom-packed-ISO pipeline design for
SilverMetal Enhanced - Windows on IoT Enterprise LTSC. Covers the licensing
frame (IoT = blessed channel for preinstalled custom images; self-apply stays a
builder), 7 build stages (verify/extract/DISM-service/inject-unattend/brand/
oscdimg-repack/attest), the offline-vs-first-boot-vs-firmware control split, an
honest reproducibility scope (pinned inputs + SBOM + attestation, NOT bit-
identical on Windows), and M0-M4 milestones.

Scaffold windows/ per the planned layout:
- installer/  build.ps1 (7-stage orchestrator, stages stubbed to M2),
              inputs.manifest.json (pinned-input schema), autounattend.xml
              (local-account OOBE), oem/SetupComplete.cmd (first-boot runner)
- hardening/  shared §A-H PowerShell modules + Verify-SilverMetalWindows.ps1
              (used by BOTH the ISO first-boot path and the self-apply track).
              BitLocker module enforces TPM+PIN and blocks TPM-only.
- policies/ wdac/ debloat/ stack-installer/ drivers/ tests/  scaffolded with
  READMEs; wdac/ documents audit->enforce; debloat/ flags Tiny11/NTLite as an
  anti-pattern; rename applocker/ -> wdac/ realised.

All 11 PowerShell scripts parse clean; manifest JSON + autounattend XML valid.
Module bodies are M1 scaffold (safe: log + policy-set; interactive/firmware
steps documented, not faked).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-08 15:35:13 +01:00
..

windows/drivers

GPD Pocket 4 driver pack, injected offline into the WIM (DISM /Add-Driver) by ../installer/build.ps1 stage 3.

Targets the Pocket 4 hardware a vanilla LTSC install may lack: Strix Point GPU, sensors / auto-rotate, Wi-Fi, fingerprint, modular-port controllers, fan/EC.

Sourcing (M2): confirm redistribution terms for the GPD driver pack. If redistribution is not permitted, store a sourced manifest (URL + SHA-256 + version, pinned in ../installer/inputs.manifest.json) and fetch at build time rather than committing the binaries.

Open question (hardening-spec §8): which drivers are actually absent from a vanilla LTSC install — determine on the physical unit.