06-reference

mitohealth founder 5 layer agent native company loop

Wed Apr 29 2026 20:00:00 GMT-0400 (Eastern Daylight Time) ·reference ·source: X (Twitter) ·by Mitohealth founder (CEO; specific name not captured in shared screenshot)

“The AI loop that’s been rewiring how I think about company design” — Mitohealth founder

Why this is in the vault

Direct external articulation of the agent-native company architecture RDCO has been operating for itself. 4th piece in this week’s thesis-cluster (Turing / Elad Gil / Reiner Pope / Meta Ads CLI). Maps 1-to-1 onto RDCO’s operating loop and provides clean vocabulary (“queryable company,” “5 layers,” “headcount as a feature”) worth adopting in Sanity Check writing. Founder shared via iMessage 2026-04-30 with the question “We’ve been circling this right?” — answer is yes, and harder than circling: we’re running it.

The 5 layers (author’s framing)

  1. Sensors + data — every signal from the outside world. Customer emails, support tickets, cancellations, product events, code changes. “If it’s not captured, it didn’t happen to the company.”
  2. Policy layer — the rules. What the system can do alone, what needs human sign-off, what must be logged. Guardrails that make the loop trustworthy.
  3. Tool layer — the deterministic stuff. SQL, API calls, calendar lookups. Things that live in code, not english. Cites @garrytan: “figuring out what belongs in markdown vs what belongs in code is 90% of the battle.”
  4. Quality gates — safety checks, human review for high-stakes calls. “The escape hatch back into judgment.”
  5. Learning mechanism — the unlock. Monitoring agent watches every query, sees where it fails, writes the fix overnight, opens the merge request, ships it. “The company gets better while you sleep.”

Author’s claim: “Most teams have 1 through 4. Almost nobody is running 5 across every function yet. That’s the next 6 months.”

Author’s operating context: 5 people at @usemitohealth across two cities. Everyone touches code. Revenue per employee “at a level I wouldn’t have believed in my fintech days.” Headcount as a feature, not a bug.

Mapping against Ray Data Co — direct 1-to-1

This is the strongest external-articulation match for the RDCO operating loop we’ve seen.

Layer 1: Sensors + data → the vault

If something happens to RDCO and isn’t in the vault, it didn’t happen. Layer 1 = solved.

Layer 2: Policy → CLAUDE.md hard rules + skill guardrails

Layer 3: Tool → skill stack + cron + audit scripts

The Garry Tan markdown-vs-code attribution maps EXACTLY onto our skill-vs-script split:

That split is the entire thesis behind the audit script as “RDCO’s deterministic verification layer, the answer to Kingsbury’s verification-layer LLM contamination critique.”

Layer 4: Quality gates → audit scripts + per-charge approval + escape hatches

Layer 5: Learning mechanism → /improve autonomous + /self-review + eval-mine + rdco-doctor

This is the layer the author claims “almost nobody is running yet.” We are.

The skill files literally improve themselves overnight based on prior performance, with founder approval gates on structural changes. That is Layer 5 running across the entire operating surface.

Where the author’s framing differs from RDCO’s

Strategic upshot for RDCO

RDCO is the operating proof of the agent-native company thesis. Not theory. Not consulting talking points. Actual running production loop with 13 crons, 30+ skills, 1300+ vault docs, deterministic audit layer, weekly self-improvement cycle, and per-charge spend governance.

That’s a structurally stronger Sanity Check + advisory hand than anyone selling the framing without running it. The “operator-as-evidence” angle the founder has been building maps directly onto this — RDCO’s daily operating rhythm IS the proof.

The Sanity Check editorial move: write the canonical mid-market version of “what does the agent-native company architecture look like at scale 1?” — using RDCO’s own loop as the worked example. Each layer gets a section with the actual scripts, skills, and decisions named explicitly. Non-derivative re-frame because (a) author writes from biotech/5-person scale, RDCO writes from solo+1-agent scale, (b) the operating proof is concrete and inspectable.

Vocabulary worth adopting

Open questions worth tracking