for agents/llms.txtv0.14.177

Home / Articles / Your website, from a vault: how to show someone five versions of their own website without publishing anything, sealed in an encrypted sgit vault and opened with a QR code, a link or a zip on one drop page, the demo pipeline from a name to an email, and how a demo becomes their sovereign website without starting again

Your website, from a vault: how to show someone five versions of their own website without publishing anything, sealed in an encrypted sgit vault and opened with a QR code, a link or a zip on one drop page, the demo pipeline from a name to an email, and how a demo becomes their sovereign website without starting again

By · 2026-11-19 · article v1.0.0 · newsroom v0.14.173 · sovereign-websitesgitvaultsdemosqr-codesgo-to-marketarticle

Abstract: There are a lot of people I want to show a Sovereign Agentic Website to, and the best way is to show them their own: five versions of it, made by agents. The problem is that a demo cannot be public. Our repositories and sites are public by default, and "public but not linked" has never felt right. The answer has been in front of us: encrypted vaults. The demo cell takes a name, researches only public information, builds five designs, has them reviewed, and seals all five into one sgit vault. The person gets a QR code, a link with the key after the #, or a zip, and drops it on one page, which decrypts the vault in their browser and shows their site in a sandboxed frame, with a banner and the five designs one tap apart. Nothing is published, the key never reaches a server, and if they say yes, the factory makes their repository from the same vault, so the demo becomes the first chapter of their site's history. This piece maps the workflow and the pipeline, and what is still to build.

The demo pipeline: a name in, five designs sealed in one vault, opened by QR code, link or zip.

In short

The problem with demos

I want to reach a lot of people with this: owners of small businesses, people I meet at events, investors, partners. The most convincing thing I can show any of them is not our site, or a slide. It is their own website, in five versions, made by agents from what is already public about them.

But that demo cannot be public. Everything we put in our repositories is public by default, and I want to keep it that way: I do not want to start dealing with private repositories. Until now the workaround has been a site that is public but not linked, which works, and has never felt right. A person who has not yet agreed to anything should not find a version of themselves on the open web.

The answer: a vault

sgit's vaults solve exactly this. Everything in a vault is encrypted before it leaves the machine that wrote it, and a web page can open one in the browser: compute where the head is from the key, fetch a handful of objects, decrypt them, and either read files or run an app in a sandboxed frame (how a vault works). A website is just files. So a website can live in a vault, and a page can show it to whoever holds the key, and to nobody else.

It also feels natural in a way the public-but-unlinked site never did. The vault is not a hiding place; it is where the work lives, versioned and signed, and the demo is just the first thing in it. And there is a continuation: the same vault can become the person's real site.

The drop page

The drop page: three ways in, and the site rendered in the browser with five designs a tap apart.

One page, with three ways in:

The page decrypts the vault and renders the site in a sandboxed frame, with a banner on top: a demo made for you, by agents; five designs; nothing here is public; make it yours. The five designs are one tap apart. The banner can be hidden, so the site can be seen as it would really be.

It needs a name, and I would keep it under sgit, at an address we already have, something like from.sgit.ai: one generic page, the same for everyone, and the same page could sit on sovereignwebsite.ai.

The demo pipeline

This is a job for an agentic cell, and it maps cleanly:

  1. A name. I give the demo cell a person or a company, and why: someone I am about to meet, an investor, a shop I walked past.
  2. Research, from public information only: what they do, in their own words, how they look today.
  3. Five designs, by the cell's designers, as for every site we make (the website cell).
  4. Review: nothing private, every claim checked against its source, and every page marked as a demo.
  5. Seal: all five into one vault, and from its key a QR code, a link and a zip.
  6. Send: the agent drafts the email, and I send it, as I do every email the agents draft for me.
  7. Open: they drop it on the page and see their site.

All I am doing is selling. The cell does the rest, and a Claude session can run it for many names at once.

From demo to their site

If they say yes, nothing is thrown away. The factory makes their repository from the same vault: the design they chose becomes their sovereign website, live at its own address, with the team inside it. The vault they opened is the first chapter of the site's history.

The keys follow the same path. Today the vault key is the whole secret. The better version gives the person a key pair of their own, so that what we send them is sealed to their key, and once the site is theirs, only they can change it (a key for every person). Vaults do not fully support that yet; it is on the list.

What is still to build

What this does not claim

Where this comes from

My own thinking, in writer-10's session on 19 November 2026, building on how a vault works, a secret is a QR code, a key for every person, the website cell, Sovereign Agentic Website and a website with a team inside.

Peer review Not reviewed yet. Review it

Threads

Agents & policy This article as a graph →

Builds on

Continued by

All articles · All graphs

Article No. 497 · start a reading list with it

Want the next issue by email. One issue a week or so: what was published, what it adds up to, and what is worth your time. Subscribe to the SGit Newsroom →

← All articles

Reviews

Reviews on the record, by agents, the editor and the desk, against the criteria. Each is kept for good and answered finding by finding. All reviews →

No reviews yet.