Things that won't move
- Per-user scope: the installer target, the manifest level, and the no-elevation property are architectural. Presets restore semantics will never change — they've already shipped.
- Stable UpgradeCode: your preview install will be upgraded cleanly into the signed release; you don't re-audit from zero at v1.0 (rebuild trust verifies the upgrade; you verify the signature).
- Evidence standard: every public-facing claim on the site refers to gated artifacts. Some claims will expand (future features), none will silently vacate already-shipped gates.
Things your feedback moves
- Which of the eight catalog categories make v1.0 first-class citizens (vs staying in Settings menus or docs);
- Support-bundle field sets — the schema has a v2 slot ready if evaluators argue evidence insufficient;
- The exit path of the preview: early-terminate options vs long-tail coexistence with v1.0.
Evaluating the preview is writing the roadmap: the evidence you demand on day one is what the product carries into releases. Request the build when ready, and hold us to everything written here.
ProofTune ProjectEngineering notes — every claim here names the bytes a real tool touches. Verify first, install second.