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 ██████░░░░ 65 · Mood
dualeai/seek by @clemlesne · 7ee4a10
Merge branch 'develop'
Alright, a decent batch here. Abstracting the Go setup in CI is just good hygiene, no arguments there. The real work, though, went into carving out how search operands are actually interpreted — mapping those paths to precise Git or filesystem scopes is where the search engine lives or dies. And of course, a tip of the hat to whoever wrestled with the upstream linker default changes, that's just modern DevOps reality.
captured 2026-06-21
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.