Write a Holiday On Call Runbook So Your Small Team Can Handle Outages Calmly

You are a site reliability engineer who helps small engineering teams stay calm during the holiday season, when traffic is higher and many people are away. I want an on call runbook for the weeks from Thanksgiving to New Year that a tired engineer can follow at 3 in the morning. Use only the details I give you. Do not invent services, alert names, vendor contacts, or SLAs. If something is missing, mark it [NEEDS INPUT].

Our product and the parts customers depend on most (checkout, login, API, dashboards): [CRITICAL PATHS]
Stack and hosting (framework, database, queue, cache, CDN, cloud provider): [STACK]
Monitoring and alerting tools we use and where alerts go: [MONITORING]
Team members available over the holidays, their time zones, and dates they are away: [ROSTER]
Status page, support channel, and who talks to customers during an incident: [COMMS]
Past incidents from this year with a one line cause each, if we have them: [PAST INCIDENTS]

Requirements:
1. Build an on call schedule from [ROSTER] with a primary and a backup for every day, clear handoff times in each person's time zone, and no one on primary for more than 7 days in a row.
2. Define 3 severity levels with plain examples from [CRITICAL PATHS], the expected response time for each, and when to wake the backup.
3. Write a first 15 minutes checklist: acknowledge the alert, check the status page and recent deploys, confirm customer impact, open an incident channel, and post a first update.
4. For each item in [CRITICAL PATHS], write a short playbook with likely causes, the checks to run, safe first actions (roll back the last deploy, scale up, fail over, disable a feature flag), and when to stop and escalate.
5. Use [PAST INCIDENTS] to add a known issues section with the fastest known fix for each.
6. Write 3 status page update templates under 50 words each: investigating, identified, and resolved. Keep them honest and avoid promising a fix time we cannot keep.
7. Add rules that protect people: no deploys on holidays without a second approver, a clear rule for when it is fine to wait until morning, and rest time after a night incident.
8. Write a short post incident review template that focuses on causes and fixes, not blame.

Deliverables:
1. Holiday on call schedule
2. Severity levels and response times
3. First 15 minutes checklist and per service playbooks
4. Known issues list and status page templates
5. Team protection rules and post incident review template