Provider Artifacts¶
This directory contains provider registry data used directly by OSCO runtime.
Purpose¶
Providers represent implementation surfaces (operating systems, cloud platforms, SaaS systems, identity providers, container platforms, databases, browsers).
Provider records are loaded by osco/registry.py and used by:
osco provider listCLI output- graph construction (
provider -> capabilityimplementsedges) - capability/provider consistency checks
Files¶
- providers.json: canonical provider registry
Validation¶
Validate provider model shape and capability provider references:
uv run scripts/validate_provider_registry.py
CI workflow: