---
id: "prereq-software-architecture"
type: "prereq"
source_timestamps: ["00:03:45", "00:08:25"]
tags: ["system-design", "layers"]
related: ["concept-crm-encoded-logic", "concept-skill-vs-process"]
reason: "Necessary to grasp why a CRM is more than just a UI, and why agents must operate within a structured logic layer."
sources: ["s53-agent-100x-review-3x"]
sourceVaultSlug: "s53-agent-100x-review-3x"
originDay: 53
---
# Software Stack Architecture

## What You Need to Know

The video's analysis relies on a layered model of modern software:

- **Storage layer** — databases, schemas, source of truth
- **Logic layer** — workflows, routing, business rules
- **Interface layer** — UIs, chat surfaces, API endpoints

## Why It Matters

The critique of vibecoding assumes the listener understands that **building an interface ≠ building robust business logic**. Without this layered intuition, the argument in [[concept-crm-encoded-logic]] reads as semantic; with it, the danger of vibecoded CRMs becomes obvious. Likewise, [[concept-skill-vs-process]] depends on the listener seeing that workflow logic and skill execution belong to different layers.