Observed provider readiness
Healthy, fresh and ready are operational observations. Selecting a model or profile does not imply started or loaded.
In development
Machine & runtime layer
AERIF Runtime
Provider readiness and lifecycle, with explicit ownership.
The foundation
A distinct responsibility.
Runtime owns provider/model lifecycle, readiness, ownership and resources. Provider identity, model identity and operational state remain separate. Observing an already-running provider does not grant permission to stop it. Provider-specific Frankenstein implementation stays adapter-local.
Explicit lifecycle ownership
External-running and Runtime-managed ownership are distinct. Logical authority release leaves an external provider running.
Explore the foundations
Core, Runtime and Graph have different responsibilities. Their accepted implementation baselines do not imply consumer downloads or suite-wide adoption.
Architecture