Skip to main content
🟡 Status: DRAFT
Applies to: CXP-Core
Last updated: 2026-02-01
The registry is the “source of truth” for portable execution artifacts.

​
Registry responsibilities

  • store capsule versions
  • store receipts and audit data
  • provide discovery and lookup
  • enforce access control
  • support edge/offline caching

​
Deployment modes

  • cloud registry (central governance)
  • edge registry (low-latency, offline)
  • hybrid (edge cache + cloud sync)

​
This page is in progress

This section is actively being drafted for the CXP protocol. Content may change as the spec evolves and community feedback is incorporated.

​
What will be added here

  • Clear definitions and terminology
  • End-to-end examples (capsule → match → plan → execute → receipt)
  • Normative requirements for compliance (where applicable)
  • Security and safety considerations

​
Contribute

  • Propose changes via /community/cxp-guidelines
  • Submit issues or pull requests in the GitHub repository