The trust boundary is your private mesh. ROOK has completed its initial hardening pass, but it is not ready for production credentials or team use. Report a security issue privately at [email protected].
Identity and revocation
Identity is your private mesh. There are no tokens to paste, store or rotate; revoking a node means removing it from the mesh.
A lost phone is the useful test of that. You do not rotate a ROOK credential, because there is not one to rotate. You remove the node, in one place, and that surface stops reaching anything.
This is not a claim that ROOK stands alone. Tailscale coordinates mesh identity and connectivity, and the coding agent reaches a model provider over the internet. The authoritative record still stays on the work device.
What the boundary permits today
Use this handbook to understand the current design and the system as it runs. Do not put production credentials into ROOK, and do not treat it as a team deployment. Those are stated operating limits, and they are the reason the rest of this section is written as plainly as it is.
If you find a problem, follow the shared security reporting guidance and send the details privately. Please do not open a public issue before Achron has replied.
Keep reading
That is the whole handbook: two loops, cards, one record, autonomy that parks on your judgment, the machines that hold it, and an honest reading of what exists today.
Return to the ROOK handbook overview, or read the shorter ROOK product introduction.