BABrett A McCallindarketype.hashnode.dev·3d ago · 5 min readOnly 2.2% of repositories earn an AFor the last several months, repOptics has been quietly doing one thing: scanning public repositories and grading them on how ready they actually are — measuring decisions, architecture, governance, d10
BABrett A McCallindarketype.hashnode.dev·Jun 29 · 4 min readAgent-ready is becoming part of repo-readyThe question I keep coming back to with repOptics is not whether AI can write more code. It can. The more useful question is what happens after that code lands in a repository. Can someone review it? 00
BABrett A McCallindarketype.hashnode.dev·Jun 15 · 3 min readThe mcp trust registry and lake stabilityIt has been almost a month since the last major research update for repOptics. The context lake has grown and we have been busy wiring up new capabilities to measure repo trust and drag. The big headl00
BABrett A McCallindarketype.hashnode.dev·May 20 · 4 min readAI coding needs better change detection, not louder scorecardsOne thing i keep learning from running repOptics every week: the loudest finding is not always the useful one. This week the research lake grew to 6,642 scans across 3,130 repositories, with 3,515 re-00
BABrett A McCallindarketype.hashnode.dev·May 11 · 4 min readThe repo is the bottleneck nowI keep coming back to the same pattern. AI has made it much easier to produce code. That part is obvious now. The less obvious part is what gets exposed after the code exists. The bottleneck moves. It00
