Deny by default
Every artifact is private to its creator until a deliberate grant exists. An error, ambiguity, or incomplete relationship lookup means no.
Security
One leaked document costs more than every feature earns.
Yobby treats trust as product behavior, not a compliance page. These are v1 invariants for hosted and self-hosted deployments—not future enterprise add-ons.
Immediate revocation
Protected content is authorized at the point of access. Removing a grant changes the very next request to denied.
Explicit deny wins
A direct deny beats owner, group, workspace, link, and public allows. The interface must show who can see an artifact and why.
Links are capabilities
Share URLs are high-entropy capabilities: independently revocable, optionally expiring, excluded from indexing, and protected from referrer leakage.
At rest
Encryption carries the tenant boundary.
Artifact blobs use per-tenant envelope encryption. One tenant's wrapped keys are useless against another tenant's data, and customer-managed keys are supported from the first artifact.
artifact versionAES-256-GCMtenant data keylocal root or KMS
BYOK from day one
External KMS is a v1 adapter, not a paid-tier promise.
Attributed audit chain
Grants, revocations, reads, downloads, and exports record the acting human, agent, link, or public principal. Public reads may be anonymous.
Invited member
The honest AI boundary
The librarian cannot invite itself.
A private drive is never read by AI until its owner invites Yobby and chooses a brain. That credential is encrypted, scoped, never logged, and removable. Agents—including the librarian—are principals with least privilege, never superusers.
01
Private means private.
Platform operators have no content path through the librarian.
02
Public means patrolled.
Public pages are explicitly moderated before availability and continuously rechecked, with takedown and appeal states.