I design and ship AI-powered products end to end — model, data,
infrastructure and interface — with a bias for boring technology,
measured costs, and details people never have to think about.
Selected work
01 — Selected work
Bolão Copa 2026
Live — archived after the final
A prediction league for the 2026 World Cup. Friends and family called the
score of all 104 matches; a scoring engine settled the arguments.
Built as a single Cloudflare Worker: the React SPA ships as static assets,
a Hono API handles auth, predictions and rankings, D1 holds the state and
KV absorbs the traffic. During the tournament, scheduled jobs synced live
results and news — retired now that the cup is over, the site stays up as
a freeze-frame of the final table.
System — one worker serves the SPA, the API and the sync pipelines
A competitive murder-mystery logic game, adapted from the puzzle book
genre: read the clues, place every suspect on the floor plan, accuse the
killer — faster than everyone else.
The heart of it is a constraint solver that proves every published case
has exactly one solution before players ever see it. An admin builder
composes rooms, furniture and structured clues that render as natural
Portuguese sentences; players race a server-side clock with a single
accusation each, solo or in teams, over an F1-style season leaderboard.
Same calm architecture as the bolão: one Cloudflare Worker, D1, KV.
System — the solver gates publishing; the API guards the clock and the secret
13 clue types1 accusation per caseReact 18 · Hono · TypeScriptD1 + KV$0/month infra
A Totobola-style prediction game for the Portuguese league. Call 1X2 on
every matchday; correct calls earn points and half a star — stars buy
doubles and triples, just like the real coupon.
Matchdays in the Liga sprawl unpredictably across Friday-to-Monday, so
there is no single deadline: every match locks server-side at its own
kickoff. Hourly jobs rebuild the calendar from football-data.org —
new rounds appear on their own, rescheduled games move themselves —
and a 15-minute results pass only spends API calls when matches are
actually hot. Same calm architecture: one Cloudflare Worker, D1, and
an idempotent scoring engine an admin can always override by hand.
System — every match locks at its own kickoff; the sync loop keeps the calendar honest
34 matchdays · 1X23 pts + ½★ per hitdoubles 1★ · triples 2★React 18 · Hono · D1$0/month infra
A four-player arena game in the spirit of the bomb-laying classics:
blast crates, grab power-ups, trap your friends. Room codes, online
multiplayer, bots that hold their own.
The whole simulation is one deterministic Rust crate — integer-only
math, seeded RNG — compiled to WebAssembly and run twice. In the
browser it powers offline practice; on Cloudflare it lives inside a
Durable Object, one per room, ticking 20 times a second as the sole
authority on every match: the sim itself validates each move, so a
modified client can't cheat physics. State streams to players as
compact binary snapshots over WebSockets; the canvas just
interpolates and draws the neon.
System — one Rust sim, two runtimes: practice in the browser, authority in a Durable Object
2–4 players · room codesRust → wasm · one sim, two runtimes20 ticks/s server authority1 Durable Object per match$0/month infra
Hangman for a crowd: rooms of up to ten, one secret word, and a
personal gallows per guesser. Wrong letters are yours alone — the
word belongs to everyone.
After Kabum's Rust-and-wasm adventure, this one is deliberately boring
tech doing a social job. The entire rulebook — turns, per-player
gallows, the word-setter role the room's owner can assign and the
setter can pass on, hint reveals, full-word risks, sit-outs, the
persistent room scoreboard — is a single pure TypeScript state
machine, shared verbatim by client and server and pinned down by
thirty unit tests. A Durable Object per room wraps it with WebSockets
and a 45-second turn clock, broadcasting personalized views: only the
word's creator ever sees the secret, and accented letters match their
plain keys, so CORAÇÃO yields to a C.
System — one pure state machine, wrapped by a Durable Object per room, one personalized view per player
2–10 players · room codesa gallows each · one shared word45 s turns · hints · word risks1 Durable Object per room$0/month infra
Striker (Cult Games, 1989) gave the ZX Spectrum a whole football
career — Division Four at 18, retirement at 34 — and resolved every
chance with one sweeping bar and the S key. This rebuild keeps the
1989 career and gives it a stage.
It started faithful — green paper, bitmap ZX font, wireframe
goalmouth — and one playtest later the verdict came back: keep the
career, lose the skin. The shipped game is a floodlit rebuild in
this site's own machine-room language: dark DOM menus carrying the
original's key letters, and a canvas match stage with the camera
behind the striker — perspective pitch, a keeper who sets and
dives, a net that ripples when you score. Every chance — one-on-one,
header, volley, penalty, spilled rebound — is a two-phase skill
shot: a reticle you steer along the goal frame, then a power bar
with a sweet zone, judged by a keeper that reads centrality and
power quality and dives the right way only if he reads it. Around
the goalmouth sits the full career: thirty-week seasons with cup
rounds and internationals threaded between league weeks, a weekly
three-chance shooting drill that sharpens whatever regime you
picked, summer transfers to Italy, France, West Germany or Spain,
promotion and relegation, honours. Still no build step and no
server — static files on a Worker, fonts self-hosted, three save
slots plus autosave in localStorage, and saves from the first build
load unchanged. Before each ship, a headless harness played a full
seventeen-season career to retirement.
System — one loop, all in the browser: the match feed offers a chance, two phases of input, one keeper model, and every outcome writes the career
King is the card game every family plays slightly differently: ten
hands, six that punish you for winning tricks and four that pay you
for it, and a scoresheet nobody ever explains to the newcomer at the
table. This build deals the rules alongside the cards.
A table needs four, and the rules take a night to learn — so the room
fills itself. Any empty seat takes a bot at one of three levels: naive,
heuristic, or one that counts what has already fallen. The only hard
rule is that at least one human sits down. The teaching layer isn't a
tutorial you skip on the way in: every hand opens with its own brief —
what it costs, what to avoid, one piece of advice — the score table is
live and opens row by row to show the arithmetic (units × value, and
the exact cards that scored), and between hands a recap replays what
the trick pile actually cost you. Six negative hands drain to −160 on
the King of Hearts alone; four positive hands pay +25 a trick with the
dealer naming trumps; the whole match sums to exactly zero, which is
the fact that finally makes the scoresheet legible. Underneath is the
same spine as the other room games — a pure state machine with zero
I/O, one Durable Object per room, the room evaporating when the last
player leaves. The constraint worth the trouble: the engine has no
words. It emits codes, never sentences, so all six languages live in
the client and four players can read the same table in four different
languages. The 45-second clock runs only while a connected human holds
the turn — a disconnect pauses it, a rejoin restarts it — bots think
for two thirds of a second so a human eye can follow the table, and if
someone walks out mid-match a medium bot takes their seat so the other
three still get their ten hands.
System — one room, one engine that has no words: every seat gets a code-only view, and each client speaks it in its own language
10 hands · 6 negative + 4 positivethe match sums to zero4 seats · bots at 3 levels6 languages · engine speaks codes$0/month infra
An IT-news television channel with no newsroom staff. Every half hour a
Worker reads the Hacker News front page, fetches the articles, and has a
model write thirty-second anchor scripts.
The bulletin is one JSON document in Workers KV. The page computes what is
on air from the wall clock, so every viewer sees the same story at the same
moment without any live server state — a broadcast, not a stream. Two
anchors alternate by the hour over stock studio footage; the voice is the
browser's own speech engine, muted until the viewer asks for it. The whole
thing runs inside Cloudflare's free tiers: ≤ 40 subrequests per run, no
database, no queue.
Pipeline — scheduled newsroom, one KV key, a wall-clock client
12 stories · refreshed every 30 minwall-clock playback · no live server state≤ 40 subrequests per run2 anchors · browser speech, muted by default$0/month infra
Shipped as Terrace Manager — live now. Case study to follow.
007
Shipped as Vrum — live now. Case study to follow.
008
Shipped as Quem é Quem? — live now. Case study to follow.
013
In research.
03 — About
Good architecture is invisible — it's the part nobody has to think about.
I work across the stack: LLM systems and agents, APIs, data models and
serverless infrastructure. I favor small, legible designs over fashionable
complexity — pick pieces that won't wake anyone at 3 a.m., measure what
they cost, and make the whole thing feel effortless. Currently exploring
what production-grade AI products look like when they're built calm.