Featured
A person who works with AI to produce quality, scalable output that helps humans or other agents get something done.
Featured
Provenance is knowing who wrote what, when, based on what input, and whether it is authoritative.
Featured
Shared state is the canonical surface where humans and agents both read and write the same plan, tasks, drafts, and decisions.
Featured
AI-powered distribution is the collapse of every promotion channel into something one builder can run.
Featured
The agent graduation path is the four-step progression every task takes: manual, co-piloted, system-to-build, autonomous.
Featured
An agent context protocol is the structured contract that lets one agent or tool hand context to another agent without a human...

Foundation content

Foundation content on AI building, AI economics, and trust in AI systems. Each article answers a canonical question and serves as a reference point for related weeklies, monthlies, and tutorials.

What AI building is, who does it, and how to think about the craft of making things with agents.

  • What is shared state for agents?

    Shared state is the canonical surface where humans and agents both read and write the same plan, tasks, drafts, and decisions. Not a vector DB. Not a Redis cache. The missing primitive that turns more agents into a coordinated team instead of more islands.

  • What is AI-powered distribution?

    AI-powered distribution is the collapse of every promotion channel into something one builder can run. Writing, design, video, podcasts, social, email, ads, and PR are now promptable. The distribution gap is closing. The filter is taste.

  • What is the agent graduation path?

    The agent graduation path is the four-step progression every task takes: manual, co-piloted, system-to-build, autonomous. Co-piloting feels productive and is the trap. Real leverage comes from graduating each task to the next step.

  • What is an agent context protocol?

    An agent context protocol is the structured contract that lets one agent or tool hand context to another agent without a human reformatting the data. MCP is the most adopted example. Without a protocol, every agent-to-agent and agent-to-tool integration is bespoke glue.

  • What is the coordination layer?

    The coordination layer is the infrastructure between specialized agents that lets them share state, route work, and operate without a human in the middle. Shared state, event bus, identity and permissions, context protocol. The four pieces that turn an agent org into an operation.

  • What is system-first building?

    System-first building means constructing the verification, monitoring, deployment, and feedback infrastructure before you ship the AI feature. AI alone is fragile. AI inside a system is reliable.

  • What is the agent org?

    The agent org is the org chart of specialized agents a builder runs to scale. Each agent has a role, identity, scope of authorization, dedicated context, and growth path. The shared foundation bonds them together.

  • What is AI building?

    AI building is directing AI to produce output that works at scale. Not using AI casually. Building with it. The distinction between asking a question and creating a system that produces answers repeatedly.

  • What is an agent team?

    An agent team is a small set of specialized agents that coordinate to accomplish a goal that would overwhelm a single agent. This article covers why one agent cannot do everything, the three team architectures in production, and how to design clean handoffs between agents.

  • What is an AI agent?

    An AI agent takes a goal, decomposes it into steps, uses tools, and verifies its own output. This article draws the line between an agent and a chatbot, a script, or an API call, and walks through what goes inside one.

  • What is an AI-native product?

    An AI-native product is one whose core value cannot exist without AI. Remove the AI and the product disappears. An AI-enhanced product adds AI on top of existing value. The difference shapes moats, pricing, and who wins.

  • What is prompt engineering?

    Prompt engineering is the craft of writing instructions to AI that produce reliable, specific output. Engineering because the work is systematic, repeatable, and testable. This article lays out the five elements of a good prompt and the iteration loop that makes prompts hold up.

  • What is the builder's toolkit in 2026?

    The AI builder's 2026 toolkit is a stack of six layers: model, IDE, deployment, data, payments, and agent infrastructure. Together they cost a few hundred dollars a month. Three years ago the equivalent required a DevOps team and ten thousand a month.

  • Who is an AI builder?

    A person who works with AI to produce quality, scalable output that helps humans or other agents get something done. This is the definitional pillar anchor for what AI building means, who becomes an AI builder, and why the category is the new organizing unit of work.

How the economics of AI-native companies work. Pricing, margins, subsidies, and what happens when they end.

  • How do AI-native products make money?

    The business models that work for AI-native products are different from traditional SaaS. Per-seat breaks down. Usage-based, consumable credits, marketplace fees, and content monetization dominate.

  • The economics of AI-native companies

    AI compressed what required 20+ people and $5M into what 2-3 people can build in weeks. This is not a cost reduction. It is a structural change in what is economically viable.

  • What does an AI-native company look like?

    An AI-native company has a different org chart. Humans do strategy, taste, verification, and relationships. Agents do code, content, operations, and monitoring. The ratio of humans to agents is inverted.

  • What is agentic debt?

    Agentic debt is the AI-era equivalent of technical debt. It is the gap between what your agents produce and what you have verified they produce correctly. It accumulates silently and compounds fast.

  • What is the "agent as customer" thesis?

    The agent-as-customer thesis is the observation that products are increasingly evaluated, chosen, and used by AI agents rather than humans. The buyer is still human. The user is an agent.

How to build and verify trust in autonomous AI systems. Accountability, verification, and the human at the edges.

  • What is provenance in agent systems?

    Provenance is knowing who wrote what, when, based on what input, and whether it is authoritative. Every write needs those four answers. Without them, shared state becomes shared ambiguity. Provenance is the bridge between shared state and shared trust.

  • What are the risks of AI building?

    The risks of AI building fall into six categories. Each has a known failure mode, a known mitigation, and a severity that maps to the stakes of the output. Managing them is the builder's job, not the model's.

  • What is AI accountability?

    AI accountability is the engineered ability to trace a wrong output back to a cause, assign responsibility for fixing it, and prevent recurrence. The agent is not accountable. The builder is.

  • What is human-in-the-loop?

    Human-in-the-loop is the design choice of placing a human at specific points in an otherwise-automated workflow to approve, verify, or redirect output. Right placement is where cost of error is high and cost of attention is low.

  • What is outcome verification?

    Outcome verification is the practice of confirming that an agent's action achieved the intended effect, not just that the action executed. It is the difference between the email was sent and the email led to a meeting.

  • What is trust in AI systems?

    Trust in AI is not about believing AI is correct. It is about building verification systems that catch when it is not. Trust is an engineering problem, not a faith problem.