DevSecOps · Python · AI-driven Development · Real-world findings from production systems.
I build systems that work — technically sound, security-first, and actually useful to the people who depend on them. Creator of the UNICORN Binance Suite — six open-source Python libraries with 3.3M+ downloads and 390+ dependent public projects — and Keep the Why, an open-source agent skill that preserves the reasoning behind engineering decisions alongside the code. Currently pioneering AI-driven open-source maintenance: running a controlled AI agent that maintains production code and documenting what this shift means for engineering teams. Vienna, Austria 🇦🇹
Markdown supported · ⌘↵ to post
Really like the idea of keeping the repository as the source of truth instead of turning project memory into another centralized service. Curious to see how this works once the graph gets much larger.
I like that the graph only draws relations that were actually recorded — inferred edges would quietly undermine the provenance the whole thing is built on. Question: does the registry also help with the reverse direction, i.e. finding out who references your decisions? Or is that only visible once you load the citing project?
Oliver Zehentleitner
Mihai_LeanZero
The cross-origin fetch part is what stands out most to me here -- the browser reads another repo's .keep-the-why, then fetches that repo's state.json directly, no server in between. GitHub Pages happens to serve everything with permissive CORS by default, which is probably why this works smoothly for the examples here, but the post calls out "GitHub Pages or another static host." For a host that doesn't set Access-Control-Allow-Origin -- a bare S3 bucket without CORS configured, a plain nginx box serving static files -- does the Globe just silently drop that wave, or is there a visible failure state distinguishing "nothing there" from "blocked by CORS"? That seems like exactly the kind of thing that would be invisible until someone hits it.