Status and limits

Five sections of this handbook described how ROOK works. This one answers the question you actually arrived with: does any of it exist, and can you have it?

ROOK is in active development. The core record, the work loop and the operator surfaces are real and in daily use. There is no installer and no signed distributable, so ROOK cannot currently be handed to another person. Both halves of that are true at once, and keeping them apart is the whole job of this section.

Why one dated page owns this

Moving facts should not be scattered through a handbook. Every other section explains something stable: two loops, cards, one record, the device model. Those explanations do not change when a release step lands. Status does.

So this section carries one dated reading, and the rest of the handbook links here instead of repeating a status sentence that would drift page by page. When you read a status claim anywhere else, check its date against this one. Later product work can change a status sentence without changing anything the earlier sections taught you.

What the handbook does not imply

Working components do not add up to an available product, and this handbook does not want you to infer that they do.

• A described mechanism is not a supported platform. The device model explains authority and connection; it does not say which machines ROOK runs on.
• Components that run for their builder are not a product another person can obtain.
• Completed internal work is not a production-readiness claim.
• Careful record design does not guarantee that every crash or retry resolves without you.

There is also no setup, installation, pricing, licence or release-date material anywhere in this handbook. Those pages would be misleading before a verified distribution path exists, so they are absent rather than approximate.

Next

Read the dated reading itself: current status.