Skip to content

Runtime providers

Hostwright routes runtime observation and lifecycle effects through the Runtime Provider API. The provider declares its identity, version, and capabilities; planning and admission reject unsupported requests before runtime effects.

  • Apple container CLI integration, with conformance coverage for versions 1.0.0 and 1.1.0.
  • Apple Containerization 0.35.0 through an authenticated out-of-process helper. Only the helper’s declared capability subset is available.

One project uses one provider for its current generation. Provider migration is explicit and fenced. The persistent local daemon and CLI use the same provider and state authority.

The interface covers provider metadata, capabilities, observation, and confirmed lifecycle execution. Execution uses current authenticated Control API 2.2 authority, durable intent, and ownership checks. Provider acceptance alone is not proof that an effect completed; Hostwright verifies observed postconditions before releasing reservations or ownership.

Provider capability does not imply release qualification. Each provider and version must pass the declared live, recovery, and cleanup evidence before it is included in the final compatibility matrix. See the core runtime-provider architecture and Compatibility.