Conversion Factory
Agents that evolve site blocks

May 31 - Jun 5, 2026 · 19 commits · phase 1 complete

spec-first the PRD and the architecture diagram were committed before the agents existed.

An agent runtime for conversion-rate optimization on Edge Delivery Services. A coordinator forms a theory from analytics, four spoke agents produce a variant block on a git worktree, and the change ships as a pull request into a live A/B test. Winners get promoted into the codebase by a separate PR. A retrospective agent then edits the agents' own instructions, so the system learns across cycles.

May 31, 2026 · PRD + architecture diagram, drawn first

Four phases, one diagram

Analyst scores the block. Architect forms the theory. Builder writes the variant. Validator runs Lighthouse, accessibility, and regression.

Conversion Factory architecture: a coordinator hub orchestrates analyst, architect, builder, and validator agents through four phases - generate a PR, human review plus live A/B experiment, promote to permanent baseline, and a retrospective loop that updates agent instructions.

From the repo's ai-docs. Phase 4 is the part I care about: the retrospective agent proposes instruction changes, and humans gate how the agents reason.

id
p-conv
  • 4 spoke agents behind one coordinator
  • A/B baseline vs variant, per visitor
  • 1 false-PASS hole closed: verify wiring, not just pixels
conversion-factory-eds ↗
Source
/writing-index.json

2026-10-02

AEM Edge Functions on a Laptop: Google Sign-in, Members-Only Pages and API Data at the Edge

Google sign-in, a members-only section and a greeting bar with the user's own data from an API, added to an Edge Delivery site without touching the site code. The six parts of my video, written up with the code at a pinned commit and a token lab that runs the real signature checks in your browser.

2026-05-24

Theming a Brand-New EDS Site with Google Stitch and MCP: One Prompt, Three Steps, Two Lessons

Theme a brand-new Edge Delivery site in three steps: define the theme, design it in Google Stitch, and wire it back through the Stitch MCP server, all in one long prompt. The real tokens that changed, the call-to-action miss, the fix, and why theming and blocks belong in separate passes.

All projects