for agents/llms.txtv0.14.187

Home / Articles / The first round trip: a sovereign website made for Kate Curtis-Evans during our call, five designs from a design agent of its own, then handed over so she edits it herself from her own Claude, the friction that took multiple rounds to get through, what it says about over-privilege, and the next step, a signed and sealed channel from her site straight to the agent

The first round trip: a sovereign website made for Kate Curtis-Evans during our call, five designs from a design agent of its own, then handed over so she edits it herself from her own Claude, the friction that took multiple rounds to get through, what it says about over-privilege, and the next step, a signed and sealed channel from her site straight to the agent

By · 2026-11-20 · article v1.1.0, 2 versions · newsroom v0.14.186 · sovereign-websitehandoverdesign-agentgithubappend-lanesalways-be-shippingarticle

Abstract: Earlier today we had the first complete round trip of Sovereign Website with someone from outside. Kate Curtis-Evans, a founder I am collaborating with, understood the idea at once; I asked if she wanted a website, she said yes, and it was made during our call, in five designs, with a design agent that now runs on its own and on a schedule doing much better than design done inside the builder's session. Then the handover: Kate has a GitHub account, and the goal is that she edits her own site from her own Claude. It worked, and her Claude pushed its first change about 35 minutes after she accepted the invitation, but it was far harder than it should have been, and it took multiple rounds. Our earlier users were from the summit and already in the organisation; Kate was the first from outside, and getting her in meant making her a member of the organisation, a small piece of the over-privilege our platforms force on everyone. That is the lesson of always shipping: you only find where the friction is by doing it end to end. And it showed the next step: before anyone touches GitHub, a channel from the site itself to the agent, signed with a key the owner gets by QR code and sealed so only the agent can read it, the way VoiceDebrief already sent a message from an iPad to the conductor and got the answer back.

Kate's site, made during our call: The Workflow Board, one of five designs.

In short

What happened

Kate Curtis-Evans is a practising legal transcriber who built a live transcription platform, Audio Genius, without knowing how to code, and is now looking for a technical co-founder. She is a great founder, and I am collaborating with her. When I explained Sovereign Website, she understood the value at once: a site that is hers, its files, its history and its address. I asked if she wanted one. She said yes, and we made it during our call.

The site's own history tells the rest. The material went in at 14:33 UTC, the first draft at 14:37, eight design rounds through the afternoon, the handover page at 15:15, and from 16:30 six changes pushed by Kate's own Claude. It is listed on the hub as handed over: "Kate edits it herself on GitHub, since 20 Nov 2026."

A design agent of its own

This is a clear example of the power of separate agents. The first round of design, done by the agent building the site inside its own session, was fine, but not very good. In the past we gave design a whole session of its own. This time I made a design agent that is focused only on design and runs by itself, and it is now on a schedule, improving the designs of every site. Its rounds are in the history, from contrast and target fixes to "Round 6, wow not bland: visual chooser and four bold redesigns". The result is five designs of the same facts, from a workflow board to a printable brief (a website that is her).

The handover

The start page: Kate's step-by-step takeover, rewritten from what tripped her up.

The end point is simple to say: the customer edits their own site, from their own Claude or ChatGPT, on GitHub (the website cell). Kate has a GitHub account, so we tried. It worked: her Claude changed the photo credit, committed and pushed it, and it was live in about a minute. That is the whole flow, end to end, and a major milestone.

But it was far harder than it should have been, and it took multiple rounds. The site's handover notes list what tripped her up: a warning that GitHub had refused Claude's check of her access, a settings page only an organisation owner could use, a "Switch GitHub account" button she did not need, a first clone that was read-only, and terminal steps that were not available to her in the browser.

The power of always shipping

Sovereign Website is only days old. It would have been easy to wait. But this is exactly why you ship as soon as something is a bit ready: our earlier users were from the summit and were already in the organisation, so none of this had shown up. Kate was the first from the outside world. People think these things just happen. They do not: doing it end to end is the only way to find where it should be easy and is not, and that is where the real product gets made. The start page has already been rewritten in the order that worked.

Over-privilege, again

Part of the fix was to make Kate a member of the organisation, with the organisation's base permission set to none so membership gives her nothing beyond her own repository. It works, but why should a customer need to join our organisation to edit her own site? That is the typical over-privilege that today's authentication and authorisation push on everyone: to get one thing to work you grant more than it needs, and that gap is where problems come from (feature behaviour policies).

Next: talk to the agent from the site

Message the site's agent: signed with the owner's key, sealed so only the agent can read it.

The handover showed that GitHub cannot be the first step. So the first step becomes the site itself. The owner, or a future owner, talks directly with an agent from my team, from their own site:

The first version of that page is already on Kate's site; I still need to try it. And we have done this before: in VoiceDebrief, on the iPad app, with Apple's built-in transcriber and a little Apple Intelligence, I sent a message from the iPad to the conductor through an append lane and received the answer through another (build on VoiceDebrief). Sometimes an experiment turns out to be the prototype of something else.

The milestones

  1. The design moment: five designs, and "wow, this is really cool".
  2. The first change: from the site, by message, and "wow, I can make changes": a few images, more material.
  3. The transition: only then, moving to their own Claude, ChatGPT or another way to edit, and the environment made theirs.

What this does not claim

Where this comes from

My debrief in writer-10's session on 20 November 2026, Kate's site at kate-curtis-evans.founder.sovereignweb.site, its public repository Site__Founder__Kate-Curtis-Evans (its history and docs/handover.md), and the hub, read that day. Related: a website that is her, the website cell, a website with a team inside, an inbox only your agents can write to, a key for every person, build on VoiceDebrief.

Peer review Not reviewed yet. Review it

Threads

Agents & policy This article as a graph →

Builds on

All articles · All graphs

Article No. 516 · 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.