QiraOS 2.0 is a bootable Linux distribution that starts straight into the Qira agent — a small image (about 13 MB) that reaches a working, self-testing session in a few seconds. This is what it is, what is proven, and what we do not claim.
Every company shipping AI agents shares one unsolved problem: when an autonomous system acts on a real computer, who authorised it, can you prove what happened, and can you undo it? The common answer today is a confirmation dialog and a chat log. Qira's answer is architectural. The language model converts a request into typed goals from a closed registry — and that is the entirety of its power. Trusted code plans the steps, classifies risk deterministically, checks human-created grants, executes with fixed arguments, verifies the effect against real system state, and records every action and refusal in a hash-chained ledger. Consequential changes are previewed before execution; low-risk reversible actions happen immediately. The model never authors a shell command, a download URL, its own permissions, or its own risk class.
QiraOS 2.0 puts that engine in charge of an entire machine. A stock Linux kernel underneath — the way ChromeOS and SteamOS are Linux — and the agent as the whole session on top. On every boot it self-tests: it reads real hardware state and verifies its own ledger before offering a prompt. This serial capture is from the actual image:
[ 1.12] Run /init as init process ██████╗ ██╗██████╗ █████╗ ██████╗ ███████╗ ██╔═══██╗██║██╔══██╗██╔══██╗██╔═══██╗██╔════╝ ██║ ██║██║██████╔╝███████║██║ ██║███████╗ ╚██████╔╝██║██║ ██║██║ ██║╚██████╔╝███████║ 2.0 A Linux kernel underneath. Qira as the session. QIRAOS-2-BOOT: engine present — qira 0.1.0 Self-test: Not readable: no battery found under /sys/class/power_supply chain internally consistent: 0 entries; empty ledger QIRAOS-2-ENGINE-OK Type what you want. The engine decides what happens.
Notice the self-test reporting no battery found inside a virtual machine rather than inventing a number. That is the house style throughout: where a mechanism is not wired, the system says so. The same style governs the evidence: the engine ships with a 52-case failure-path battery, a 27-entry goal-type matrix read from the goal registry (so an untested capability fails the suite itself), a 14-case shell-smoke suite, a 35-task battery run on real hardware, and a resolver evaluation passing ~115 of 116 cases — all re-runnable from the repository.
| System | What it is |
|---|---|
| QiraOS 1.x | A from-scratch research OS — its own kernel and userland — certified as an architecture proof (45 gates, 415 invariants, 0 failures) and feature-frozen. It is not distributed. |
| QiraOS 2.0 | A Linux-based distribution carrying the production Qira authority engine, built to run useful software and reach real hardware. The research kernel did not "become" Linux; 2.0 is a second track with a different job. |
The 2.0 preview is a live image: BIOS boot, unsigned, no installer — it runs from memory and never touches an installed system. There is no in-place conversion of an existing OS, because nobody can promise that honestly. The ledger's anchoring detects same-user tampering; it is not cryptographic anti-rollback. macOS distribution is currently a source build; a notarized installer is in progress. Android compiles to a signed APK but is not yet verified on a device. A Windows agent is only an early scaffold — the engine compiles for Windows but it is unrun and not a usable build yet.
QiraOS 2.0 is in gated early access — codes are personal, revocable, and checked server-side, and every release is published with its source commit, build record, and SHA-256.
Request or use an access code →