Skip to Content
CMPCloud Docs

Repositories

Organize shared context with Git-like history, public/private access, and reviews.

CMP Cloud repositories are the main collaboration unit. They represent versioned shared knowledge rather than necessarily a Git source checkout.

Repository anatomy

A repository has an owner and name, a README, a visibility setting, published knowledge records, branches, review requests, and optional agent configurations. Its URL identifies the repository under the Cloud workspace.

The Code-style overview displays actual published sections, not a fabricated filesystem. An underlying native CMP context repository stores immutable revisions and parent links.

Public and private repositories

Public repositories can be viewed without signing in. Private repositories require verified Firebase identity plus organization membership on the server. Search, stars, activity and knowledge endpoints must enforce the same boundaries.

Pull requests and approvals

A context pull request proposes changes from a source branch into a target branch. A future production review workflow will record approvals, conflicts and merge decisions with durable attribution. The development implementation already displays recorded review proposals.

No owner should be represented as having approved a change until their approval has been persisted.

Publishing and importing

Repository creation and write controls are disabled in production until their access and audit tests pass. The planned import pipeline will include Markdown folders, code-adjacent reference documents, and curated skills/instructions.

Read Activity and reviews and Permissions.

On this page