---
id: "concept-stack-literacy"
type: "concept"
source_timestamps: ["00:21:16", "00:22:31"]
tags: ["developer-skills", "strategy", "architecture"]
related: ["concept-the-agent-stack", "concept-false-lego-marketing", "concept-compounding-failure", "framework-builder-skills-2026", "action-develop-stack-literacy"]
definition: "The ability to critically evaluate the layers of the agent infrastructure stack, understand vendor trade-offs, and identify where to build competitive moats."
sources: ["s52-orchestration-layer"]
sourceVaultSlug: "s52-orchestration-layer"
originDay: 52
---
# Stack Literacy

## Definition
The ability to critically evaluate the layers of the agent infrastructure stack, understand vendor trade-offs, and identify where to build competitive moats.

## Why it's mandatory
Because [[concept-the-agent-stack]] is highly fragmented, rapidly evolving, and plagued by [[concept-false-lego-marketing]], builders cannot simply plug components together and expect them to work. Stack literacy is the discipline that protects you.

## What it looks like in practice
- Knowing whether your workload requires the **ephemeral** sandboxing of [[entity-e2b]] or the **persistent** environments of [[entity-daytona]].
- Understanding the platform risk of relying on a standalone memory provider like [[entity-mem0]] versus a frontier model's built-in memory.
- Identifying which layer of the stack is your **competitive moat** and which layers should be outsourced to commodity infrastructure.
- Recognizing that without this discipline, teams build undifferentiated plumbing or architect systems that collapse under [[concept-compounding-failure]].

## Position in the broader skill set
Stack literacy is one of the three critical builder skills for 2026 in [[framework-builder-skills-2026]] (alongside Context Engineering and Eval-Driven Development). The practical action is [[action-develop-stack-literacy]].