---
id: "entity-andrej-karpathy-d2"
type: "entity"
entityType: "person"
canonicalName: "Andrej Karpathy"
canonicalUrl: "https://karpathy.ai"
source_timestamps: ["§2.2"]
tags: ["context-engineering", "lineage"]
related: ["concept-context-scoping", "concept-icm"]
sources: ["paper"]
sourceVaultSlug: "icm-paper-folder-architecture-2026Jun02"
originDay: 2
---
# Andrej Karpathy

## Role in this source

Cited as the source of **"context engineering"** (2025) — the framing that:

> *system performance depends on what context is delivered, in what structure, and at what moment.*

## Why ICM cites him

ICM **operationalizes Karpathy's framing** by structuring context into separate organizational tiers ([[concept-five-layer-hierarchy]]) rather than a monolithic prompt — see [[concept-context-scoping]].

Karpathy is not an author of ICM; he is the **lineage anchor** for the context-engineering posture the methodology adopts. Other lineage anchors are in [[prereq-unix-pipelines]] (Unix philosophy), [[prereq-llm-context-windows]] (Liu et al.'s "lost in the middle"), and [[concept-icm-as-compilation]] (Aho et al.'s compiler architecture).


## Related across days
- [[entity-andrej-karpathy-d1]]
- [[concept-dialogue-structure]]
- [[synthesis-dialogue-to-context-engineering]]