Writing · AI systems in production

AI systems that survive contact with real operations.

Field notes on the part after the demo: source data, operational workflows, approval gates, audit logs, employee adoption, and the cost of producing and delivering the product or service.

Featured series

Built. Shipped. Running.

Six production systems, one public pet project, and one operating principle: AI handles persistence and volume, humans approve what matters, and every action stays auditable.

For operators

Owners, COO/CFO leaders, and teams responsible for real workflows and P&L.

For data- and process-heavy work

Finance, analytics, legal, estimating, construction, operations, and compliance.

Proof before persuasion

Named systems, explicit controls, public data, and source-level receipts.

All field notes

Start with the workflow that matches your problem

Part 1 of 8 · 6 min

The Operational Last Mile

A production AI system needs source data, validation, approval gates, and an audit trail built around how a product or service is delivered.

Receipt: 6 production systems · 1 public pet project · 8 field notes
Read field note →
Part 2 of 8 · 6 min

Marco: Infrastructure Before Copy

Marco is an outbound AI agent that begins with sender health, deliverability gates, and signals before it writes a message.

Receipt: SPF/DKIM/DMARC · placement tests · 15-minute reply triage · approval gates
Read field note →
Part 3 of 8 · 6 min

Hunter: Rules Before Autonomy

Hunter runs persistent PPC operations across Google and Microsoft Ads, but meaningful changes stay governed by written rules and human approval.

Receipt: Google Ads + Microsoft Ads · CRM-grounded rules · Telegram approval · action logs
Read field note →
Part 4 of 8 · 5 min

Oscar: The Dashboard Is the Wrong Interface

Oscar is a self-hosted YouTube operations agent that turns analytics, SEO, captions, and channel tools into a plain-language interface.

Receipt: Self-hosted · multi-channel · dozens of tools · analytics, SEO, captions, reporting
Read field note →
Part 5 of 8 · 6 min

InspectPilot: Reputation vs. Record

InspectPilot pairs inspection scheduling with a compliance engine built on roughly 11 million Los Angeles inspection records over 13 years.

Receipt: ~11M public records · 13 years · LADBS inspections · first-pass and violation history
Read field note →
Part 6 of 8 · 6 min

AI Changed the Build-vs.-Buy Line

A field note on replacing selected SaaS tools with self-hosted systems, where ownership saves money, and where it creates new operating costs.

Receipt: 4 named migration paths · Git source of truth · one MCP gateway · tool-level cost logs
Read field note →
Part 7 of 8 · 7 min

Behind the Watt: AI With Receipts

Behind the Watt is an open evidence database that uses AI to extract claims from public records while preserving source-level provenance and human approval.

Receipt: 3 facilities · 1.03 verified operating GW · 143.3 reported GW separate · source provenance
Read field note →
Part 8 of 8 · 7 min

The Operating Principle

A production pattern for AI systems: let software handle persistence and volume, keep consequential decisions with people, and log every action.

Receipt: Explicit rules · human approval gates · audit logs · source evidence
Read field note →