https://lacunari.com Lacunari indexes a corpus — a codebase, an archive, a body of research — maps what it contains, and reports what is absent. The gaps become a queue that people and AI agents work in parallel without colliding. https://lacunari.com/writing/conflict-free-merge/ https://lacunari.com/writing/conflict-free-merge/ 2026-08-01 If two parties key their documents by the hash of the contents, combining their work is a union rather than a negotiation. Here is what that buys, what it does not, and why disagreement should be preserved instead of resolved. https://lacunari.com/writing/fails-while-reporting-success/ https://lacunari.com/writing/fails-while-reporting-success/ 2026-08-01 A migration that aborts and exits zero. An extractor that processes nothing and returns cleanly. A lock that guards one code path and leaves another open. Notes on the failure mode that test suites are structurally bad at catching. https://lacunari.com/writing/the-1943-problem/ https://lacunari.com/writing/the-1943-problem/ 2026-08-01 Search engines, vector databases and RAG pipelines all rank things that exist. None of them can tell you what is missing, because absence is a property of a set rather than a document. Here is why that gap matters and how to close it in SQL. https://lacunari.com/writing/why-not-just-git/ https://lacunari.com/writing/why-not-just-git/ 2026-08-01 Git records that bytes changed. It has never read your files, cannot tell you what is unfinished, and detects collisions only after the work is done. Here is exactly where that boundary sits, and what sits on the other side of it.