Paged Context Protocol, or PCP, stores, organizes, and retrieves durable context across applications, sessions, and models. It represents content as stable Pages, immutable Revisions, Scopes, Relations, and Provenance, then uses bounded queries to bring selected material into the current task.
PCP can serve one application or multiple tenants contributing to different Scopes under one Identity. The product above it still decides what to record, how to present it, and which results enter the working context.
Protocol objects
Current implementation
The repository maintains both the protocol and its Rust implementation: a SQLite Store, embedded and remote clients, Unix socket RPC, Runtime, CLI, MCP server, Console, maintenance coordinator, and read-only facility observation.
The current implementation includes exact, text, graph, temporal, and automatic search; Runtime semantic search and intent matching; Summary, Topic, Validity, Relation, Provenance, archive and restore, lossless packing, and retention planning. Ordinary tenants use PcpTenantApi; Runtime maintenance and local administration use the privileged PcpApi superset.
Status and boundaries
The current release is v0.8.0-draft. Protocols, interfaces, and Store formats may still change. A v0.7 Store cannot be opened as v0.8; migration requires a new Store and re-import from source material retained by each tenant.
External chats, media, and domain objects remain with the host application; PCP stores their durable context and source references. Semantic search requires an explicitly configured Provider and reports unavailable when none is configured.