The Library
The system behind the emails.
The three journeys are the output. This is the system: a component library the role asks you to own, the agent pipeline that assembles from it, and the platform I built to run it.
The component catalogue
The emails are compiled from this. Bulletproof, table-based components, render-proofed before this concept existed. Filter by category.
The machine assembles, on-brand
The “next 100 years”, as a working thing. A replay of the nine-agent pipeline composing a BA email and passing the ten-check 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 platform
I build products, not just emails. The email-hub platform runs the render checks, the QA gate, the agents and the human sign-off. It supports the email craft, it does not replace it.
Product UI from email-hub, the platform I built solo with an agent team. High-fidelity interface mockups, not live screenshots.