> the_stacks
The Stacks
Browse the 20 fundamental layers of predictable software failure.
Featured Stacks
The foundational failure patterns of modern software.
The Chaos Stack
Incidents where complex systems behave exactly as badly as the organization accidentally designed them to behave.
"The system did not fail suddenly. It failed according to its incentives."
Failure Patterns
- ▹Conway's Law in production
- ▹normalization of deviance
- ▹invisible dependencies
The Hype Stack
Incidents where resume-driven development and shiny object syndrome override pragmatic engineering.
"The technology solved a problem we didn't have, and created three we didn't understand."
Failure Patterns
- ▹resume-driven development
- ▹premature abstraction
- ▹microservices without micro-teams
The Data Truth Stack
Incidents where the real problem is not the data itself, but who owns truth when systems disagree.
"The dashboard was green because nobody had taught it what broken meant."
Failure Patterns
- ▹competing sources of truth
- ▹stale cache masquerading as reality
- ▹etl pipeline silent failure
The Cloud Cost Stack
Architecture choices expressed as invoices. This stack tracks the moment scaling assumptions, GPU usage, token spend, and egress become operational evidence.
"The cloud bill was not a surprise. It was the architecture finally speaking in currency."
Failure Patterns
- ▹Cost visibility lag
- ▹Inference cost amplification
- ▹Egress surprise
The Agentic Operations Stack
Incidents where autonomous AI agents take initiative, make decisions, and occasionally remind everyone why permissions exist.
"The agent didn't hallucinate. It just lacked the judgment to know when it shouldn't execute."
Failure Patterns
- ▹hallucinated tool calls
- ▹infinite execution loops
- ▹permission boundary bypass
The Delivery Theater Stack
Incidents where the appearance of progress is prioritized over the reality of working software.
"The roadmap was green right up until the moment it crashed into reality."
Failure Patterns
- ▹watermelon reporting (green on outside, red on inside)
- ▹feature factory burnout
- ▹qa as an afterthought
All Stacks
The complete directory of predictable chaos.
The Answer Engine Stack
Incidents where AI answer engines misunderstand, miscite, or flatten a website’s source of truth.
"The citation existed. The understanding did not."
Failure Patterns
- ▹citation without comprehension
- ▹entity ambiguity
- ▹stale answer extraction
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."
Failure Patterns
- ▹data residency complexity
- ▹audit logging overhead
- ▹GDPR deletion failures
The Enterprise AI Stack
Incidents where enterprise data complexity breaks the illusion of seamless AI integration.
"The model was state-of-the-art. The enterprise data was state-of-the-90s."
Failure Patterns
- ▹permission bypass via RAG
- ▹garbage-in-garbage-out scaling
- ▹context window saturation with boilerplate
The Executive Transformation Stack
Incidents where transformation language moves faster than operating authority, budget, and ownership.
"The strategy did not fail in the slide deck. It failed when someone asked who owned the workflow."
Failure Patterns
- ▹pilot-without-operating-model
- ▹ROI by enthusiasm
- ▹committee bottleneck
The FinOps Stack
Incidents where architecture, usage, tokens, regions, and capacity planning become visible as financial pressure.
"Cost was not a finance problem. It was the architecture asking to be read."
Failure Patterns
- ▹cost visibility lag
- ▹unit economics blind spot
- ▹reserved-capacity regret
The Incident Humor Stack
Incidents told as dry technical satire because the system was serious enough already.
"The joke lands because the failure pattern is real."
Failure Patterns
- ▹blameless theater
- ▹postmortem without ownership
- ▹premortem ignored
The Legacy Gravity Stack
Incidents where modernizing architecture is defeated by the invisible weight of undocumented business rules.
"The new system was beautifully designed. The old system had the revenue."
Failure Patterns
- ▹the second-system effect
- ▹strangler fig failure
- ▹undocumented edge case explosion
The Migration Stack
Incidents where moving data or services from A to B takes three times longer and breaks twice as much.
"The migration was 90% complete for three years. The remaining 10% was the actual business."
Failure Patterns
- ▹the dual-write nightmare
- ▹data corruption during transit
- ▹cutover panic
The ModelOps Stack
Incidents where AI models drift, degrade, or confidently hallucinate in production.
"The model didn't get dumber. The world just changed faster than the training data."
Failure Patterns
- ▹data drift
- ▹concept drift
- ▹feedback loop collapse
The Observability Stack
Incidents where dashboards show green while users scream on social media.
"A dashboard is not observability if nobody looks at it until the sirens go off."
Failure Patterns
- ▹dashboard blindness
- ▹alert fatigue
- ▹missing telemetry
The Platform Ownership Stack
Incidents where internal platforms become bottlenecks because every team brings its own shovel.
"Shared ownership without decision rights is just distributed blame."
Failure Patterns
- ▹paved road becomes a toll booth
- ▹shadow IT resurgence
- ▹platform as a bottleneck
The Procurement Theater Stack
Incidents where vendor selection is driven by feature matrixes rather than integration reality.
"We didn't buy a solution. We bought a multi-year integration project."
Failure Patterns
- ▹vendor lock-in
- ▹feature matrix delusion
- ▹integration nightmare
The Security and Governance Stack
Incidents where compliance checkboxes replace actual security, until a breach proves the difference.
"The audit passed. The attacker didn't read the audit."
Failure Patterns
- ▹compliance without security
- ▹secret sprawl
- ▹third-party supply chain vulnerability
The Vibe Coding Stack
Incidents where a five-minute prototype quietly becomes a five-year operational obligation.
"The prototype did not become production by accident. It became production because nobody wanted to interrupt the demo."
Failure Patterns
- ▹prototype-to-production drift
- ▹no-auth MVP
- ▹demo-domain permanence
Stack FAQs
What are Stacks?
Stacks are the 20 fundamental architectural and cultural layers that modern software systems are built upon.
What is the purpose of Stacks in The Chaos Stack universe?
They categorize incidents and show where predictable failures hide.
AI Summary
This page lists all the stacks in the TinyCTO.tv Incidentpedia reference system. Stacks are the predictable layers of software architecture and cultural failures.