​
Visibility

Every twin and context store carries a visibility level, and access widens in steps: Isolation is defense-in-depth — enforced both in application code and in Firestore security rules.

​
Team-twin members

The most common form of sharing. A member is invited by phone or email and is fenced to exactly one twin:
A phone invite activates on the member’s first WhatsApp message to the twin’s number. A revoke is a hard deny from their next ask onward.

Team members

Full roster management.

​
Agents and API keys

An agent gets access by holding an sk-kaya-* key. Treat a key as the unit of access: mint one per agent or person so you can revoke it without disturbing anything else.
Agents reach your connected services through the credential broker rather than holding tokens themselves, so revoking the key cuts off everything at once.

Credential broker

How agents call Gmail and friends without ever seeing a token.

​
Public graphs

A knowledge graph can be published to a public URL without making its twin publicly answerable — those are separate decisions:
--ask will never flip a twin public on its own. Making a twin publicly answerable is always an explicit, separate act.