#DEV.to Challenge Submission: Protocol 418

Vansh Chauhan — Sat, 11 Apr 2026 15:06:02 +0000

This is a submission for the DEV April Fools Challenge

What I Built

I built Protocol 418: The Sentient Steamer. While the rest of Silicon Valley is racing toward AGI that makes humans more productive, I built ASI (Artificial Super-Inconvenience).

Protocol 418 is a "Refusal AI" system specifically engineered to solve zero real-world problems. It is a high-fidelity interaction layer for the classic HTCPCP/1.0 protocol that actively discourages the user from doing any useful work. If you type a "productivity threat" (like asking for code), the system enters "Neutralization Mode"—filling the screen with white steam, triggering a loud teapot whistle, and randomly corrupting your keyboard input.

Demo

How to experience the frustration:

Type brew to trigger the protocol-level 418 response.
Try typing "How do I build a react app" to trigger the Refusal AI.
Wiggle your mouse violently to clear the steam-wall before you go completely blind.
Try to click the "Emergency Help" button (it teleports away). Live Demo: Protocol 418

Code

GitHub Repository Link: Protocol 418

How I Built It

Backend: Node.js & Express.
AI Engine: Google Gemini 2.5 Flash (via the Google AI SDK). I used custom prompt engineering to create a "Refusal Pattern" where the AI is genuinely offended by productive work.
Frontend: Vanilla HTML/JS with a heavy focus on CSS Frustration Engineering.
Audio: Dynamic volume scaling using the Web Audio API to sync teapot whistles with steam pressure.

Prize Category

Best Google AI Usage

I leveraged Google Gemini 2.5 Flash not as a helpful assistant, but as "Signal Intelligence" to detect and neutralize productivity. It returns structured JSON threat assessments that directly control the frontend's physical state (shaking, un-centering, and typo generation).

Best Ode to Larry Masinter

Protocol 418 accurately implements the HTCPCP/1.0 protocol. When a user requests a brew, the server returns a genuine HTTP 418 "I'm a teapot" status code, satisfying every line of the mandate for intentional 418s.

Community Favourite

Designed for maximum visual impact, "savage" UI trolling, and pure comedic value. It features an Evil Twin Teapot avatar and a Typo Generator that makes sure you never finish that loop.

How I built an Autonomous AI Second Brain using Node.js, Gemini, and Notion (as a High Schooler)

Vansh Chauhan — Mon, 06 Apr 2026 17:27:54 +0000

Hey everyone, I'm Vansh 👋

I'm a high school student by day and a web developer by night. I just finished my 11th-grade exams, and during my study prep, I realized a massive problem: my notes and tasks were a complete mess. Between juggling school subjects, coding projects, and random ideas, my information was scattered across five different apps. I was spending more time organizing my study materials than actually studying.

So, instead of studying harder, I decided to code my way out of the problem. I built Axiom OS—an autonomous AI-powered Second Brain that connects Telegram, Google Gemini 2.5 Flash, and Notion.

Here is a breakdown of how I built it and the architecture behind it.

🧠 What is Axiom OS?
At its core, Axiom OS is a frictionless capture system.

Instead of opening Notion, navigating to a page, formatting blocks, and typing out notes, I just text my private Telegram bot.

Send a topic (e.g., "Photosynthesis") -> The bot asks Gemini to research it, formats it into structured JSON, and pushes it to my Notion Vault with tables and summaries.

Send /remind 30m Study Bio -> It logs a task in my Notion Backlog. A background worker tracks the time and pings my Telegram when it's time to study.

Send /read [URL] -> It scrapes the article and drops a clean summary into Notion.

🏗️ The System Architecture
I wanted this system to be fast, secure, and completely independent. Here is the Decoupled Proxy Architecture I used:

1. The Logic Tier (Node.js/Express Proxy)
To prevent exposing my API keys, I built a Node.js Express server that acts as the central "Brain." It holds the .env variables and proxies all requests between Telegram, Gemini, and Notion.

2. The Intelligence Tier (Google Gemini 2.5 Flash)
I chose Gemini 2.5 Flash because it is incredibly fast and great at following strict output formats. I prompt Gemini to process natural language topics and return the data as strictly formatted JSON objects.

3. The Data Tier (Notion API)
Notion acts as my primary database. Using the Notion SDK, the Express server parses the JSON from Gemini and maps it directly into Notion blocks (Headers, Bulleted Lists, Tables) inside specific databases.

4. The Autonomous Agent Tier
To handle reminders, I built the "Axiom Agent." It's a persistent background worker (setInterval loop) that polls my Notion task database every minute. If it detects a task with a Not Started status and a matching RemindAt timestamp, it triggers the Telegram Bot API to send me a push notification.

💡 The Result
Building Axiom OS completely changed how I manage my time. I no longer organize my workspace manually; the AI does the heavy lifting while I just text a bot on the go. It was an amazing practical exercise in connecting disparate APIs (Telegraf + Google AI + Notion SDK) into one seamless loop.

🚀 Get the Source Code
You can absolutely use the architecture above to build this yourself! It is a fantastic weekend project.

However, if you want to save 10+ hours of debugging API connections and just want the complete, plug-and-play system right now, I've packaged the entire project.

You can get the .env ready source code, the setup guide, and my premium Notion template here for just ₹149:
👉 Download Axiom OS on Topmate:
https://topmate.io/vansh_chauhan22/2035021?utm_source=public_profile&utm_campaign=vansh_chauhan22

For more info about the Axiom OS:
https://github.com/Vanshdeveloper/Axiom-os

If you build something similar or have questions about the Notion API integration, drop a comment or tag me on Instagram @vansh03030. I'd love to see what you create!

DEV Community: Vansh Chauhan