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].
[Visual 6.2 - One private-mesh boundary surrounds the work device and its surfaces. Tailscale identity sits on the boundary. A model-provider connection leaves from the coding CLI. A separate arrow labelled "private report" points to [email protected].]
Identity and revocation
Identity is the private mesh. There are no ROOK tokens to paste, store or rotate. Revoking a node means removing it from the mesh.
This does not mean the system has no outside dependencies. Tailscale coordinates mesh identity and connectivity, while the coding CLI reaches a model provider over the internet. The authoritative ROOK warehouse still remains on the work device.
What the boundary permits
Use the handbook to understand the current design and development system. Do not place production credentials in ROOK or treat it as a team deployment. Those are explicit operating limits, not a hidden checklist of security defects.
If you find a problem, follow the shared security reporting guidance and send details privately. Do not post a public issue before Achron has responded.
Keep reading
Return to the ROOK handbook overview or read the shorter ROOK product introduction.