Adapter packages
What you'll find here
The craik.adapter_package contract — runner adapter distribution
metadata that describes how an adapter loads and what surfaces it
exposes.
Distribution metadata, not authority.
Adapter packages do not grant runtime authority. Policy envelopes and capability grants still decide what a run may do.
What it records
Adapter identity & package version
Adapter implementation entrypoints
Capability surfaces
Exposed by the adapter.
Compatibility
Craik · runner mode · Python · platform.
Linked runner metadata & plugin descriptors
Docs · provenance · version constraints
Expectations
- At least one entrypoint.
- At least one capability surface.
- Docs and provenance.
- Version-like package version.
- Semantic-version-like package and Craik compatibility versions.
- Compatibility names at least one supported runner mode, Python version, and platform.
Compatibility is an execution boundary, not a suggestion. Adapter
packages must declare the Craik versions they support as
MAJOR.MINOR.PATCH values, plus the runner modes, Python versions,
and platforms used for validation.