Skip to main content
🟢 Status: STABLE
Applies to: CXP-Core
Last updated: 2026-02-01
A context capsule is the unit of portability in CXP.

​
What a capsule contains

  • Goal: what should happen (intent)
  • Constraints: what must not be violated (limits, zones, approvals)
  • Policy hooks: what checks must run
  • Parameters: tuned values, offsets, safe defaults
  • Provenance: origin, confidence, test environment
  • Optional signatures: who published it

​
Minimal capsule example

{
  "cxp_version": "0.1",
  "capsule_id": "cap_pick_place_01",
  "name": "Pick and place (validated)",
  "goal": { "type": "pick_place", "object": "bin_item" },
  "constraints": {
    "max_speed_mps": 0.25,
    "max_grip_n": 18,
    "no_go_zones": ["human_zone"]
  },
  "skill_params": { "approach_offset_m": [0, 0, 0.08] },
  "provenance": { "tested_in": "sim+warehouse_A", "confidence": 0.86 }
}

​
Why capsules (instead of copying “models”)

Capsules standardize execution context and constraints—independent of how you learned them.

​
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