Essays, frameworks, research notes, theses, field notes, and contrarian views. How I think about systems, company building, AI governance, distribution, communications, and real-world operations.
An AI agent may be able to draft, route, summarize, recommend, or trigger — but the business still needs rules for what it is allowed to do, when humans review, and what evidence is captured. The Seven Gates framework for autonomous system governance.
The recurring pattern across my work is not any one industry — it is the underlying operating system. How I design the software, workflows, models, and infrastructure that turn fragmented ideas into functioning enterprises.
How something reaches its users — the channels, communications, partnerships, and acquisition systems — is not separate from what is built. It is part of the architecture and must be designed, not bolted on after the fact.
Software that never touches physical operations is incomplete. Real-world deployment — field workers, equipment, weather, customer expectations — exposes the gaps between designed systems and actual behavior. Building for the field.
Every system, component, process, and asset should be designed for reuse across ventures. The portfolio compounds when infrastructure is shared. How federated architecture creates increasing returns from shared platforms.
Systems that account for failure, recovery, and redemption produce better outcomes than systems optimized only for success. Why resilience, accountability, and second chances are core design principles.
Most business software treats communication as an afterthought — notifications, emails, alerts. But for field operations, communications IS the workflow. Building a governed communications layer for distributed work.
The same system-design principles that work for companies also work for individuals. How I built my own personal operating system — knowledge management, relationship tracking, project architecture, and decision frameworks.
The gap between AI demos and production AI is not about model capability — it is about authority, context, evidence, and accountability. What happens when autonomous systems touch real work without adequate governance.
Insurance is a natural early adopter of autonomous systems because it is already a rules-based industry with defined workflows, explicit authority boundaries, and regulatory evidence requirements. Observations from the field.
Why I structure my work as a portfolio of connected ventures rather than a single company. The economics, operating model, and personal design principles behind federated venture architecture.