Your Code Knowledge Graph Needs Four Layers, Not One
Memory should be a graph. The graph should be four layers. The middle one carries navigation. The top one turns navigation into action.
Open post8 posts
Memory should be a graph. The graph should be four layers. The middle one carries navigation. The top one turns navigation into action.
Open postTwo 2026 studies disagree about whether AGENTS.md helps coding agents. The fight makes sense once you separate push context from pull context.
Open postTracing a sporadic 'invalid middleware' error in Sablier to a hidden startup dependency introduced by a Traefik 3.5.3 refactor.
Open postAG-UI, A2UI, Vercel AI SDK, TanStack AI, and Kombai take different bets on how agents should build interfaces. The architectural question decides which wins.
Open postSelf-evolving AI harnesses fail when they optimize a fixed evaluator. The biological model is right: what needs to evolve is the selection pressure, not just the genome.
Open postMemory consolidation made retrieval worse. Three design principles from agent memory benchmarks, and their unexpected parallels in yogic attention theory.
Open postAI agents capture memories but never consolidate them. Here's how MuninnDB's Dream Engine borrows from neuroscience to fix that.
Open postWhy AI features inside traditional apps are backwards, and how MCP flips the architecture.
Open postA tiny JS island posting to a Cloudflare Worker that streams answers from a free Nemotron endpoint. No origin server. No database. The static site stays static — this one box is the only thing that breathes.