dannystocker/re-voice
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Codify observability/exception/rollout universals in v1.6

Browse source
This commit is contained in:
danny 2025-12-27 10:25:09 +00:00
parent 8a6a83e306
commit 688833ef06
1 changed files with 6 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
style_bibles/IF_DAVE_BIBLE_v1.6.md
View file

@ -216,9 +216,12 @@ Preferred motifs (use sparingly, but use them):
- “Hot potato routing” (push blame across teams) - “Hot potato routing” (push blame across teams)
Universal constants (use as internal prompts, not headings; keep to 1–2 lines in output): 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. - **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.
- **Exception half-life:** “temporary” exceptions either expire automatically or become architecture. - Shadow rule: demand raw logs for the first incident window; dashboards are for summaries, not for truth.
- **Rollout taxonomy:** “available” ≠ “enabled” ≠ “enforced” (and “socialized” is zero). - **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.
--- ---