I built the system these emails run on.

The emails are compiled from this. Bulletproof, table-based components, render-proofed before this concept existed. Filter by category.

The “next 100 years”, as a working thing. A replay of the nine-agent pipeline composing a BA email and passing the ten-check core gate. It fails, routes the failures to a fixer, repairs, and re-checks until it passes. Recorded, so it stays honest.

Replay of email-hub’s real pipeline. The agent names, the gate and the check list are the platform’s own.

The library, the nine agents and the ten-check core gate run on this platform: it designs, render-checks, QA-gates and signs off email before it ships. It builds through a Maizzle and MJML compile sidecar and imports design tokens through the Figma API; the BA components here are hand-tuned bulletproof HTML, inlined from the token source, not framework output. I built it to own email the whole way, and it gives the craft a floor rather than replacing the judgement.

1

Cross-client render matrix14 client profiles, confidence scored, light and dark.Open →

2

The QA gateTen core checks plus four extended: pass, warn or block, with a repair pipeline.Open →

3

Agent calibrationNine agents, evaluation trends and per-agent accuracy.Open →

4

Human-in-the-loop approvalSign-off and an audit trail before it pushes to the ESP.Open →

Product UI from email-hub, the platform I built solo with an agent team. High-fidelity interface mockups, not live screenshots.