Posts
All the articles I've posted.
-
How This Site Is Built
The stack behind artificialcuriositylabs.ai: Astro on S3 + CloudFront, DNS on Cloudflare, email forwarding via SES, and an AI-readable content layer. Every decision explained.
-
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.
-
Methodology Is Infrastructure
Every AI session starts fresh. If your methodology lives only in your head, it resets too. The fix is treating it like code.
-
Cloud Sync Is the Wrong Storage Layer for AI Agents
Cloud-synced filesystems (OneDrive, Dropbox, Google Drive) are eventually consistent layers masquerading as transactional storage. AI agents write at machine speed and expect durable writes. The architectural mismatch causes silent data loss. The collaboration model is wrong too.
-
Your AI Agent Needs Communication Modes, Not a Voice Clone
Every AI platform treats voice as a single axis. But knowledge workers switch between six distinct communication registers daily. The fix is mode-specific profiles — engrams — not better cloning.
-
Every AI Tool Encodes a Cognitive Mode
The friction you feel using the wrong AI tool isn't a prompting problem — it's a mode-matching problem.
-
Proof Replaces Persuasion
AI collapsed the cost of building evidence. The rational response is to stop writing alignment documents and start showing working things.
-
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.