Skip to main content
🟢 Status: STABLE
Applies to: CXP-Core
Last updated: 2026-02-01
Matching prevents unsafe portability.

Inputs

  • capsule requirements (skills, constraints, dependencies)
  • target capabilities (tools, hardware, safety features, limits)
  • environment constraints (site rules, calibrated sensors)

Output: match result

  • green: compatible
  • yellow: compatible with mitigations
  • red: incompatible

Why matching is core to safety

Portable execution is powerful—but portability without matching causes failures and unsafe behavior.

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