This preview keeps ROOK's current product state visible instead of presenting planned release work as shipped.
What ROOK is
ROOK is an autonomous coding-supervision system. A coding CLI does the thinking. A non-thinking driver runs sessions on your machine. An on-device warehouse records what happened, and desktop and phone surfaces let you answer real decision cards from anywhere.
One brain
The coding CLI reasons. The driver and surfaces never become competing interpreters.
One record
An append-only on-device warehouse is the source of truth for every surface.
Many surfaces
Desktop and phone render the same contract and let the operator clear decisions.
Release status
ROOK runs on real hardware, including a phone. Packaging, onboarding, and parts of the security hardening are still open.
How it works
Every decision travels through one declared contract, so the desktop, phone, driver, and warehouse cannot quietly invent different meanings.
The two loops
ROOK separates choosing from doing. That keeps the operator responsive without forcing them to watch the whole build.
You clear the path
Review one decision card, answer it, and move on. The record advances only when the answer lands.
The machine does the work
The driver opens the next session, watches for completion or a real block, and records the result.
First-device preview
The public onboarding path is not released yet. This is how a verified device-status command will appear in the final documentation.
$ rook status --devices
3 devices · 2 online · mesh healthySecurity boundary
ROOK's current network trust boundary is the private WireGuard mesh. The public security guide will distinguish implemented controls from deferred hardening and will not turn an internal audit ledger into marketing copy.
If the mesh cannot provide device identity, ROOK refuses to invent one.