Skip to main content

Roadmap

Missing pieces​

  • A DRS release document per-version (theme, highlights, design boundaries)
  • Release artifact fields in the manifest (release.installer.*, package_version, sha256, path)
  • Build and packaging commands / reproducible build instructions recorded in the manifest
  • Per-version verification records (build result, test count/result, install/uninstall checks) in the manifest and release checklist
  • A release checklist and per-version verification block (release-evidence folder)
  • An artifact integrity record (SHA-256) and evidence filehash.txt for any installer or ISO artifact
  • A signing status declaration for any produced artifacts
  • Explicit instructions or automation to include docs/ in publish output or installer

Next steps​

  1. Confirm and document build/run/packaging commands required to produce a trimmed ISO or installer; add to the manifest under release.build
  2. Create a DRS-style release note draft for v0.1.0 (theme name, highlights, design boundaries) and attach it to docs/
  3. Add release fields to WinTrim.manifest.toml (release.version, release.date, release.installer.sha256/path/size, release.verified)
  4. Run a controlled build of a representative preset, compute SHA-256 of the produced artifact, and append a per-version verification block
  5. Create a release-evidence/v0.1.0/ bundle with build.log, test.log, install-check.txt, uninstall-check.txt, filehash.txt
  6. Document signing posture (self-signed / unsigned / code-signed) for produced artifacts and record it in release notes and manifest

Potential improvements​

  • Automated VM-based smoke tests applying a preset in an instrumented VM, recording side effects (boot, services, missing drivers)
  • A small headless verification CLI (verify-presets) checking preset validity, dependency collisions, and producing a deterministic artifact summary
  • Reversible "restore pack" scripts to re-add high-risk removed components, for recovery scenarios
  • Integrating DSC/winget application of presets into a CI-like local runner to validate installs and post-configuration steps
  • A reproducible ISO build guide (clean-clone steps, exact tool versions) for future reproducibility and provenance claims

Creative enhancements (ideas on file, not committed)​

  • Embedding an Aptlantis metadata capsule into generated ISO images (SVG metadata + base64) so each artifact carries self-describing provenance
  • A small Tauri/Electron single-operator GUI previewing a preset's removals with risk badges and one-click generate/rollback scripts
  • A "simulation mode" performing a dry-run in an offline VM snapshot, outputting an integrity validation matrix vs. baseline
  • A catalog service selecting presets by risk profile (safe/caution/risky), generating a tailored restore-pack and operator checklist
  • An interactive HTML report per preset linking removed components to re-add instructions and winget alternatives, shipped inside docs/