the software / concept visualizations - not the shipped product

You say it. It asks. Then it acts.

Five concept frames of what OutOS is being built toward. Illustrations, not screenshots - the shipped artifact today is the guided installer.

OS. outOS ( ask-first: on )

›

outOS asks

move 214 files -> /archive · delete nothing

denyallow once

The command surface: every privileged action crosses an approval you can see.

OS. outOS installer ( nothing written yet )

preflight - machine scanned

image verified - sha-256 match

handoff bundle staged

write - locked behind your token

ConfirmTarget 2:A1B2C3D4E5F6 writes only after your exact disk + serial

The guided install: three green stages, and a fourth that waits for you.

OS. outOS recovery ( planned - not built )

image A - running OutOS on Fedora Atomic / bootc

⟲

image B - previous always bootable - one command back

Rollback by design: the future base keeps yesterday's OS one boot away. Planned, not built.

OS. outOS voice ( lab only - planned )

● "close everything except the editor"

outOS asks

close 6 windows · save 2 unsaved files first

denyallow once

Voice is a modality, not a bypass: spoken commands cross the same approval gate, with the microphone indicator always visible. Lab-only, planned.

OS. outOS ledger ( planned - the audit trail )

intent: archive screenshots -> did: moved 214 files

intent: install editor -> did: 1 package, approved 14:02

intent: close windows -> did: 6 closed, 2 saved first

every row: what was asked vs what really changed

The ledger records what actually changed - not what the assistant meant. Intent and effect, side by side. Planned, not built.