What problem does it solve? Teams running self-hosted products often lack a consistent backup and disaster recovery doctrine, leading to unclear recovery objectives, untested backups, and offsite strategies that require code changes when infrastructure evolves. ## Core Features & Use Cases - Four-Tier Backup Model: Defines T1 ZFS snapshots, T2 host-local restic, T3 removable USB, and T4 cloud offsite, all encapsulated behind a single OFFSITE_BACKEND environment variable. - RTO/RPO and Drill Cadence: Specifies how to declare per-product recovery objectives in a BCDR plan and enforce weekly restore-tests, quarterly BCDR drills, and compliance sweeps. - Gate Enforcement: Documents gates G112-G116 that block release-train promotion without backup evidence, successful restore tests, and offsite backends for production trains. - Use Case: When adding a new product to a single-host RAID server, use this doctrine to configure daily T1+T2 backups with WARN-level offsite gates, then flip to blocking enforcement when USB drives or cloud storage arrive. ## Quick Start Ask the agent to define a backup and BCDR strategy for a new product using the four-tier model and OFFSITE_BACKEND contract.