Skip to content

Writing · Field notes from the operating layer

Ideas for operating AI, not merely adopting it.

Essays, field reports, frameworks, and technical guides for the people responsible for making AI work.

Current essay · Models & Engineering

The AI Most People Haven't Met Yet

Chatbots continue and coordinate symbolic information. A different class of model represents how a bounded environment may change, often conditioned on action. Both are useful. Treating them as the same thing is why enterprise AI conversations keep talking past each other.

Choose your path

Start with the work closest to the decisions you make.

Editorial pillars

Six editorial lenses. Each starts from a point of view, not a topic label.

Active series

Multi-part arguments, ordered as published.

Series / qwen38-local-wow

Qwen3.8: Same Weights, Different Product

A five-part investigation into how the harness and serving stack make Qwen3.8-27B useful: the reasoning dial, the harness delta (raw local 2/8 → harnessed 8/8), verified demos, portfolio economics, and native 262K context on 32 GB.

5 published parts5/5 planned
Browse in archive

Series / agent-native-work

Agent-Native Work

A four-part series on designing work for agents: why software got them first, every domain's AGENTS.md, the verification gap, and the practitioner-builder.

4 published parts4/4 planned
Browse in archive

Series / llm-os-modes

Modes of the LLM OS

A six-part series on the operating modes behind frontier AI: Chat, Agent, Deep Research, Cowork, and owned infrastructure.

6 published parts6/6 planned
Browse in archive

Series / token-economy

The Token Economy

A strategy and architecture series on token economics, model portfolios, and AI factory operations.

3 published parts3/3 planned
Browse in archive

Series / context-compilation

Context Compilation

The missing systems layer between retrieval and reasoning, from benchmark blind spots to measured evidence.

3 published parts3/3 planned
Browse in archive

Series / autonomous-stack

The Autonomous Stack

The architecture of intelligent systems, from the data substrate to agent runtimes and prescriptive intelligence.

4 published partsOngoing
Browse in archive

Series / agent-societies

Agent Societies

A field guide to what happens when agents interact at scale, from emergence to competence.

4 published partsOngoing
Browse in archive

Series / ai-native-computer

AI-Native Computer

A technical and operating-model series on what changes when AI becomes the computer, not just another app.

3 published partsOngoing
Browse in archive

Complete index

Archive

4 essays

Filters (1)
Pillar
Audience
Format
Series
  1. Framework · July 9, 2026

    Why Software Engineers Got Agents First

    85.2% versus 10.4%. Same tier of models, five weeks apart. That is not a domain gap — it is a grader gap. Software got agents first because its work came with a free compiler. One law, three multipliers, and the reason every other domain now has to build its own.

  2. Technical Guide · July 9, 2026

    Every Domain Needs Its AGENTS.md

    AGENTS.md is not a document. It is an interface stack — MCP tools, skill catalogs, policy packs, and audit streams — with a README on top. Five translations, one procurement boundary, and the difference between agent-legible and Potemkin agent-ready.

  3. Framework · July 9, 2026

    The Verification Gap

    Verification is not merely the reliability blocker — it is the pricing lever. Where a domain can verify cheaply, it prices on outcomes and tunes smaller models. Where it cannot, it stays hostage to frontier tokens. Margin follows verification.

  4. Framework · July 9, 2026

    The Rise of the Domain Practitioner-Builder

    The forward-deployed engineer is not a phase every domain passes through — it is a fork. Which side your domain walks down is decided by whether it owns its evals fast enough to outrun acquisition. The capstone of the four-part series on designing work for agents.

Newsletter · The Operating Layer

The dispatch for people accountable for making AI work.

A biweekly note on governed enterprise AI, written from inside the operating problem.

Read The Operating Layer
Writing | Brian Letort