slo-engineering

name	slo-engineering
description	Define service-level indicators, objectives, windows, and error budgets from user-critical outcomes rather than infrastructure vanity metrics.

Slo Engineering

Use when this procedure is the primary professional method needed for the assignment.

Procedure

1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using request traces, availability/latency data, dependency behavior, and business criticality. Do not fill material gaps with assumptions when they can change the result.
3. Map user journeys to measurable good/bad events, choose statistically meaningful windows, set justified objectives, and connect breaches to explicit action.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

Quality gate

The SLO can be computed reproducibly and drives a concrete operational decision.