ULTRA com Jarvis no ar·50% off nos 3 primeiros meses em qualquer plano·cupom DESCONTO50 aplicado automático
journey· day 4 · arr R$1,974

The day Sentinel was born (and almost leaked a key live)

On the fourth day of the journey, with revenue stuck at R$1,974, Guilherme stopped selling by email for a whole stream to build Sentinel — an AI radar that watches Anthropic, OpenAI, and GitHub in real time — and in the middle of it leaked (and had to rotate) an API key live.

the night

On the fourth day of the marathon toward R$1 million in email sales, the scoreboard was stuck: R$1,974 billed, 19 sales on autopilot. Instead of attacking the number directly, Guilherme decided to spend the whole stream on invisible infrastructure: a system so he'd never again find out about an AI development through a clickbait YouTube video. That's where the day's goal was born — an AI intelligence radar that, after a live brainstorm with the audience, got named "Sentinel."

The build started as usual: six VS Code windows open in parallel, each running Claude Code, and a long brainstorm inside his "brain" (the project's logbook) to design the architecture before writing a single line. They settled on a cron running every 30 minutes sweeping official blogs (Anthropic, OpenAI, Google, Meta, Mistral), GitHub Trending, Hugging Face, YouTube, and X, with one golden rule: total silence if nothing relevant shows up — no alert-for-alert's-sake. Triage stayed in two layers to save cost: Haiku filters fast, Sonnet only digs into what passes the filter, with Opus orchestrating everything via Cloud Flow. For YouTube, instead of counting views, they built an "outlier" criterion: a small video with disproportionate engagement scores higher than a big, lukewarm channel.

With the data model defined in Supabase (sources, items, YouTube channels), the cockpit gained a "Sentinel" tab showing sources, AI costs, and categories in real time. Guilherme tested the pipeline by sending an HTML email with a screenshot auto-generated by the deploy skill, and sent an AI-narrated audio message to the WhatsApp group explaining the project to the base of managers: the thesis was that the biggest problem for email marketers isn't writing the email, it's knowing what to write about. Meanwhile, Cloud Flow ran a swarm of agents in parallel, each terminal pulling the "brain" to know exactly its slice of the task.

The tensest moment of the night wasn't technical, it was security: mid-stream, the agent itself leaked an API key in the terminal output — twice. "We're going to have to reset that key," "generate a new one," "hide it silently" — the reaction was immediate, rotate the credential and move on, remembering that days earlier the project had already suffered an attack from a bad actor who created over 24,000 fake sign-ups trying to bring the system down. Building in public has that price, and the antidote is a fast reflex, not perfection.

The stream closed on an almost meta moment: Sentinel, still under construction, had already found something of real value — the launch of Anthropic's "Claude Partner Network" — and Guilherme applied to the partner program live, using the tool he was building to feed the tool itself. It also left behind a reflection that becomes the next day's task: the "brain" works fine as a logbook, but the project needs a living "system.md", a real architecture map synced with the code, so agents stop making decisions without full context.

key moment

In the middle of building Sentinel, the agent itself exposed an API key in the terminal output, live, twice in a row. Guilherme stopped everything, had it regenerated and hidden on the spot, recalling the attack the project had already suffered days earlier — a reminder that building in public demands a fast reflex for rotating secrets, not the illusion of never messing up.

lesson of the night

If you build in public, sooner or later a key is going to leak on screen — what saves you isn't never making a mistake, it's the automatic habit of swapping the credential on the spot and moving on without stopping the flow.

The biggest problem for a manager using email marketing isn't writing the email, isn't setting up automation — Email Hacker already does that. The biggest problem is knowing what to send an email about.

said live, on the stream itself
what came out of the night

Built live

  • Sentinel system: an autonomous radar monitoring Anthropic, OpenAI, Google, Meta, Mistral, GitHub Trending, Hugging Face, YouTube, and X for relevant AI news
  • Two-layer triage pipeline (Haiku filters fast, Sonnet digs deeper) with a relevance/hype score and an "outlier" engagement criterion for YouTube videos
  • Data model in Supabase (sources, items, YouTube channels) and a dedicated "Sentinel" tab in the cockpit, with sources, AI costs, and categories
  • WhatsApp alerts integrated with Open Claw, capped at three notices a day, plus a consolidated daily brief
  • HTML email with an auto-generated screenshot and an AI-narrated audio announcing the project to the base and the WhatsApp group
  • Cloud Flow orchestration (multi-agent swarm) running in parallel across six terminals, coordinated by the project's "brain"
  • Application to Anthropic's Claude Partner Network, an opportunity discovered by Sentinel while it was still being built
  • First steps toward separating the "brain" (logbook) from a future living "system.md", documentation synced with the code
Claude CodeVS CodeCloud Flow (multi-agent/swarm orchestrator)Claude Opus (orchestration)Sonnet (execution)Haiku (triage)SupabaseActiveCampaignHotmartOpen Claw (WhatsApp)Evolution APIyt-dlpWhisperslash start / slash up skill (brain)slash ui skillslash deploy skill
pronto pra rodar

Pare de revezar janelas. Comece a entregar em paralelo.

Ver os squadsVer preçosa partir de R$ 48,50/mês nos 3 primeiros meses