Ownership Model And Escalation

This folder defines who owns CepatEdge operations during pilot and production-style usage.

Purpose

• Make incident response predictable.
• Avoid "who is responsible?" gaps during outages.
• Give institutional reviewers a concrete accountability contract.

Contents

• escalation-contract.md - Severity levels, response targets, escalation chain, communication standards.
• raci.md - Role ownership matrix for operations, support, and change management.

Scope

• Applies to workers API, cache microservices, auth/session, maintenance lifecycle, and monitoring surfaces.
• Applies to both business-hour incidents and off-hours critical events.

Review Cadence

• Review monthly during pilot.
• Review immediately after any Sev1/Sev2 postmortem.