Presence and collaboration
Presence and collaboration help people and agents see who is in the vault and what is changing. In the full KB-1 experience, Cloud coordinates the shared session boundary while the vault engine remains the content authority.
What presence means
Section titled “What presence means”Presence is live session state: who is connected, where they are focused, and which editor cursor or selection they are broadcasting. It is not the durable copy of the note.
A presence problem can make teammates disappear from the UI even when file content is still safe on disk.
What collaboration means
Section titled “What collaboration means”Collaboration is the shared editing path for a note. The editor session and the daemon coordinate document updates, then the daemon materializes durable content back to the vault files.
For self-hosted vaults, your machine still owns the durable file write. For Hosted vaults, KB-1 operates the daemon that owns the write.
By mode
Section titled “By mode”| Mode | Presence and collaboration |
|---|---|
| Local-only daemon | Local app and local agent workflows; no Cloud org presence. |
| Self-hosted full experience | Cloud coordinates authenticated shared sessions; self-hosted daemon owns content. |
| Hosted full experience | Cloud coordinates shared sessions; Hosted daemon owns content under KB-1 operation. |
Common failure split
Section titled “Common failure split”When collaboration looks wrong, separate these questions:
- Can the user sign in?
- Is the user an organization member?
- Can Cloud reach the daemon or Hosted runtime?
- Did the edit reach the durable vault file?
- Is the browser showing stale presence state?
That split keeps access, routing, presence, and durable content bugs from being mixed together.