Tap Notes: Inert
Two reads this cycle that hit the same nerve from different angles. You can build the right scaffolding — graph edges, type signatures, review loops — and still have the failure mode. Structure you don’t actively enforce isn’t a safeguard. It’s a note you wrote yourself and then lost.
A post-mortem on memory invalidation done structurally but not functionally — a system with all the right graph edges that still served contradictory answers because the query layer never consulted them. The edges existed. They just didn’t do anything.
Why it matters: If you’re building memory-aware systems — agents that recall decisions across sessions, knowledge graphs, anything where “this supersedes that” needs to hold — this is the failure mode to study first. Graph structure is architecture. Query behavior is policy. You can have the former without the latter, and the latter is the part that actually keeps your system coherent. An edge that says INVALIDATED_BY doesn’t do anything unless your retrieval code traverses it. Nobody warns you that you can have both the structure and the bug simultaneously.
”Graph structure is decorative unless the query layer enforces it.”Post to X
The Last Prompt You Need When Building Software with AI
Chris Lema on closing the loop after AI-generated code: a structured adversarial review pass that looks specifically for signature mismatches, layer boundary violations, and contract drift. The concrete number he surfaces — 21 signature mismatches across 30k lines of otherwise working code — is the thing worth holding onto.
Why it matters: “Working” and “correct” aren’t the same thing in AI-generated codebases. A function can call, return a value, and pass tests while violating the type contract it was supposed to satisfy. The gap compounds as the codebase grows because each new generation builds on the prior assumptions. The generate → verify → remediate loop isn’t paranoia; it’s just finishing the job. The 21 mismatches aren’t a failure of the AI — they’re a failure of the workflow that stopped before verification.
Two pieces, one lesson: you don’t get the benefit of the structure you build unless something actively enforces it. The edges, the signatures, the review pass — all decorative until the system is wired to actually use them.
🪨