Team, files & horizontal spaces
This page groups the collaboration layer that sits above the shared platform boundary: team
owns membership, RBAC, and the onboarding brief; files owns the user-file vault (bytes, parsing,
quota, GDPR erase) and is the boundary vs the library/docs corpus; horizontal-spaces
owns purpose-partitioned spaces, the workspace switcher, purpose views, and first-session
non-coding onboarding. files depends on platform + economics (storage_limit_gb) and is
consumed by retrieval, surfaces, and trust; it does not own operator-imported third-party
corpus (that is library).
Capability status
| Capability | Status | Evidence |
|---|---|---|
team | Partial | Membership + RBAC + org read + onboarding brief; expertise/offboarding designed |
files | Shipped | User-file vault, R2 plane, parsing, admission, GDPR erase |
horizontal-spaces | Shipped | Purpose-partitioned spaces, switcher, purpose views, first-session onboarding |
team
team ships membership, RBAC, org-wide shared read, and the onboarding brief API
(GET /api/cloud/team/onboarding-brief). The expertise graph, disclosure-edge share, and
offboarding knowledge transfer remain designed-not-built. Team tier scopes memory promotion
edges and governance waiver visibility; see openspec/CAPABILITIES.md for the team catalog.
files
files is Tier 1 — it owns user uploads (bytes + parse + storage/admission + quota) and the
file recall family including GDPR erasure. It depends on platform + economics
(storage_limit_gb); retrieval and trust consume parsed user files. files does not
own the operator-imported third-party corpus — that is library, which holds no bytes.
horizontal-spaces
horizontal-spaces ships purpose-partitioned spaces, the workspace switcher, purpose views,
and first-session non-coding onboarding. It binds a purpose to a scope so the same belief base
can be projected into different lenses without duplicating memory.
Availability
| Surface | Tier | Residency | Notes |
|---|---|---|---|
zephr_files (MCP) | docs | deferred | List, stat, read Markdown, upload, and remove files |
GET /api/cloud/team/onboarding-brief | — | cloud | Team onboarding material (team member only) |
| Workspace switcher | — | local | Purpose view selection per scope |
Limits and failures
filesquota is enforced againsteconomics.storage_limit_gb; exceeding it blocks new uploads but never silently evicts existing bytes.- A GDPR erase on a user file removes the object bytes and the parsed recall; provenance anchors are tombstoned, not silently rewritten (see Trust).
- The expertise graph and offboarding transfer for
teamare designed-not-built: a departing member's disclosure edge is not yet re-shared automatically.
Related capabilities
platform (tenancy, admission, audit log), economics (storage quota), and library (the
no-bytes corpus boundary) own the platform side of this layer. See
Data flows: files and library for the upload→parse→recall path.