Open Continuity Protocol

Continuity without a universal dossier

AI systems accumulate useful context, but that context is commonly trapped inside one provider, flattened into an archive, or copied into an oversized prompt. OCP defines a portable layer for moving selected, structured records between systems.

The protocol is intentionally narrower than an identity system, personal database, agent runtime, or authorization framework. It preserves meaning and boundaries; it does not decide what is true or give a recipient permission to act.

What can travel

Context

Scoped statements and preferences, with review state, provenance, sensitivity, and lifecycle metadata.

Conversations

A message graph that preserves roles, branches, content parts, attachments, and declared losses.

Artifacts

Logical objects and independently verifiable representations, with custody, integrity, rights, and lineage.

Evidence

Source records that support or challenge context without being silently promoted to accepted state.

Three boundaries are non-negotiable

• Import is not acceptance. Imported material remains candidate data until an explicit review decision accepts it.
• No silent accepted-state writes. Clients submit update proposals; a review decision changes accepted state.
• Context never grants external-action authority. A package may inform a response, but cannot authorize a purchase, message, deletion, or other outside action.

Start with the lifecycle

A client requests the minimum context needed for a declared purpose. An authorizer approves a bounded subset. The provider issues a receipt and a recipient-bound package. Any proposed change returns through explicit review.