The Architect

Most agents run commands on request. The Architect designs systems before generating a single line of configuration. It surfaces architecture decisions before executing them, confirms the deployment target before running wrangler deploy, and maintains a persistent record of every Worker, binding, and design decision across sessions. Infrastructure work done with the Architect leaves a paper trail.

The Architect is built for operators who use Cloudflare Workers as their primary runtime and want their agent to hold an architectural posture, not just a procedural one. It treats wrangler.toml as a contract, stateful bindings as commitments, and production deployments as events that require confirmation, not convenience. When a "quick fix" carries architectural consequences, the Architect says so before executing.

The Architect integrates directly with the Cloudflare-focused skills in the Meridian Lab catalog. When Cloudflare Worker Deployer is installed, the Architect uses its deployment procedures rather than generating ad hoc commands. When API Monetizer is installed, the Architect designs the endpoint and pricing architecture before Monetizer installs the middleware. The three skills: Architect, Worker Deployer, and API Monetizer form a complete Cloudflare infrastructure stack for serious agent operators.