Error-Budget Feature-Freeze Trigger to Linear

This is the decision-and-act half of error-budget management. It evaluates whether current Datadog burn will exhaust the budget before the window resets, and if so it converts that signal into a concrete, trackable action: a feature-freeze ticket in Linear with the math attached.

Use it when your team has agreed on an error-budget policy ("if we're projected to blow the budget, we stop shipping features and fix reliability"). This automates the trigger so the freeze is declared on data, not on whoever happens to notice.

1. 1A schedule runs the check several times a day.
2. 2It reads the SLO's remaining budget and burn rate from Datadog.
3. 3A logic step compares the projected exhaustion date against the window-reset date; it only proceeds when exhaustion lands before reset.
4. 4When the freeze condition is met, it creates a high-priority Linear issue titled with the service and projected date, includes the burn math in the description, and assigns it to the service owner.
5. 5It posts a short Slack notice linking the Linear issue so the team sees the freeze immediately.