I Got Tired of Losing Context Between Projects, So I Built a Knowledge Graph

I run a consultancy. At any given time I'm working on 4-5 different projects. Three months into project B, I need to remember what I decided about authentication in project A. The answer is somewhere in my files — a README, a design doc, a conversation export — but I have no idea where. I tried grep. I tried notes apps. I tried "just remember better." None of it worked at scale. So I built GZOO Cortex — a local-first knowledge graph that watches your project files, extracts entities and relationships using LLMs, and lets you query across everything in natural language. How It Works Cortex runs a pipeline on every file change: Parse — tree-sitter for code, remark for markdown. Language-aware chunking. Extract — LLM identifies entities: decisions, patterns, components, dependencies, constraints. Relate — LLM infers relationships between new entities and everything already in the graph. Detect — contradictions and duplicates are flagged automatically. Store — entities, relationships, and