---
id: "concept-agentic-primitives"
type: "concept"
source_timestamps: ["00:09:20", "00:09:49", "00:10:38", "00:11:10"]
tags: ["infrastructure", "agent-design", "primitives"]
related: ["concept-human-affordance-bottleneck", "framework-web-rebuild-layers", "entity-branchfs"]
definition: "Fundamental building blocks of computing infrastructure designed exclusively for AI agents, stripping away all human-facing interfaces and scaffolding to maximize speed."
validation_status: "partially-supported"
sources: ["s20-50x-faster"]
sourceVaultSlug: "s20-50x-faster"
originDay: 20
---
# Agentic Primitives

## Definition

Fundamental building blocks of computing infrastructure designed exclusively for AI agents, stripping away all human-facing interfaces and scaffolding to maximize speed.

## Core Idea

Agents do not have eyes, hands, or a need for coffee breaks — so the software they use shouldn't account for those things. Agentic primitives replace traditional human-targeted tools with infrastructure built natively for non-human consumers that measure time in CPU ticks rather than human seconds.

## Concrete Examples

1. **Persistent containers / hosted shells** — Dependencies are installed once and never restarted, eliminating the concept of 'starting up the compiler.'
2. **Shared Key-Value (KV) caches for multi-agent coordination** — Agents coordinate via shared memory rather than text-based messaging, lowering latency by 3-4x.
3. **Sub-millisecond branching file systems** — Tools like [[entity-branchfs]] enable copy-on-write branches in under a third of a second, letting agents rapidly fork, test, and kill parallel execution paths.
4. **Strict-compiler toolchains** — Languages like [[entity-rust]] act as verification engines (see [[concept-tool-agent-coevolution]]).

## Architectural Implications

These primitives assume an 'always-on' consumer that:
- Has no need for visual dashboards or login screens
- Can ingest entire datasets rather than paginated slices (contrast with [[prereq-api-pagination]])
- Coordinates state in memory rather than over text channels

This fundamentally alters how state, memory, and execution are managed in the cloud — and is the architectural escape hatch from [[concept-human-affordance-bottleneck]].

## Validation

Partially supported. The need for agent-native infrastructure (shared caches, low-latency tools) is echoed in observability literature for tool-invocation success and p99 latency. Macro benchmarks increasingly test real workloads mirroring agent use rather than human-style request/response patterns.

## Related

- [[concept-human-affordance-bottleneck]] — the problem these primitives solve
- [[framework-web-rebuild-layers]] — Layer 2 of the rebuild is primitives
- [[entity-branchfs]] — canonical primitive example
- [[concept-agentic-economy-d20]] — what primitives unlock at scale


## Related across days
- [[concept-human-affordance-bottleneck]]
- [[framework-the-agent-stack]]
- [[concept-tool-agent-coevolution]]
- [[prereq-the-bitter-lesson]]