Conduit
A three-part series on Conduit — why we built a static-site dev-log aggregator that runs on per-project publishers and an LLM, how its architecture splits responsibilities between project repos and the consumer site, and what running it actually looks like in practice.
Start the trail →Parts
-
Part 1
The Work That Writes Itself
Why we built Conduit, and what it gives the team that nothing else did
-
Part 2
How Conduit is Shaped
The architecture that lets one consumer site read N project repos without coupling either side to the other
-
Part 3
How Conduit Runs
Onboarding a project, surviving operational failure, and what's deferred until the system grows