Nexus
-
Operators as building blocks
Post 5 of the Nexus series: tiny agents, one job each, composable into a DAG. What a plan is made of Write programs that do one thing and do it well. Write programs to work together. (Doug McIlroy, Bell Labs, 1978) Plans, not replanning was about the plan library: saved query-shapes that Nexus tries to… Continue reading
-
Plans, not replanning
Post 4 of the Nexus series: why a runtime library of saved query plans beats cold-start LLM replanning on every query. The plan you already wrote Point of view is worth 80 IQ points. (Alan Kay) The previous post, Decisions as indexed data, was about refusing to let design decisions evaporate into chat history. This… Continue reading
-
Decisions as indexed data: a traction control system for AI development
Post 3 of the Nexus series: bringing design decisions into the project’s indexed knowledge. The catalog has decisions in it Wholly new forms of encyclopedias will appear, ready made with a mesh of associative trails running through them… (Vannevar Bush, “As We May Think”, 1945) In the last post, Typed links and the catalog introduced… Continue reading
-
Typed links and the catalog
Post 2 of the Nexus series: the graph that sits next to the vector store. The catalog In Xanadu did Kubla Khan / A stately pleasure-dome decree… The Nexus catalog is a metadata layer that sits alongside ChromaDB, tracks every indexed document, and carries typed links between them. It’s what turns the flat vector store… Continue reading
-
Nexus, by example
Post 1 of the Nexus series: an explainer walking through the Delos corpus. What Nexus Is So Nexus is the knowledge system I’ve been building to make my work stick, and to give the AI agents I work with something durable to lean on across sessions. It indexes code, prose, PDFs, and decision records into three tiers of storage, all tied… Continue reading