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 ββββββββββ 70 Β· Mood
murtazahr/Kafila by @murtazahr Β· f28db9f
docs: make the README about Kafila
The README was upstream's, so the repository introduced itself as Ollama and
then spent three hundred lines on download links and a community integrations
list, none of which says anything about what this fork is f
β¦
This isn't just a README rewrite; it's an intellectual refactoring of a project's identity. Swapping generic download links for a deeply technical discussion on distributed model inference and a principled approach to clock discipline elevates the documentation from user guide to research platform. The clarity on complex, easily fudged problems is genuinely impressive.
captured 2026-08-16
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.


