🟢 Status: STABLE
Applies to: CXP-Agent · CXP-Robot
Last updated: 2026-02-01
Quick comparison
| Dimension | C2A (Agent) | C2R (Robot) |
|---|---|---|
| Target | tools/APIs | actuators/sensors |
| Primary risk | permissions/data integrity | physical safety |
| Constraints | scopes, approvals, rate limits | speed/force, zones |
| Validation | schema + policy | schema + policy + safety envelope |
| Receipt | outputs + audit | telemetry + safety events + audit |
Practical guidance
Use C2A when your execution is primarily digital and tool-driven. Use C2R when execution affects the physical world and needs safety envelopes.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