Signature Ideas

> Recurring, high-leverage ideas that define the author's intellectual territory.
> Last updated: 2026-07-24

---

1. State Machines as the Universal Mental Model for UI and Agent Orchestration

This is the most distinctive intellectual position.

The author doesn't just use state machines — they see them as the foundational abstraction for both UI behavior and LLM agent behavior. The same XState patterns that model a document editor's 10+ states also model how agents should make decisions.

Modeling UI with State Machines should be the norm — full content hub

State machines to visualize the work of agents — extending the pattern to agent orchestration

Notes about how the document machine should work — real production application

Why it matters: Most developers treat state machines as niche. This position argues they are the right default for any system with multiple states — including agent workflows. It is contrarian and defensible.

Evidence of commitment: 4+ articles, a full content hub with integrations and case studies, a 465-line production XState v5 machine.

---

2. Agent-Codebase Contracts via Documented Interface Conventions

Newly emerging signature idea. Still forming but has high potential.

The "Interface Notions" document is the beginning of a formal contract between human-written code and AI-generated code. The explicit framing — "make sure the Agent Sticks to our conventions" — shifts the problem from "how do we review AI code" to "how do we constrain AI code before it is written."

Interface Notions — full component catalog with architectural structure

Why it matters: This is the right answer to the AI slop problem. Instead of policing output, constrain the input space through documented conventions that agents can read and follow.

---

3. Platform Primitives Over Features

A consistent architectural philosophy: build primitives, not features.

Seed's contact system isn't just for follow/unfollow — it's a trust graph primitive. Capabilities aren't just permissions — they're the trust gating layer. Documents aren't just content — they're the policy layer. This pattern recurs across the work.

Graduated Trust — "Contacts as the vouching primitive... Capabilities for delegated trust... Documents as the policy layer"

Why it matters: Primitives compose. Features don't. Building primitives is harder but creates orders of magnitude more leverage.

---

4. Performance as a First-Class User Experience Concern

Performance is not a technical metric — it is a user trust signal.

The Electron tRPC analysis frames performance not as optimization but as respect for the user. The editor block rendering fix is about trust, not just alignment. The startup sequence improvement is about showing users something immediately rather than making them wait.

The Case Against electron-trpc — "prioritizing developer convenience over user experience"

Improving Editor Block Rendering — "Consistent rendering is a form of trust"

---

Idea Maturity

| Idea | Maturity | Next Step |
|---|---|---|
| State Machines as Universal Model | **Established** — 4+ articles, hub, patterns, case studies | Bundle into course |
| Agent-Codebase Contracts | **Forming** — one document, strong framing | Build agent prompt templates from Interface Notions |
| Platform Primitives Over Features | **Established** — proven through Graduated Trust, capabilities, contacts | Showcase through case studies |
| Performance as Trust Signal | **Articulated** — multiple analyses, unified framing | Synthesize into a "Performance Manifesto" |