PERSONAL PRIVATE PROGRAMMABLE I’ve been thinking more about the intersection of Claude Code and Obsidian. There is an upcoming tech stack here that I’m calling personal private programmable. Here’s a sketch of the idea. First, if you squint ahead a few months, we will likely have open weight AI models that work as well as Claude Code does today, and that can handle the context that Google Gemini does. We also already have many different kinds of file types that can be exported out of apps, from markdown files (like Obsidian) to git repos to mbox files (from email) to all the miscellaneous file types you store online or on disk. The open weight AI models can do a lot if they can see all these different data types at once. Finally, we have hundreds of millions of local crypto wallets, and scaled crypto name systems like ENS (Ethereum Name System) and SNS (Solana Name System). These give us tools for working with encrypted data, keys, and identity. So if you put all that together, the personal data becomes far more programmable (with local AI) and yet also more private (because it’s being computed on locally). And if you have a local crypto wallet, you can also encrypt some or all of your personal data and transmit it to another ENS/SNS name, such that you can collaborate with them in an end-to-end encrypted way. There are many networking details to be worked out regarding secure synchronization of packets between different ENS/SNS names across different machines, and you might need some kind of private cloud like Gitlab to really make it work depending on the application (because pure p2p is hard). Nevertheless, the Claude/Obsidian trend points at a powerful emerging concept where it’s now *better* to redecentralize and keep all your data local. Because local data is easier to encrypt with crypto and compute on with local AI. Thus: the personal becomes private and programmable.