Concepts
- Manifest API compatibility: the validator accepts only vcp.shyda.ai/v1alpha1.
- SDK compatibility: vega.sdkVersion must contain the installed SDK version according to standard Python specifiers.
- Platform compatibility: manifest declarations may limit manufacturers, models, variants, robot types, architectures, operating systems, ROS distributions, compute platforms, and required features.
- Action version compatibility: versions_compatible compares normalized versions for equality.
Rules
A package MUST declare a compatible SDK range. The validator rejects invalid ranges, unsupported API versions, malformed schemas, paths escaping the package root, unknown resource references, duplicate Action IDs, and inconsistent execution declarations. The current manifest validator accepts only Python Provider runtime declarations.
Compatibility matrix
| Manifest API | SDK installed | Declared SDK range | Result |
|---|---|---|---|
| vcp.shyda.ai/v1alpha1 | 0.1.0 | >=0.1.0,<0.2.0 | Compatible |
| vcp.shyda.ai/v1alpha1 | 0.2.0 | >=0.1.0,<0.2.0 | Incompatible |
| unsupported value | any | any | Incompatible |
Migration and deprecation
The repository does not publish a VCP deprecation schedule or manifest migration framework. Treat the manifest API version and bounded SDK range as the current compatibility controls. A future API version MUST be documented with explicit migration guidance before a Provider claims support for it.
Example
vega:sdkVersion: ">=0.1.0,<0.2.0"provider:runtime: python
Run vega-capability validate . in the Capability package root before installation. This validates the package without importing the Provider or starting Vega Runtime.