Boundaries you can understand
What the alpha assumes, what approvals mean, and how to report concerns.
Documentation for Nookins 0.42.1-alpha.1 · Public alpha
An owner-operated alpha
Nookins assumes a trusted owner and operating-system administrator. It is not a hostile multi-tenant sandbox. The alpha can contain defects; configuration and supported platforms may change. A hosted signup service is not shipped.
The source repository is private. These guides do not promise repository access or a public issue tracker.
Each Nookin has its own boundaries
A Nookin has its own identity, memory, workspace, and permissions. Routing a conversation does not grant new abilities. Links to other Nookins are explicit; a friendly name or a shared group does not imply shared access.
The primary Nookin has owner administration capabilities only in the authorized context. Groups, delegation, and background work do not inherit those powers simply by involving the primary agent.
Approval and evidence
When an operation needs approval, review the exact proposed change. A request for clarification is not approval. A model's confident statement is not evidence that a write or delivery succeeded. Current authorized records and effect receipts take precedence over recollection.
Messaging and private data
WhatsApp relies on an unofficial integration and can break or carry account-policy risk. Pair in your own session. Never post QR codes, credentials, or private conversation archives in feedback.
Private security reporting
For ordinary bugs or questions, use feedback. For a possible vulnerability, use that form only to request a private contact channel, optionally including your contact address. Do not include exploit details or sensitive data in the initial request.
Feedback is reviewed by the owner; no response time is guaranteed.