Add blameless-postmortem-incident-analysis-systemic-causes article

Author: webstackdev

.vscode/settings.json

@@ -113,6 +113,7 @@
     "pgbouncer",
     "PGRST",
     "pids",
+    "Plaso",
     "pleroma",
     "Poslovski",
     "Postg",

COVERS.md

@@ -157,3 +157,25 @@ Create an image of a hydroelectric dam with water flowing through controlled spi
 ### Prompt 5: Graceful Degradation Tiers
 
 Design a visualization of a building with multiple floors, each representing a degradation tier. The ground floor (emergency) is fortified and always lit. Higher floors (normal operations) have more features but can be "powered down" during stress. Power flows upward from a stable base. Style: architectural cutaway, blueprint meets modern infographic, warm to cool gradient from bottom to top, 16:9 aspect ratio.
+
+## blameless-postmortem-incident-analysis-systemic-causes
+
+### Prompt 1: The System Lens
+
+Create an image of a magnifying glass examining a complex system diagram (interconnected nodes and lines). Through the lens, the viewer sees system components highlighted; outside the lens, shadowy human figures are visible but not the focus. Style: technical illustration, clean lines, blue and white color scheme with subtle gold highlights, 16:9 aspect ratio.
+
+### Prompt 2: The Investigation Table
+
+Design an image of a large conference table viewed from above, covered with timeline cards, diagrams, and documents. Multiple hands point at different system factors (servers, pipelines, alerts) rather than at any person. Collaborative investigation aesthetic. Style: overhead view, warm lighting, paper and digital elements mixed, 16:9 aspect ratio.
+
+### Prompt 3: The Iceberg of Causation
+
+Illustrate an iceberg where "Human Action" is the small visible tip above water, and below the waterline are much larger layers labeled with systemic factors: "Process Gaps," "Tool Limitations," "Organizational Pressures," "System Design." Style: cross-section illustration, cool blue tones, clear labeling, dramatic scale contrast, 16:9 aspect ratio.
+
+### Prompt 4: The Root System
+
+Create an image of a single incident (represented as a fallen tree or withered plant) with an extensive root system visible underground. Each root represents a contributing factor, spreading in different directions, all connecting to the surface event. Style: botanical illustration meets technical diagram, earth tones with technical overlays, 16:9 aspect ratio.
+
+### Prompt 5: The Learning Loop
+
+Design a visualization of a continuous improvement cycle: Incident → Analysis → Learning → Improvement → Resilience → (back to start but at a higher level, spiral upward). The emphasis is on forward motion and growth, not punishment or backward-looking blame. Style: abstract/geometric, upward spiral motion, gradient from darker (incident) to lighter (resilience), 16:9 aspect ratio.

_TODO.md

@@ -186,6 +186,8 @@ To overlay an article title and published date on a cover image, use CSS positio
 - The title for a code block with yaml as the language type in "Sync wave annotations controlling resource application order" section of src/content/articles/argocd-sync-failures-gitops-debugging-troubleshooting/index.mdx is not displaying, it's showing the YAML language tag instead of the title. Also, the word "app" is being highlighted for some reason in this code block.
 - Code block formatting for 'text' language is very plain.
 - Mathjax not working on inline formulas: "Where $L$ is the average number of items in the system (queue depth), $\lambda$ is the arrival rate (requests per second), and $W$ is the average time in system (latency)." In src/content/articles/backpressure-load-shedding-admission-control-overload/index.mdx
+- Uppy, Tus server, whatever other server needed
+- Need a Q & A format to use in blameless-postmortem-incident-analysis-systemic-causes
 
 ## Reading position indicator