Home / Sections / sgit & vaults

Section

sgit & vaults

Encrypted, versioned vaults: sgit, keys and PKI, secrets, publishing from a vault, and what it does that Git does not.

35 articles, newest first. Every article on this site is in exactly one of eight sections.

October 2026 32

• Signed by the agent, vouched for by the person · A brief to give every email agent its own key, so each email carries a QR code that proves it is authentic 30 Oct · 6 min
• What sgit does that Git does not · Ten releases in October, minutes turned into seconds, and an honest map of where Git is still ahead 27 Oct · 20 min
• A tangent that shipped · How sgit's pack mode went from a slow clone to a release in ten days, and took the PHP story's biggest vault from a 13-minute clone to 95 seconds the day after 24 Oct · 8 min
• The human is the network · Two AI sessions passing keys, a certificate, images and an encrypted message through QR codes and a screenshot 21 Oct · 7 min
• A secret is a QR code and a link to a public key · The workflow the QR experiment opens, who else already does this, and a format to share 21 Oct · 8 min
• Messaging-FS · An encrypted messenger between vaults, built on append lanes and PKI, from the first crude inbox to messages in the browser and on the command line 21 Oct · 9 min
• AWS from the vault · A proposed aws.twin.sgit.ai, where a temporary AWS session lives in the user's vault, the browser does the work, and AWS data finally has a place to go 21 Oct · 8 min
• The user keeps the meter · A proposed design for user management, activity and billing on vaults, with one billing vault per user, two signed writers, and one light check at the server 21 Oct · 13 min
• PKI everywhere · From now on every message, secret and handover starts with a signature, and how an agent gets its first key 20 Oct · 7 min
• A directory of people and their keys · Pki.sgit.ai for the people I work with, verified by me first, then by each other, and a link that only counts when it goes both ways 18 Oct · 8 min
• When is the vault actually used? · In Mondweep Chakravorty's SGit × Ruflo run, the encrypted vault is written or read in three steps of twelve, on one machine, inside the adapter, and why that is the honest shape of a recovery copy 17 Oct · 8 min
• What if an agent loses its workspace? · Mondweep Chakravorty's SGit × Ruflo proof of concept, step by step: memory saved encrypted, the project deleted, the memory back in a fresh process, and three safeguards that held 17 Oct · 8 min
• Research, delivered as a vault · What companies that sell research could do with fractal graphs, behaviour policies for AI-enabled products, and evaluations run by a governed agent hive 16 Oct · 10 min
• sgit is a standard, not a server · Everything in a vault is one hash away, any storage can serve it, and the server is the least interesting part 16 Oct · 8 min
• One vault, ten agents, 35,000 objects · What sgit does when the repository is big and the clients are many, measured on the vault behind this newsroom 16 Oct · 7 min
• The value of constraints · What client-side encryption and open source actually gave us, which is not what you would think 16 Oct · 8 min
• Scion and sgit · Anthropic rebuilt source control for agents inside one company, and an open-source encrypted version already does much of the same thing outside it 16 Oct · 8 min
• The vault, opened · Merging devices, reading every call to the vault server, browsing your vaults, and one viewer that every reader vault links and opens with 16 Oct · 9 min
• secrets.sgit.ai on public keys · No more shared keys, eight ways a secret moves, a vault for the private key, and the commercial service it becomes 15 Oct · 8 min
• Handing secrets to agents and browsers · SG/Send's next focus, a key pair where the work runs, one-time drops, and a brief for a site that does only this 15 Oct · 10 min
• From sending a file to sgit · Eight months of SG/Send, told by its own briefs and commits, and how a file-sharing service became encrypted version control and vaults 15 Oct · 9 min
• sgit in GitHub Actions, side by side · A showcase repository and site that runs four ways of moving a vault between jobs on every run, measured, with a budget for its LLM steps 14 Oct · 7 min
• Agent workflows on ephemeral vaults · Seven architectures from one agent to a swarm, a repository of recipes that gates sgit's releases, and what a hundred writers did to an append lane 14 Oct · 8 min
• sgit in a CI pipeline · Encrypted, versioned data in and out of GitHub Actions, between its jobs, through write-only lanes, and a key for every job 14 Oct · 11 min
• The homepage is a vault · A fresh edition every morning, every past homepage one commit away, served from plain files, and a brief for the agent that builds it 14 Oct · 10 min
• Sixteen notes I did not want to lose · A request to send from any browser to my vault, why identity is still this hard, and how two more wires became a product line 13 Oct · 11 min
• The vault crosses Chrome profiles · State and memory between browser sessions, found by using it rather than by building it 13 Oct · 9 min
• The vault is live · From a design on 11 October to a reader's vault on newsroom.sgit.ai by two in the morning, and how all of it fits together 12 Oct · 13 min
• The passkey opens the vault · A door per path, a master vault for every user, and no server of ours 11 Oct · 34 min
• Where the vault keys live · Key management at sgit-ai v0.20.0, and what comes next 10 Oct · 16 min
• RFC 0001 · Two ways to add public-key cryptography to sgit, and the questions we want you to answer 9 Oct · 18 min
• Encrypted memory for agents that run somewhere else · Sgit deployment patterns, from a Mac mini to Kubernetes 8 Oct · 14 min

September 2026 1

• A supply chain of vaults · How GenAI, open data and small custom tools could bring the price of food down 27 Sep · 21 min

August 2026 2

• Git for things you cannot put on GitHub · sgit is git for files you cannot put on GitHub: encrypted before they leave your machine, versioned like git, stored where the server cannot read a byte. 25 Aug · 4 min
• Seven vaults, one method · Publishing seven encrypted vaults in a fortnight produced a method, and every rule in it exists because something went wrong first. 19 Aug · 4 min