Deterministic Consent Gate: analytics remain disabled until explicit opt-in. No third-party trackers are loaded.

Specification de capacite

Threshold-based budget stop-loss alerts

FinOps Stop-Loss

Threshold-based budget stop-loss alerts defines a core capability outcome delivered by FinOps Stop-Loss, including implementation intent and execution coverage.

DORA

Objectif

Translate FinOps Stop-Loss intent into a concrete capability stream that can be executed, measured, and accepted by the delivery team.

Contexte de perimetre

Budget policy mesh with automated threshold actions and escalation workflow.

Entrees

- Current-state architecture and operating model

- Approved bundle scope and target compliance obligations

- Delivery constraints, timeline, and responsible owners

Sorties

- Implemented capability increment with ownership mapping

- Execution notes and evidence pointers for review

- Operational handover requirements for production use

Criteres d acceptation

- Capability can be demonstrated in a controlled walkthrough

- Owner, scope, and change boundaries are explicit

- Linked controls and evidence references are complete

Notes de preuve de conformite

- [DORA] Capability execution mapped in FinOps Stop-Loss control evidence

Schema de specification

Role responsable

Capability Stream Owner

Validation finale

Product owner and platform lead

Politique de versioning

Revisioned per release with backward-compatibility notes

Cadence de revue

Sprint review and monthly capability maturity checkpoint

Retention des preuves

Operational evidence retained for at least 12 months

Sections obligatoires

- Capability objective and intended business outcome

- Technical scope and dependency matrix

- Implementation steps and ownership mapping

- Validation checklist and acceptance evidence

- Operational handover and support model