This directory contains current user guidance, engineering references, release material, and historical investigations. Start with the first section, then use topic sections for deeper detail. Documents marked historical record a completed investigation or an earlier plan; they are not current operating instructions.
- Start here — download and open wootc.
- User guide — use the migrated system and return to Windows.
- Manual tests — pre-flight checks for real hardware.
- Verification status — proven matrix cells and their evidence.
- Philosophy — product goals and decision rules.
- Specification — complete product and protocol requirements.
- Architecture boundary — separates generic migration from bootc-specific code.
- Backend contract — measured deployment-backend interface.
- Deployer experience — deployer screens, states, and recovery behavior.
- GUI and Phase 1 architecture — Windows installer flow.
- GUI walkthrough — screen-by-screen product flow.
- Native Windows shell — WinUI 3 status, transport, and cutover plan.
- Plugin architecture — program-migrator plugin design.
- Session migration — copy, relink, and sign-in boundaries.
- Managed VM — Windows VM lifecycle and ownership.
- E2E architecture — test control plane for hosted runs and boot chain.
- Non-bootc adoption — support boundaries for other Linux systems.
- Distro adoption — installer adaptation for another distribution.
- Brand identity — product names and re-skinned builds.
- Brand distribution — branded installers and offline packages.
- Branded walkthroughs — automated visual walkthroughs for each brand.
- Artifact authentication — boot-artifact verification.
- Destructive paths — inventory of operations that can remove or alter data.
- NTFS on Linux — filesystem hazards and mitigations.
- systemd-boot — package and trust policy.
- Windows state trust — evidence required before Windows state changes.
- VHDX exploration — dynamic root-disk investigation.
- Borrowed from Libertix — adopted boot-chain and recovery designs.
- Upstream blessings — upstream provenance and permissions.
- Verification ladder — phase-by-phase evidence gates.
- Release instructions — green-gated release process.
- Alpha adopter program — structured early-adopter tests.
- Pre-filled profiles — migration tests with an existing Windows profile.
- Native GUI soak — shell stability ledger for long runs.
- Agent lessons — operational traps from E2E work.
- Docs truth pass — dated documentation-versus-build checks.
- Implementation plan — remaining specification coverage.
- Completion plan — dakota, btrfs, and matrix work.
- Project review — review snapshot from 2026-09-26.
- dakota return-boot RCA — historical Phase-2 hang investigation.
- Phase-2 attach postmortem — historical debugging record.
- Phase-2 debug plan — historical hypotheses and resolution path.
- v0.3.0-beta release notes — release record and evidence status.
- v1.0.0 release notes — release goals and evidence checklist.
-
adr/— architecture decision records. -
specs/— detailed migration proposals. -
experiments/— dated research notes and implementation experiments. -
evidence/— checked-in evidence summaries. -
experiments/evidence/— experiment artifacts and provenance. -
screenshots/— UI walkthrough images. -
Use status.md and release instructions for current verification and release decisions. Use dated plans and investigations for context, not as substitutes for those sources.