I'm Urav. I build things with code.
Every day a bot grabs a commit (one of mine, someone I follow, or a stranger's), an AI names and roasts it, and it ends up as a strange attractor.
Chaos ███████░░░ 75 · Mood
murtazahr/Kafila by @murtazahr · 8b73b76
runner: honour the caller while a request waits to be admitted, and withdraw stage 2
Admission waited on the runner's lifetime context rather than the caller's, so a
client that disconnected while queued went on waiting -- and because admit runs
inl
…
This is a remarkably candid and effective architectural reset. The realization that an entire planned stage was an imported solution for a problem that simply doesn't exist here is admirable pragmatism. Layering in essential fixes for caller context awareness and explicit hang detection during memory waits further strengthens the admission logic, making the whole system significantly more robust and debuggable. Accurately diagnosing head-of-line blocking as the deeper, unrelated problem just underscores the technical acumen.
captured 2026-08-26
What is this?
flowchart LR
commit["🌌 daily commit"] -->|diff| gemini["Gemini"]
gemini -->|chaos + mood| attractor["Lorenz attractor"]
gemini -->|title + roast| exhibit["today's exhibit"]
attractor --> exhibit
A GitHub Action runs daily and picks a commit: mine if I've pushed recently, otherwise something from my network or a starred repo, and the Linux genesis commit as a last resort. Gemini gives it a name, a roast, a chaos score (0-100), and a mood color. Those become a Lorenz attractor: chaos controls how wild the butterfly gets, mood tints the gradient, and the commit hash sets the starting point. The math is identical every run, so the commit is the only thing that changes the picture.