In the Token Stream: Architectural Options for Monetizing AI
AI companies can tie revenue to inference by owning the model path, agent runtime, or integration layer, but each added toll must justify its cost.
The Wire
Research notes and product arguments about what software must own when agents become the interface.
AI companies can tie revenue to inference by owning the model path, agent runtime, or integration layer, but each added toll must justify its cost.
Trustworthy AI systems keep consequential authority in deterministic control planes, sandboxes, policies, and independent verification around the model.
LLM judges are moving from offline evaluation into runtime control flow, creating powerful new feedback loops and new production risks.
Multiplayer AI can share conversations, sessions, harnesses, graphs, memory, or work; the key decision is which state must remain durable.
The data stack offers an early view of how mature systems can add inference and agents while preserving governance, semantics, and deterministic foundations.
AI architecture is built around model limits that keep moving, forcing builders to distinguish durable product structure from temporary workarounds.
As many agents work across models and applications, shared external memory is becoming a durable operational data layer rather than a feature of one assistant.
Durable AI work needs identity, types, relationships, and provenance instead of being repeatedly flattened into text and reconstructed later.
Context determines what an AI system knows and produces, so it needs the schemas, lineage, controls, and quality discipline applied to other critical data.
Many apparent model gains come from strong systems engineering around inference, a lesson application builders can use without training frontier models.
Agents need broad access to useful information without owning the pipelines, provenance, and decisions that determine what reaches their context.
Prompt, tool-response, output, and structured-data caching can make agent systems faster, cheaper, and more context-efficient.
AI systems can borrow proven data-engineering patterns for dependencies, transformation, state, and interfaces instead of relearning them.
Reasoning tokens create valuable work that usually disappears; durable artifacts can preserve the useful structure for the next iteration.
Self-improving agents optimize prompts, skills, and workflows, but the bigger opportunity is reusable structure that transfers across new kinds of work.
Code mode turns MCP from a maze of individual tool calls into a programmable product surface shaped by a semantic SDK.
After six months of building ThruWire, the same structural problems kept showing up across AI systems, pushing us to make our point of view explicit.
AI systems encode a hierarchy of control that shapes decisions, often without humans participating in the reasoning that produces confident answers.
Human memory preserves structure more than content, and that procedural logic is what current AI memory systems still cannot replay.
As users move their thinking into AI chats, software companies risk becoming mere infrastructure. The durable moat is structured domain judgment and customer context that keeps professional thinking inside the product.
Lencioni’s alignment playbook assumed every actor was human. With AI in the system, cultural clarity isn’t enough; organizations need explicit, structural reasoning to keep humans and AI aligned.
As models converge, the advantage shifts to the human-authored thinking substrate that aligns people and AI. A personal story of compounding alignment and the thesis behind ThruWire.
AI is brilliant in the moment, but the hardest work is the arc of reasoning that compounds over time. This essay explains why that arc is still human and what tools are missing.