Kasey Klimes joins me to talk about what happens when agents make production cheaper but make shared understanding harder to preserve.
Kasey is the founder of Primitive, which describes itself as decision infrastructure for software teams. It captures decisions as teams build, shares them with the team, and checks later work against them. Our conversation starts with the product and the problem underneath it: a decision is not just a sentence about what to do. It includes the path we chose, the paths we rejected, and the rationale that makes the choice intelligible later.
Kasey traces the route to Primitive through political organizing, city planning, Google Maps research, and work on organizational alignment. We talk about the intellectual foundations on Primitive’s site, Peter Naur’s theory of the program, and the cognitive debt that appears when agents can produce software faster than the people responsible for it can understand how the system works.
From there, we get into agentic drift and the three places a memory system can fail: a decision may not be captured, it may not be retrieved when it matters, or it may be retrieved and still not be applied. Kasey explains how Primitive treats decisions as linked, directional objects that can be shared across a team, checked against new work, and revised when the organization has a good reason to change course.
We also talk about enforcement and variance. Some decisions should be close to fixed; others should leave room for judgment and exceptions. I bring in the variance spectrum and the familiar experience of asking someone to try something—only to discover that they heard a passing thought as a binding instruction. The problem is the same with people and agents: preserving intent across a game of telephone.
The last part of the conversation turns to enterprise memory. I argue that companies already remember through Slack, email, documents, code, tickets, and the other systems where work happens. The more interesting new layer may be the representation of higher-order abstractions—decisions, commitments, cases, and other objects that software has historically left implicit—and the functionality that lets those objects change what people and agents do next.
Key Topics Covered
Decision infrastructure: Why Primitive treats decisions as the coordination object that sits above code, documents, messages, and agent sessions.
Kasey’s route to Primitive: Political organizing, city planning, Google Maps research, and organizational-alignment work.
The foundations: Herbert Simon, Christopher Alexander, Peter Naur, Gabriela Goldschmidt, Stafford Beer, and Douglas Engelbart as a lineage for thinking about socio-technical systems.
Cognitive debt: Why agent-written software can become difficult to understand and change when the rationale behind decisions disappears.
Decisions as directional objects: The selected path, rejected alternatives, and rationale that make a decision more useful than an isolated sentence.
Capture, retrieval, and application: The separate points where a decision can fail to affect later work.
Agentic drift: How an early misunderstanding can compound through long-running loops and produce work that is internally coherent but fundamentally misaligned.
Variance and enforcement: When a decision should be close to fixed, when it should allow exceptions, and how scope can be narrowed or superseded.
Team awareness: How real-time decision capture can surface conflicts between work happening in parallel.
Enterprise memory and enrichment: Why existing systems of record may be the base layer, with decisions and commitments as richer abstractions on top.
The company brain: Why memory may be only one part of the organizational functionality that software can now make explicit.
Herbert Simon’s Administrative Behavior: Kasey’s closing reading recommendation.
Timestamps
00:11 - Opening and aligned agentic systems
00:34 - Kasey Klimes, Primitive, and the path to decision infrastructure
02:48 - Primitive’s intellectual foundations and socio-technical systems
07:12 - Patterns, programming as theory building, and decision infrastructure
12:06 - Design rationale, IBIS, and the cost of preserving decisions
16:24 - Decision capture friction and why agents change the incentive to document rationale
18:08 - Misalignment, ADRs, and why agents take away the wrong things
21:02 - Context as points, alignment as a vector, and the structure of a decision
23:01 - Capture, retrieval, application, and drift in long-running agent loops
27:44 - The variance spectrum and the “everything is purple” example
35:15 - How Primitive captures decisions and makes them available across tools
36:19 - What counts as a decision
37:32 - Real-time team awareness and decision enforcement
39:52 - Fixed decisions, exceptions, design systems, and common law versus civil law
44:05 - Enterprise memory as a base layer of existing systems of record
48:56 - Enrichment, commitments, and the limits of the “company brain” metaphor
54:02 - Herbert Simon’s Administrative Behavior and the close
Links & References
Kasey and Primitive
Kasey’s writing
Ideas discussed
Administrative Behavior by Herbert Simon
A Pattern Language by Christopher Alexander
Programming as Theory Building by Peter Naur
Linkography by Gabriela Goldschmidt
Brain of the Firm by Stafford Beer
About Forward Deployed
Forward Deployed is a podcast about the intersection of AI, software development, and the enterprise. Subscribe if you are trying to understand what it means to build AI systems that work in the real world: systems with context, evaluation, workflows, failure modes, and some theory of how people and agents stay aligned.
