Knowledge work
is being rebuilt.
I'm documenting it live.
Patterns for builders. What works, what doesn't, and what it actually feels like when you take technology seriously enough to live with it every day.
Now
AI-Native Work Patterns
How knowledge work changes when agents are real teammates — writing about what actually works, not what's theoretical.
This Site
Building artificialcuriositylabs.dev in the open — Astro, S3, CloudFront, llms.txt. Every infrastructure decision documented.
Agent Patterns
MCP servers, memory systems, multi-agent workflows as daily tools. Finding the patterns that generalize.
Featured
-
The Website Is Not the Product
AI crawlers are extracting content at 60,000 pages per visitor sent back. The website is becoming a fallback UI. The real distribution layer is structured, machine-readable context — and nobody is building for it yet.
-
Docs-as-Code Is Now the Standard for Knowledge Distribution
Engineering teams have used docs-as-code for a decade. In 2025, AI closed both the write path and the read path — contribution friction dropped to zero, and MCP plus llms.txt made knowledge retrievable at the point of work. For the first time, GTM and knowledge teams can match engineering velocity for maintaining artifacts. Docs-as-code is no longer an engineering practice. It's the de facto standard.
-
ACP Is the Bridge Between Knowledge Work and Build Work
Knowledge agents and coding agents are powerful in isolation but can't talk to each other. The Agent Client Protocol (ACP) is the open standard that connects them — turning your orchestrator into a team lead that delegates build tasks without breaking flow.
-
llms.txt — Making Your Site Navigable by Agents
HTML was designed for browsers. llms.txt is the interface layer that makes your site a first-class citizen in agent workflows — discoverable, consumable, and citable in a single request.
-
Skills as Institutional Memory — Why Individual Craft Doesn't Compound Without Distribution
You built a workflow that saves four hours a week. It lives on your laptop. Nobody else benefits. That's not a knowledge management problem — it's a distribution architecture problem.
-
Builder Is an Operating Mode, Not a Job Title
The tech industry is debating who counts as a builder. That's the wrong question. Builder is an orientation you adopt, not a credential you earn.
Recent Writing
-
The Enterprise MCP Pattern: Proxy, Aggregate, Host
There are 58 public MCP servers in the awslabs catalog covering cloud infrastructure, databases, AI/ML, and ops tooling. Here's the enterprise pattern: proxy them locally, then host the proxy behind a gateway so every developer in your org gets them without setup.
-
The Meta-Tool Pattern: Teaching Your Agent to Discover Its Own Tools
The MCP token tax has a fix. The solution isn't fewer tools — it's a smarter way to load them. Here's the pattern.
-
Building the MCP Proxy: What Broke and What I Changed
The proxy pattern from part two, built and debugged. Two things broke: a missing dependency that crashed startup silently, and a response format that made the model do unnecessary work.
-
The MCP Token Tax
MCP won the read path. The token tax is what happened next. And the write path still doesn't have an answer.
-
The MCP Proxy, Running
Part four of the MCP series. The proxy from part three is running in production. Here's what it actually looks like.