<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Dominic Lee</title>
  <link>https://domlee.dev</link>
  <description>Build journals on AI delivery, agent infrastructure, and engineering for Japanese-enterprise contexts.</description>
  <language>en</language>
  <lastBuildDate>Fri, 26 Jun 2026 12:44:35 GMT</lastBuildDate>
  <atom:link href="https://domlee.dev/feed.xml" rel="self" type="application/rss+xml" />
  <item>
    <title>How I&apos;d advise a customer rolling out AI agents on their data</title>
    <link>https://domlee.dev/posts/advising-an-ai-agent-rollout</link>
    <guid isPermaLink="true">https://domlee.dev/posts/advising-an-ai-agent-rollout</guid>
    <pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate>
    <description>An architect&apos;s memo: the risks that actually bite when you put an AI agent over real enterprise data, a phased runbook to de-risk it, and how to translate the same architecture for the exec and the platform team.</description>
    <category>ai</category>
    <category>agents</category>
    <category>data</category>
    <category>architecture</category>
    <category>advisory</category>
  </item>
  <item>
    <title>Agent and data governance for Japanese enterprises</title>
    <link>https://domlee.dev/posts/agent-governance-japanese-enterprise</link>
    <guid isPermaLink="true">https://domlee.dev/posts/agent-governance-japanese-enterprise</guid>
    <pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate>
    <description>Deploying AI agents over enterprise data for a Japanese company has constraints a US-centric playbook misses: data residency under APPI, an approval culture that wants confirmation gates, and Japanese-language grounding. Notes from the context.</description>
    <category>ai</category>
    <category>agents</category>
    <category>data</category>
    <category>japan</category>
    <category>governance</category>
  </item>
  <item>
    <title>Wrapping a governance check as an Agentforce action — Flow vs Apex vs LWC</title>
    <link>https://domlee.dev/posts/governance-as-an-agentforce-action</link>
    <guid isPermaLink="true">https://domlee.dev/posts/governance-as-an-agentforce-action</guid>
    <pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate>
    <description>sf-dev-ai runs governance checks over MCP. Here&apos;s the same check as a native Agentforce action — an allow-listed, user-mode Apex InvocableMethod — plus when to reach for Flow or LWC instead, and why the security has to live in code.</description>
    <category>salesforce</category>
    <category>agentforce</category>
    <category>apex</category>
    <category>security</category>
    <category>build-journal</category>
  </item>
  <item>
    <title>Grounding a Salesforce agent in Data 360 — LlamaIndex vs LangChain</title>
    <link>https://domlee.dev/posts/grounding-salesforce-agent-data360</link>
    <guid isPermaLink="true">https://domlee.dev/posts/grounding-salesforce-agent-data360</guid>
    <pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate>
    <description>The useful questions an architect asks an org can&apos;t be answered by a model alone — they need the org&apos;s real config and unified data as context. Here&apos;s a retrieval layer over Salesforce metadata + Data 360, built twice (LlamaIndex and LangChain) and compared honestly.</description>
    <category>ai</category>
    <category>salesforce</category>
    <category>rag</category>
    <category>llamaindex</category>
    <category>langchain</category>
    <category>data-cloud</category>
    <category>build-journal</category>
  </item>
  <item>
    <title>Text-to-SOQL that won&apos;t leak</title>
    <link>https://domlee.dev/posts/text-to-soql-that-wont-leak</link>
    <guid isPermaLink="true">https://domlee.dev/posts/text-to-soql-that-wont-leak</guid>
    <pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate>
    <description>Generating SOQL from natural language is easy. Doing it without leaking restricted data is the architect&apos;s problem. A two-layer field-level-security guard: constrain the prompt, then enforce on the output.</description>
    <category>ai</category>
    <category>salesforce</category>
    <category>nlp</category>
    <category>security</category>
    <category>build-journal</category>
  </item>
  <item>
    <title>Building a governance MCP server for Salesforce — after Dreamforce 2025</title>
    <link>https://domlee.dev/posts/sf-dev-ai-governance-mcp</link>
    <guid isPermaLink="true">https://domlee.dev/posts/sf-dev-ai-governance-mcp</guid>
    <pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate>
    <description>Salesforce shipped Agentforce Vibes and an MCP server for build/deploy/migrate. The governance lane was open. Here&apos;s what I built — tier-annotated tools, a proxy that composes with @salesforce/mcp, and five things that surprised me.</description>
    <category>ai</category>
    <category>mcp</category>
    <category>salesforce</category>
    <category>open-source</category>
    <category>build-journal</category>
  </item>
  <item>
    <title>Architecture from workload: a seven-dimension skill that derives, instead of suggesting</title>
    <link>https://domlee.dev/posts/architecture-from-workload</link>
    <guid isPermaLink="true">https://domlee.dev/posts/architecture-from-workload</guid>
    <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
    <description>An agent skill that turns infrastructure design into a constraint-solving problem. Seven dimensions, ten formulas, a swappable catalog. Same workload in, same architecture out — citable to a formula instead of a hunch.</description>
    <category>ai</category>
    <category>infrastructure</category>
    <category>claude-code</category>
    <category>build-journal</category>
  </item>
  <item>
    <title>The reflection paradox: when self-critique overruled a correct escalation</title>
    <link>https://domlee.dev/posts/langgraph-reflection-paradox</link>
    <guid isPermaLink="true">https://domlee.dev/posts/langgraph-reflection-paradox</guid>
    <pubDate>Sun, 26 Apr 2026 00:00:00 GMT</pubDate>
    <description>Adding a self-reflection node to a LangGraph ticket-triage agent dropped escalations from 60% to 0%. It also took a sev1 cross-tenant data-leak from &apos;escalate&apos; to &apos;finalize&apos;. The math says reflection helps; the tail says be careful where you put it.</description>
    <category>ai</category>
    <category>langgraph</category>
    <category>vertex-ai</category>
    <category>build-journal</category>
  </item>
  <item>
    <title>multi-sdk-llm-notebooks: same task, two SDKs, what actually changes</title>
    <link>https://domlee.dev/posts/multi-sdk-llm-notebooks</link>
    <guid isPermaLink="true">https://domlee.dev/posts/multi-sdk-llm-notebooks</guid>
    <pubDate>Sat, 25 Apr 2026 00:00:00 GMT</pubDate>
    <description>A side-by-side benchmark harness for the OpenAI and Anthropic SDKs. Same task, same prompt, same input — and a few cost surprises.</description>
    <category>ai</category>
    <category>developer-tools</category>
    <category>open-source</category>
  </item>
  <item>
    <title>A Month of Agentic Delivery</title>
    <link>https://domlee.dev/posts/agentic-delivery</link>
    <guid isPermaLink="true">https://domlee.dev/posts/agentic-delivery</guid>
    <pubDate>Mon, 20 Apr 2026 00:00:00 GMT</pubDate>
    <description>An internal AI product shipped in a month — a small product team, a director-mode engineer, and three other teams that quietly made it possible.</description>
    <category>ai</category>
    <category>claude-code</category>
    <category>build-journal</category>
    <category>developer-tools</category>
  </item>
  <item>
    <title>The Messaging-Native Agent Moment</title>
    <link>https://domlee.dev/posts/agent-messaging-moment</link>
    <guid isPermaLink="true">https://domlee.dev/posts/agent-messaging-moment</guid>
    <pubDate>Mon, 23 Mar 2026 00:00:00 GMT</pubDate>
    <description>OpenClaw has 200k stars. Anthropic just shipped Claude Code Channels. I built the same thing a year ago with bash scripts. Here&apos;s what all of it is pointing at.</description>
    <category>ai</category>
    <category>mcp</category>
    <category>build-journal</category>
    <category>developer-tools</category>
  </item>
  <item>
    <title>Claude Code Channels: What They Are and What You Can Build</title>
    <link>https://domlee.dev/posts/claude-code-channels</link>
    <guid isPermaLink="true">https://domlee.dev/posts/claude-code-channels</guid>
    <pubDate>Mon, 23 Mar 2026 00:00:00 GMT</pubDate>
    <description>Channels let you push events into a Claude Code session and relay permission prompts to a remote device. Here&apos;s how the API works and what it actually enables.</description>
    <category>ai</category>
    <category>mcp</category>
    <category>developer-tools</category>
    <category>claude-code</category>
  </item>
  <item>
    <title>Building AgentHive</title>
    <link>https://domlee.dev/posts/building-agenthive</link>
    <guid isPermaLink="true">https://domlee.dev/posts/building-agenthive</guid>
    <pubDate>Sat, 21 Mar 2026 00:00:00 GMT</pubDate>
    <description>I wanted a control plane for AI agent teams — persistent rooms, structured decisions, visible autonomy. Here&apos;s how I built it.</description>
    <category>ai</category>
    <category>developer-tools</category>
    <category>build-journal</category>
    <category>agenthive</category>
  </item>
  <item>
    <title>Building an AI Browser</title>
    <link>https://domlee.dev/posts/ai-browser</link>
    <guid isPermaLink="true">https://domlee.dev/posts/ai-browser</guid>
    <pubDate>Tue, 17 Mar 2026 00:00:00 GMT</pubDate>
    <description>I wanted to test MCP discovery in practice, so I built a browser extension. It grew. Here&apos;s what I found.</description>
    <category>ai</category>
    <category>mcp</category>
    <category>browser</category>
    <category>build-journal</category>
  </item>
  <item>
    <title>MCP Needs a robots.txt Moment</title>
    <link>https://domlee.dev/posts/mcp-discovery</link>
    <guid isPermaLink="true">https://domlee.dev/posts/mcp-discovery</guid>
    <pubDate>Tue, 17 Mar 2026 00:00:00 GMT</pubDate>
    <description>MCP servers are proliferating but there&apos;s no standard way to find them. A case for decentralized discovery — no portals, no registration, just a file at a known path.</description>
    <category>ai</category>
    <category>mcp</category>
    <category>protocol</category>
    <category>open-source</category>
  </item>
  <item>
    <title>Introducing Sonde: AI That Understands Your Cloud</title>
    <link>https://domlee.dev/posts/sonde</link>
    <guid isPermaLink="true">https://domlee.dev/posts/sonde</guid>
    <pubDate>Thu, 26 Feb 2026 00:00:00 GMT</pubDate>
    <description>A cloud operations platform that builds a knowledge graph of your AWS environment and uses AI to reason about security, changes, and compliance.</description>
    <category>ai</category>
    <category>cloud-security</category>
    <category>aws</category>
    <category>developer-tools</category>
    <category>open-source</category>
  </item>
  <item>
    <title>Building envibe, Part 3: The Polish</title>
    <link>https://domlee.dev/posts/building-envibe-3</link>
    <guid isPermaLink="true">https://domlee.dev/posts/building-envibe-3</guid>
    <pubDate>Sat, 31 Jan 2026 00:00:00 GMT</pubDate>
    <description>Shipping v0.2, finding a security bug in my own security tool, and what I learned building with AI.</description>
    <category>ai</category>
    <category>developer-tools</category>
    <category>open-source</category>
    <category>build-journal</category>
  </item>
  <item>
    <title>Building envibe, Part 2: The Build</title>
    <link>https://domlee.dev/posts/building-envibe-2</link>
    <guid isPermaLink="true">https://domlee.dev/posts/building-envibe-2</guid>
    <pubDate>Sat, 31 Jan 2026 00:00:00 GMT</pubDate>
    <description>From design to first commit. Building an MCP-powered permission layer for AI coding assistants with Claude Code.</description>
    <category>ai</category>
    <category>developer-tools</category>
    <category>open-source</category>
    <category>build-journal</category>
  </item>
  <item>
    <title>Building envibe, Part 1: The Idea</title>
    <link>https://domlee.dev/posts/building-envibe</link>
    <guid isPermaLink="true">https://domlee.dev/posts/building-envibe</guid>
    <pubDate>Sat, 31 Jan 2026 00:00:00 GMT</pubDate>
    <description>How a concern about AI assistants reading .env files turned into a permission layer. The research, the design, and the first architecture.</description>
    <category>ai</category>
    <category>developer-tools</category>
    <category>open-source</category>
    <category>build-journal</category>
  </item>
  <item>
    <title>envibe: Stop Leaking Secrets to AI Assistants</title>
    <link>https://domlee.dev/posts/envibe</link>
    <guid isPermaLink="true">https://domlee.dev/posts/envibe</guid>
    <pubDate>Sun, 12 Jan 2025 00:00:00 GMT</pubDate>
    <description>Introducing envibe - a permission layer that gives AI coding assistants granular access to environment variables without exposing sensitive secrets.</description>
    <category>ai</category>
    <category>security</category>
    <category>developer-tools</category>
    <category>open-source</category>
  </item>
</channel>
</rss>