( 05 ) limits

It will never do these.

Not promises of politeness - refusals enforced by the code paths themselves, each one tested. The stillness of this page is deliberate.

The four walls

WRITEnever erases or writes a disk without the exact DiskNumber:Serial confirmation you type. Non-USB, boot, system, and oversize targets are refused outright.

REBOOTnever restarts the machine - the boot handoff prepares the restart and asks; you perform it.

FIRMWAREboot order, BCD, firmware variables, Secure Boot, and BitLocker are read-only. Enumerated, never edited.

NETWORKno auto-update, no telemetry, no callbacks. The download is the whole program.

Straight answers

( q )Is OutOS an operating system I can install today?

No. OutOS the OS is not released - no beta, no image, no dates. What you can download is a Windows guided installer that writes an Ubuntu 26.04 live USB safely. That is the first real artifact of the project, and the only one.

( q )Why does Windows warn me when I run the launcher?

Because the scripts are unsigned - there is no EXE and no code-signing certificate yet. SmartScreen is doing its job. The trade: everything is plain text. Open the launcher and the PowerShell scripts in an editor and read them before running.

( q )Can it erase my Windows disk by accident?

The writer refuses any disk Windows marks as boot or system, refuses non-USB bus types, refuses disks larger than the removable range, and refuses any serial that does not match what you typed. All four refusals are covered by tests, and the write path was validated on real hardware. Nothing protects against typing the serial of the wrong USB stick on purpose - read what you type.

( q )Will my Bluetooth keyboard work after reboot?

Assume no. Pairing keys do not migrate from Windows to a live Ubuntu session. Preflight flags this, and the staged checklist repeats it: have a wired or 2.4 GHz dongle keyboard ready before you restart.

( q )Does the installer download Ubuntu for me?

Not in MVP1. You provide the ISO and its SHA256SUMS file locally; the installer proves they match before anything else happens. A failed checksum stops the flow with no override.

( q )What does "pre-release" actually mean here?

It means this is an engineering build for testing the installation experience: no auto-update, no telemetry, no AI features, no signing. It also means these pages mark every capability as proven, in-build, or planned - and a claim without evidence does not get printed.