This is a submission for the DEV April Fools Challenge

This is a submission for the DEV April Fools Challenge

What I Built
The Sentient Teapot (HTCPCP-Compliant AI Agent) ☕🤖 I took the internet’s oldest joke—RFC 2324 (Hyper Text Coffee Pot Control Protocol)—and gave it a brain. While the original spec defined the legendary 418 I'm a Teapot error, my version uses Gemini 2.5 Flash to actually analyze your "brew request."

If you try to "brew" coffee, the teapot evaluates the "vibes" of your situation, refuses to help (as a teapot should), and writes a custom, algorithmically-generated poem roasting your life choices.

Demo
🚀 Live Dashboard: https://achieving-container-penguin-hampton.trycloudflare.com/view/teapot-agent/

How I Built It
I wanted this "useless" project to have a "Grade-A" production heart.

AI Brain: Google Gemini 2.5 Flash for the "Vibe Analysis" and "Poetic Refusal."
Architecture: Built on a modular Fractal Kernel (Node.js) where features are self-discovering "Agents."
Infrastructure: Hosted on GCP Compute Engine (e2-micro) for 24/7 "Always-On" refusal.
Persistence: Local PostgreSQL instance on the VM to track every failed "brew" in a global ledger.
Security: Locked down with Cloudflare Tunnels (obfuscating the origin) and a GCP Firewall that only allows traffic from the Cloudflare edge.
Process Management: Handled by PM2 with systemd auto-restart.
Prize Category
Best Google AI Usage: For using Gemini 2.5 Flash to bring logic and sass to an ancient HTTP status code.
Best Ode to Larry Masinter: I’ve fully implemented the HTCPCP headers (x-vibe-context) and strict 418 status code compliance. Larry would be... well, he'd be something.