Components & providers
Select exact optional capability in the operating graph, then let its company-local target apply and own the result.
Components vs. execution providers
- Component package — An immutable package implementing a company capability such as an integration, automation service, data system, operator surface, or execution adapter.
- Execution provider — An adapter behind a provider-neutral execution binding. A company may select Codex or another exact provider package without making that provider a kernel concept.
Selecting a component
Selection is a company-state change, not a side effect of browsing a catalog or downloading bytes.
- Resolve exact bytes — Resolve an immutable component artifact through the registry and verify its identity and digest. The registry owns distribution only.
- Author the desire — Record the exact package, component template, configuration, target, and desired presence in the operating graph.
- Apply locally — The selected component target validates the desire, applies it, and reports its own status. A package may contribute an API, files, or optional interface for its domain.
- Observe actuality — Inspect component-owned status and any external service state. A successful artifact download is not proof that the capability is active.
What to check
- Artifact identity — Pin the publisher, package name, version or selector, and digest required by the desire. Avoid mutable source-tree dependencies.
- Authority and configuration — Review the package’s declared contracts and the exact configuration accepted by its target. There is no generic permission envelope that can substitute for domain-specific checks.
- State ownership — For important state or external promises, understand the owning component’s export, recovery, and replacement behavior.
Removing or replacing a component
Change the graph desire to select a replacement package or request absence. The owning target reconciles that change. Any state export, migration, external cleanup, or credential revocation follows the component’s domain contract; the registry does not perform it.
Configuring providers
Platform-origin credentials remain in platform custody until the provisioning handoff. Company-local provider material is accepted by the package that consumes it, through that package’s API, files, or optional settings surface.
Execution bindings select exact provider and harness references. The runtime routes execution mechanically; provider-specific fallback, authentication, and model behavior belong behind the selected adapter.