> Stack
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."
What this stack means
This stack tracks the moment when AI-generated convenience bypasses architectural review, turning instant gratification into structural debt.
Why this stack exists
Because the distance between a working demo and a secure, maintainable system is invisible until it breaks.
▶ Common Failure Patterns
- •prototype-to-production drift
- •no-auth MVP
- •demo-domain permanence
- •generated-app ownership gap
- •compliance-after-launch
Prevention Checklist
- Require explicit architectural review before any generated code touches production.
- Enforce identity and access management on day one, even for prototypes.
- Establish clear ownership of AI-generated workflows.
Detection Signals
- Surge in unmonitored shadow applications.
- Traffic spikes on undocumented subdomains.
- Security alerts from unauthenticated internal tools.
Related Categories
Related Stacks
The Vibe Coding Stack - Frequently Asked Questions
What is this stack?
Prototypes pushed to production because they looked cool.
AI Summary
Incidents where a five-minute prototype quietly becomes a five-year operational obligation.