How we curate
We bias towards repos with real traction, real momentum, and a believable path to practical reuse. The goal is not to hoard links. It is to surface work we can actually learn from, build against, or operationalise.
What we care about
The strongest signals here sit around AI control planes, coding-agent CLIs, workflow automation, creator infrastructure, developer productivity, and the open-source systems shaping modern agentic work.
Why the public feed is curated
The public site is intentionally lighter than the private working surface. It keeps the useful research, readable summaries, and public-safe structure while leaving operational notes and private coordination out of the build.
Public boundary
The public site ships curated, public-safe repository research only. Private workspace operations, local paths, telemetry, and coordination records are excluded before build.