> Stack
The Compliance Stack
Incidents where regulatory requirements force architecture decisions that degrade performance and usability.
"The architecture wasn't designed to serve users. It was designed to survive auditors."
What this stack means
This stack tracks the necessary friction introduced by data privacy, residency, and security regulations.
Why this stack exists
Because organizations must prioritize legal compliance over engineering elegance.
▶ Common Failure Patterns
- •data residency complexity
- •audit logging overhead
- •GDPR deletion failures
- •compliance-driven architecture
- •policy paralysis
Prevention Checklist
- Design for compliance from day one, not as an afterthought.
- Automate compliance reporting and audit logging.
- Understand the difference between a regulatory requirement and a company policy.
Detection Signals
- Features delayed indefinitely because 'legal needs to review them'.
- Complex, slow data pipelines built solely to handle GDPR deletion requests.
- Database performance degrading due to excessive audit logging.
Related Categories
Related Stacks
Incidents in The Compliance Stack
Reference
The Security and Governance StackSecurity, Compliance and Audit
Retry Policy Tried Too Hard
"The chaos was predictable."
Pattern: compliance theater
Read Incident →
Reference
The Security and Governance StackSecurity, Compliance and Audit
Architecture Review Became Therapy
"The chaos was predictable."
Pattern: compliance theater
Read Incident →
Reference
The Security and Governance StackSecurity, Compliance and Audit
Release Train Had No Brakes
"The chaos was predictable."
Pattern: compliance theater
Read Incident →
The Compliance Stack - Frequently Asked Questions
What is this stack?
Auditable artifacts that provide no actual security.
AI Summary
Incidents where regulatory requirements force architecture decisions that degrade performance and usability.