Agentic Engineering

Most people use it to write code. I use it to build organizations.

Agentic Engineering — a term Andrej Karpathy brought into focus in early 2026 — is the emerging discipline of building software systems with AI agents at their core. The industry conversation centers on development methodology: how to architect, orchestrate, and govern autonomous coding agents.

I take it one layer up.

My work applies Agentic Engineering to organizational design: how one person, aided by a system of AI agents, can produce the output of an entire organization. Not faster coding. Structural capability.

Three principles

1. Agency over Code — The goal is capability formation, not code output.
2. Architecture over Prompts — Not prompt tricks; structural orchestration.
3. Constitution over Speed — Autonomy must be governed to remain controllable and evolvable.

Frameworks

The following frameworks emerged from building real products, not from theory:

• AOA — Agentic Organizational Architecture: Five layers from strategy to execution.
• OTLT — Two-Time Model: Why capability acceleration without structural coherence leads to failure.
• Capability Density: Engineering output capacity per unit.

Products built this way

Every product below is built by one person using these principles:

• One Page — Focus in one gesture. → Try it
• MARGIN — Natural language → Action. → Try it
• FileFlow — Safe automation. → Try it
• Fairmate — Your negotiation team. → Try it
• SFA — AI sales coach.