SLO documents that product managers actually annotate

We ask product partners to initial explicit exclusions—features under beta flags, batch replays, or partner-specific throttles—so error budgets stop being engineering monologues. The second paragraph covers visualization: Grafana rows are labeled with customer journeys, not microservice pet names. That small rename reduces confusion during joint reviews. Third, we explore multi-window burn policies as negotiation objects. Each window is tied to a stakeholder who can authorize temporary capacity during marketing events. Finally, we store annotated PDFs beside Git-tracked Markdown so historical context survives dashboard refactors.