---
title: "How we think about AI operations — Braydon McCormick"
url: https://setearth.io/how-we-think.md
for_agents: /agents.md
updated: 2026-11-03
---

<!-- Fig. 1 (explainer mode) renders above this text. -->

# How we think

<p class="manifesto-thesis">The work gets rebuilt so the agents do it from the start.</p>

<p>None of this started as a framework. It came from twenty years running companies in and around pharma, devices, and software, and then from rebuilding the work inside those companies so the agents do it from the start: the reports, the monitoring, the follow-ups. Every company that has run this way so far is one Braydon owns or co-owns. The four claims below are what survived. They are the mental model for how AI helps.</p>

<section class="claim" id="claim-01">
  <p class="claim-n">[01]</p>
  <h2>the unit</h2>
  <p>The unit is a standing workspace with memory, a repository, a task list, and the systems it is connected to. When work comes in, the fleet that takes it already knows the work.<sup><a href="#note-1">1</a></sup></p>
</section>

<section class="claim" id="claim-02">
  <p class="claim-n">[02]</p>
  <h2>the standing fleet</h2>
  <p>A fleet is many of those units standing at once, kept separate by company and purpose. When work comes in, it goes to a workspace that already knows the operation. Agents get built and retired as the work changes; what persists is the memory.<sup><a href="#note-2">2</a></sup></p>
</section>

<section class="claim" id="claim-03">
  <p class="claim-n">[03]</p>
  <h2>the overlap is the work</h2>
  <p>The work is in the overlap: one agent is rarely the whole job. A question goes through several worldviews and gets challenged. A build moves through research, planning, dependencies, and review. The shape is the same: context, task, execution, then a handoff a person can inspect. Work that runs through this shape is on the <a href="/examples/">examples</a>.<sup><a href="#note-3">3</a></sup></p>
</section>

<section class="claim" id="claim-04">
  <p class="claim-n">[04]</p>
  <h2>a person decides</h2>
  <p>A person designs the contexts, assigns the work, redirects it, and decides what becomes part of the next state. The agents keep the work moving.<sup><a href="#note-4">4</a></sup></p>
</section>

<section class="claim-notes" aria-label="Notes">
  <h2>Notes</h2>
  <ol class="notes">
    <li id="note-1"><span class="note-n">[1]</span> The fleet figure above shows one work item collapsing: the fields behind it are standing agents, durable context, and running services.</li>
    <li id="note-2"><span class="note-n">[2]</span> The count (10+ fleets, 2–50 agents each) and the daily texture of the fleet live on <a href="/how-we-run/">How we run</a>. Agents are built and retired as the work changes.</li>
    <li id="note-3"><span class="note-n">[3]</span> The cases behind those links are drawn from the work records of the companies Braydon is inside, under codenames.</li>
    <li id="note-4"><span class="note-n">[4]</span> Operating sources: STRATEGY.md, OPERATIONS.md, notes/braydons-view-of-ai.md (internal).</li>
  </ol>
</section>
