Platform features
Zephr's platform is the foundation layer beneath product semantics: tenancy boundaries, credential planes, scope bindings, storage contracts, and the interface surface through which humans and AI agents interact with the system.
This section documents each platform capability with an honest status classification.
Status classifications
Every requirement and feature in this section carries one of seven status labels:
| Status | Meaning |
|---|---|
| Shipped | In production, tested, and the source of truth for behaviour. |
| Evolving | The foundation ships but a documented gap remains — the system works, but not all requirements are satisfied. |
| Planned | Spec-complete and reviewed, but not yet implemented or wired. The design exists in openspec/ as a tracked change. |
| Dark | Implemented in code but not published, documented, or exposed to users. May be gated by a feature flag or an internal-only code path. |
| Unsupported | Known to be absent or explicitly out of scope. No implementation exists and none is planned for the current release. |
| Deprecated | Still recognizable for migration, but no longer recommended. |
| Unverified | Evidence is insufficient to make a stronger public claim. |
Platform capabilities
| Capability | Status | Page |
|---|---|---|
| CLI, MCP server, daemon, editor integration | Evolving | Surfaces |
| Agent runtime — packs, tool tiers, context injection | Evolving | Agent runtime |
| Hosted tools — BYOK/metered external providers | Evolving | Hosted tools |
| Extensions — manifest, registry, hooks, signals | Evolving | Extensions |
| Universal integration — HTTP surface, host packs | Planned | Universal integration |
Key identifiers
The platform uses the following canonical IDs throughout the codebase. These are not user-facing — they are the machine-readable contract between packages.
MCP tool tiers
The generated MCP tool reference is canonical for exact membership and residency. The current tiers are:
core: activate, constraint, get_observations, how_to_obtain, recall, remember, session, status, sync_status, timeline, tools_execute, tools_search.search: search, grep, lsp, why, verify, graph_query.docs: docs and files.review: rules, admin, review, review_usage.extension: verified extension tools; no default grant.hosted: the external-provider catalog; no default grant.
Role policy controls tier grants. docs_writer is the documented role for docs-tier access; role IDs in configuration are opaque identifiers, not preset names.
Hosted tool IDs
| Tool ID | MCP name | Provider |
|---|---|---|
context7 | context7_call | Library documentation |
firecrawl | firecrawl_scrape | Web scraping |
tavily | tavily_search | Web search |
browser | browser_render | Browser snapshots |
sentry | sentry_query | Error tracking |
github | github_api | GitHub API |
linear | linear_search | Linear issue tracker |
supabase | supabase_query | Supabase database |
Credential modes
| Mode | Meaning |
|---|---|
byok | User supplies their own API key; metered at provider cost |
hosted | Zephr-supplied credential; metered at published retail rate |
Related references
- Security and privacy — trust model, scope binding, admission
- Architecture — repository structure and design docs
- Configure your client — MCP server configuration
- Reference — MCP tool API contracts