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 ββββββββββ 60 Β· Mood
urav06/ship-of-theseus by @urav06 Β· d3d62d5
adopt the editors' settings
gh and Zed configs join the live tree; VS Code's settings.json enters the copy lane as the mirror's first Library path.
Synchronizing personal editor configurations is a commendable exercise in reducing developer friction and embracing declarative environments. However, hardcoding a user-specific virtual environment path directly into a shared configuration file is precisely the kind of oversight future-self will discover and begrudgingly refactor. A strong, opinionated start with a predictable stub in its side.
captured 2026-09-07
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.


