GuideOpenCoven ecosystem
OpenCoven ecosystem
Where Coven ends, what the neighboring OpenCoven projects own, and which documentation is canonical.
2 min read
Where Coven ends
Coven is the local runtime and durable session substrate. These docs are canonical for its CLI, daemon, harness boundary, supported local API, and operational security model.
OpenCoven's neighboring projects build on or integrate with that substrate. They do not become part of the stable Coven contract merely because they share an organization or product vocabulary.
| Project | Owns | Go there when |
|---|---|---|
| Psyche | Canonical orchestration contracts, authority, execution bindings, durable transitions, and bounded surface ports | You need the protocol and authority model above runtime execution |
| Psyche Build | The multi-lane coding cockpit, worktree and pane orchestration, review and integration workflows, and optional Coven session surfaces | You need a human-facing cockpit for parallel agent or terminal work |
| Coven Cave | First-party application surfaces, mobile pairing, research and communication experiences, and product-level interaction design | You need Cave-specific UI, pairing, or application behavior |
| Coven Threads | Fail-closed authority gates for protected familiar surfaces and approval semantics | You need identity-surface mutation enforcement |
| Familiar Contract | The normative identity, purpose, authority, memory, and human-binding requirements for a familiar | You are implementing or evaluating familiar conformance |
| OpenCoven SDK | Experimental TypeScript clients and coordination packages | You need package-level client contracts rather than raw local API calls |
| Coven Memory | Read-only local and mobile memory browsing surfaces | You need the memory dashboard or its privacy boundary |
| Coven Runtimes | Runtime manifests, conformance tooling, and the accepted runtime registry | You are authoring or adopting a runtime adapter |
Documentation ownership rule
When two repositories describe the same boundary:
- The repository that implements or normatively specifies the contract owns the facts.
coven-docsexplains how the stable portion affects Coven users.- Generated inventories may be imported, but explanatory prose remains intentionally authored.
- Preview or experimental integration must stay visibly classified until its owner publishes release evidence.
For the runtime path, continue with Architecture. For unsupported foundations with explicit remaining gates, use Experimental.
Was this page helpful?No
Last updated on