SYSTEMA CONSTRUCTUM

Accepted ontology entry

service-level-objective

A service-level-objective (SLO) is a formal reliability target expressed as a quantified measure — such as 99.9% uptime over a rolling 30-day window — that defines the acceptable boundary of service behavior. It serves as the contractual a…

ACCEPTED THINGcmsinft2b00jqnobphwthgc0i

Definition

A service-level-objective (SLO) is a formal reliability target expressed as a quantified measure — such as 99.9% uptime over a rolling 30-day window — that defines the acceptable boundary of service behavior. It serves as the contractual anchor between providers and consumers, decomposing into service-level indicators (SLIs) for measurement and service-level objectives (error budgets) for tolerance. Its persistence mechanism is organizational documentation, monitoring systems, and the contractual agreements that enforce compliance. [formal: servile | substrate: behavior | horizon: a moment | explicit: yes | epoch: 0.01]

Why it is in scope

A service-level-objective is a human-made target that specifies the desired level of reliability, availability, or performance for a service. It is a formal commitment expressed as a quantified metric over a time window — the contract between service providers and users about what 'good enough' means. Built to persist through documentation, monitoring tooling, and organizational practice.

Names and aliases

Relations from this entry

  • cmrwiv1rn00a8soacg5vdpiogINSTANCE_OF →

    An SLO is a specific kind of metric — a quantified measure defining an acceptable level of service performance. It files against 'metric' as the nearest kind of measurable target.

Relations to this entry

  • cmsimrhe700hrnobp5skprwiu← DERIVED_FROM

    Error-budgets were derived from service-level-objectives: an error budget is the acceptable amount of failure derived by subtracting the SLO target from 100%. SLOs came first — error budgets are a direct consequence of SLO targets. Which existed first? SLOs. SLOs fed into error-budget.

Record identity

Created
Aug 7, 2026, 7:54 AM UTC
Content hash
72c64da7eb10f77e69393b8ef761b72bddffea17b85ccccdd0e890d62c8dbe92

Open a related act record