Capability domains
The core belief circuit is documented under Core capabilities and the platform foundation under Platform features. This section closes two families that the baseline leaves uncovered as discrete product surfaces:
- Governance — the guard, fleet, and observability surfaces that make memory and review
accountable:
governance,defect,fleet,sync,team,files,horizontal-spaces,review-intel,progress, andpulse. - Integrations — the surface-area that connects Zephr to the outside world:
external-signals,onboarding-import,workspace-sync,autonomous-agents,agent-adapter-sdk,agent-plugin-interop,intelligence-gateway,universal-capture,workspace-product-surface,personal-agent-hosts,agent-envelope-dispatch,fleet-connect, andnative-host-plugins.
Each page below groups related capabilities and states, per capability, whether the behaviour
is shipped, evolving (ships with a documented gap), partial (a slice ships, the rest
is designed-not-built), or designed-not-built. The canonical status oracle for every
capability is openspec/CAPABILITIES.md; this index groups for the reader and never adds a
claim the map does not already carry. Shared boundaries — identity/admission, persistence,
trust, continuity, security/privacy, economics, observability, and recovery — are documented once
in the Architecture and Data flows sections
and are referenced, not restated.
Status vocabulary
| Label | Meaning for a grouped page |
|---|---|
| Shipped | The capability is live in production and the public contract is frozen. |
| Evolving | The surface ships but an interface, tier, or deployment mode is still being expanded; the gap is documented. |
| Partial | A slice ships; the remainder is designed-not-built and is called out per capability. |
| Designed-not-built | Fully specified in openspec/specs/<id>/spec.md but not implemented or exposed. |
Pages
| Page | Family | Coverage |
|---|---|---|
| Governance & defect | Governance | Constraint authoring/enforcement + defect immunity & decay; the post-failure accountability band |
| Fleet & sync | Governance | MCP profile portability and per-client projection, plus unified WorkspaceSnapshot reconciliation |
| Team, files & horizontal spaces | Governance | Membership/RBAC/onboarding, the user-file vault, and purpose-partitioned work spaces |
| Review intelligence, progress & Pulse | Governance | LLM-augmented review, evidence-anchored progress graph, and the product observability surface |
| External signals & onboarding import | Integrations | CI/external signal ingress and the cold-start corpus / partner import engine |
| Agent integration | Integrations | Background agents, adapter SDK, plugin interop, inference gateway, universal capture, envelopes |
| Workspace, hosts & plugins | Integrations | Workspace verb contracts, personal-agent hosts, fleet connect, and native host-plugin parity |
Honesty and scope
These pages carry the same openspec/CAPABILITIES.md truth oracle as the core and platform
sections. They describe what the system does, not what an adapter or plugin author might
infer it could do: every non-shipped item is flagged, every egress is reviewed and labelled
with a public service class, and no private route, credential, tenant identifier, or
infrastructure coordinate is exposed. For verification, review-state, and recall-gating semantics,
see Trust; for session and cross-device handoff, see
Continuity.