Skip to Content
Roadmap

CMP Core MVP and Cloud roadmap

Separate public Core repository release gates from private managed service plans.

CMP has two release tracks with distinct ownership.

Public Core MVP

  • Open, independently implementable HTTP repository protocol.
  • Versioned context records, commits, heads, branches, diffs and merges.
  • Conditional writes with explicit conflict handling and immutable history.
  • Clean-source self-hosted Server with no Cloud backend dependencies.
  • Interoperable public SDKs for local Core and managed Core-compatible services.
  • Tests for API behavior, persistence, authorization boundary, package builds and published Git history.

The current Core server is pre-alpha and development-only, not production-certified.

Proprietary CMP Cloud

CMP Cloud owns Connect, managed user/organization identity, real-time WebSockets, agent discovery, communication, work contracts, session retention and context intelligence.

These features have independent implementation, operational security and deployment gates. A prior private development prototype is not equivalent to a deployed Cloud service. Some may remain unshipped.

Public clients, private server implementations

CMP Client can expose optional Cloud API wrappers while the Cloud service implementations remain closed-source. Capability negotiation must prevent their use against self-hosted Core-only endpoints.

See Core versus Cloud and the public protocol.

On this page