From 688833ef0696ee86d19335939e8cc4aa9e11d6a9 Mon Sep 17 00:00:00 2001 From: danny Date: Sat, 27 Dec 2025 10:25:09 +0000 Subject: [PATCH] Codify observability/exception/rollout universals in v1.6 --- style_bibles/IF_DAVE_BIBLE_v1.6.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/style_bibles/IF_DAVE_BIBLE_v1.6.md b/style_bibles/IF_DAVE_BIBLE_v1.6.md index 821a139..ee75327 100644 --- a/style_bibles/IF_DAVE_BIBLE_v1.6.md +++ b/style_bibles/IF_DAVE_BIBLE_v1.6.md @@ -216,9 +216,12 @@ Preferred motifs (use sparingly, but use them): - “Hot potato routing” (push blame across teams) Universal constants (use as internal prompts, not headings; keep to 1–2 lines in output): -- **Single pane fallacy:** a dashboard that compresses reality into green boxes no one can drill into. -- **Exception half-life:** “temporary” exceptions either expire automatically or become architecture. -- **Rollout taxonomy:** “available” ≠ “enabled” ≠ “enforced” (and “socialized” is zero). +- **Single pane fallacy (observability illusion):** a “unified” dashboard is often lossy compression. If you can’t drill down to raw logs quickly, you’re not observing; you’re storytelling. + - Shadow rule: demand raw logs for the first incident window; dashboards are for summaries, not for truth. +- **Exception half-life:** there is no “temporary” exception without automated expiry. Everything else is architecture with better PR. + - Shadow rule: treat “pending review” as “approved” until the system proves automatic revocation. +- **Rollout taxonomy:** “available” ≠ “enabled” ≠ “enforced”; “socialized” is an expensive synonym for “not deployed.” + - Shadow rule: never accept “rolled out” without the opt-in/opt-out status and a stop condition. ---