https://occlude.dev/blog/ Notes from building Occlude: the security model stated plainly, the alternatives teams use today, and the engineering decisions behind the product. en Thu, 29 Oct 2026 12:00:00 GMT https://occlude.dev/blog/memory-dump/ https://occlude.dev/blog/memory-dump/ Thu, 29 Oct 2026 12:00:00 GMT The compiler reads the code a contractor cannot, so that code is in memory. Who can read that memory, what stops them, and what we do not claim. https://occlude.dev/blog/four-states-not-two/ https://occlude.dev/blog/four-states-not-two/ Thu, 29 Oct 2026 12:00:00 GMT Most access control has two answers. Occlude has four, because "denied" tells someone the file exists, and credentials need a different answer. https://occlude.dev/blog/perforce-controls-what-syncs/ https://occlude.dev/blog/perforce-controls-what-syncs/ Thu, 29 Oct 2026 12:00:00 GMT Perforce has kept files from contractors for decades, and its manual says what it costs: the build. Why hiding files at runtime does not. https://occlude.dev/blog/five-things-teams-do-today/ https://occlude.dev/blog/five-things-teams-do-today/ Thu, 29 Oct 2026 12:00:00 GMT Five ways teams hand code to a contractor or an agent today: what each gets right, where each stops, and which one we lose to most.