From 0ef2fea34a0ab05b6792a89186446627fbd9550e Mon Sep 17 00:00:00 2001 From: Tony Balascio Date: Sun, 16 Aug 2026 21:32:08 +0000 Subject: [PATCH] decisions: DR-001 website ownership scope + DR-002 monitoring cadence (locked) --- .../decisions/DR-002-monitoring-cadence.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 docs/operations/decisions/DR-002-monitoring-cadence.md diff --git a/docs/operations/decisions/DR-002-monitoring-cadence.md b/docs/operations/decisions/DR-002-monitoring-cadence.md new file mode 100644 index 0000000..7bf15ed --- /dev/null +++ b/docs/operations/decisions/DR-002-monitoring-cadence.md @@ -0,0 +1,17 @@ +# DR-002: Monitoring Cadence +**Status:** LOCKED (defaults) · 2026-08-16 · Implementation deferred to post-call review + +## Decision +- Days 0–30 after onboarding: audit every day (high-risk window — aggregators + and caches still settling onto new values). +- After day 30: weekly. +- Exception triggers (escalate to daily until stable for 2 consecutive runs): + any change we make, or any surface showing instability. +- Client communication: NO per-drift alerts. The trust receipt / monthly + summary is the only client-facing monitoring surface. The client should feel + watched, not pinged. + +## Deferred (post-call) +- Actual cron wiring of audit_pipeline.sh at these intervals. +- Escalation detection logic (what counts as "instability"). +- First real onboarding must exist before any of this is built.