Re-checked 12 August 2026

This is a dated reading of the pinned ROOK source snapshot from 10 August 2026. It is not a release announcement, and it carries no date for one.

Everything the earlier sections described was written from working software. That sentence is easy to misread in one direction, so this page reads it out row by row: what exists and runs, what happened once, what you cannot have, and what is merely intended.

ROOK at the evidence boundaryfour bands, re-checked 12 August 2026 — not a release announcement
Built and runningthe contract, the loop, the surfaces, the fleet, dictationok
Real, in use, and the basis for everything the earlier sections explain. ROOK's own work loop builds ROOK.
Demonstrated oncea signed development build on a real iPhone, 2 August 2026open
Live off a real server over a private mesh. A single event on the builder's own hardware — a demonstration is not a distribution.
Unavailableno installer, no signed distributableblocked
ROOK cannot currently be handed to another person. There is no just-open-it path hiding behind the earlier pages.
Plannedpackaging and distributionopen
No date, no sequence you can rely on, and no commitment about what a first available version contains.
thenThe builder has all of it running across a fleet. A reader has a handbook and nothing to install. Those two positions are separated by packaging, not by permission.

Of the platforms, macOS and iPhone are what has run. Windows is not supported.

A dated reading of the pinned source snapshot from 10 August 2026. Everything a reader would need in order to obtain ROOK sits below the third line.

Built and running

At the reviewed boundary these are real, in use, and the basis for everything the earlier sections explain.

AreaState
The contract, the on-device server and the warehouseBuilt and running
The work loop, including watching and answering decision cardsBuilt and running
The desktop dashboard and the phone appBuilt and running
The fleet model and the workspace selectorBuilt and running
On-device voice dictationBuilt and running

ROOK's own work loop builds ROOK. The archive-and-search examples in this handbook are the same mechanism running on the same machines.

Two boundaries belong beside that list. Dictation is input only: audio stays on the device and never enters the record or the contract, and nothing is spoken back to you. And everything described here treats the decision card as the interaction unit; this handbook is not a description of a free-text conversational layer, in either direction.

Demonstrated once

ROOK has run on a real iPhone: a signed development build, live off a real server over a private mesh, on 2 August 2026. Not a distributed app.

That is a single event on the builder's own hardware, and it is recorded here because it is the strongest available evidence for the phone surface, not because it moves ROOK closer to you. A demonstration is not a distribution.

Unavailable

There is no installer and no signed distributable yet. ROOK cannot currently be handed to another person.

This is the load-bearing fact of the whole section. Running ROOK today means a server process on each work machine and a configured private mesh, set up by the person who built it. There is no version of that you can obtain, and no "just open it" path hiding behind the earlier pages.

The honest comparison is short. The builder has all of it running across a fleet. A reader has a handbook explaining how it works and nothing to install. Those two positions are separated by packaging, not by permission.

Planned

Packaging and distribution are planned work. Nothing follows from that word here: no date, no sequence you can rely on, and no commitment about what the first available version contains.

Of the platforms, macOS and iPhone are what has run. Windows is not supported.

What this page deliberately does not say

It makes no claim about public availability, release timing, pricing or a licence. It does not turn completed internal work into a production-readiness claim, and it does not describe ROOK as suitable for a team; single operator per device is a design decision rather than deferred work.

Next

One question is left, and it is the one a careful reader asks last: what can this be trusted with today, and where do you report a problem? Finish with trust and reporting.