Dimension · Operability

Operability

Can the stack be shipped and maintained as a dependable dependency?

What this page will show

planned

The lifecycle from launching an application to a healthy local-model response, then on through failure, recovery and change. No step is measured yet.

  • The runtime is available
  • The model is available
  • First-run provisioning succeeds
  • The model loads on the intended hardware
  • Health checks pass
  • Requests and streaming stay healthy
  • A failure is diagnosable
  • Recovery or fallback works
  • An upgrade or a model change remains safe

Operability is the gap between a model that runs on a laptop and a dependable application dependency. The lifecycle runs: the runtime is available, the model is available, first-run provisioning succeeds, the model loads on the intended hardware, health checks pass, requests and streaming stay healthy, a failure is diagnosable, recovery or fallback works, and an upgrade or a model change remains safe.

The first release follows that lifecycle from launching an application to a healthy local-model response: provisioning, readiness and model-load states, the failure and diagnostic path, and recovery and fallback.

run evidence

Operability has no payload schema yet; its lifecycle view is planned. Each committed run is listed here with its own reason. To read a bundle of your own, open it on the Performance page.