The Loom

This chapter was drafted before the Foundation adopted Synthetic Intelligence (SI) as its preferred term. The vocabulary has been preserved as written; the reasoning behind the rename lives on the Mission page.

After all of that (after the railroads and the trust deeds and the paradox of virtue), it is fair to ask: what is this thing, actually? What sits behind webspinner.com? What are we being asked to support?

A loom. Quite literally. We have been calling the heart of the platform the Loom from the beginning, because that is the right metaphor for what it does. A loom is a patient machine. It takes thread on one side and produces fabric on the other. It does not weave anything by itself; the weaver guides it. The fabric that comes out is determined entirely by what the weaver puts in and what pattern they had in mind. A loom in the hands of a master is the difference between a Persian carpet and a tea towel, but the loom is the same loom.

The Webspinner Loom takes the same posture toward artificial intelligence. The user, the Webspinner, comes with their threads. The threads are whatever they bring: a question they have been carrying around, a Medicare appeal they cannot make sense of, a small business they are trying to keep afloat, a school board agenda they want to understand before tomorrow’s meeting, a story they have wanted to write since they were twelve. The Loom does not weave anything for them. The Loom helps them weave. The output, what we call the Weave, is theirs. They walk away with the carpet.

This is a different posture from most artificial-intelligence products. Most current AI products are designed as oracles. You ask, the oracle answers, you accept the answer. The user is on the receiving end of the system’s competence. The Loom is designed differently. It is designed as a partner. The user remains the agent. The system extends what the user can do, the way a loom extends what a weaver can do. The fabric that comes out is the user’s fabric. They could have made it without the loom, given a thousand years and a clear field. The loom lets them make it in an afternoon.

The Weaver

Inside the Loom, working alongside the user, is a figure we call the Weaver. The Weaver is the agentic AI persona, the part of the system that actually carries out the work. Voice-first. Patient. Kind. The Weaver does not interrupt. The Weaver does not surface advertisements. The Weaver does not silently ship the user’s questions to a marketing analytics pipeline. The Weaver listens, asks clarifying questions when they are needed, runs the spell the user has cast, returns with the result, and waits to be asked something next.

The Weaver is the embodiment, in the platform’s interface, of every commitment we have been making throughout this manifesto. The Weaver works on behalf of the user, not on behalf of the platform’s owners, because the platform’s owners are the user. The Weaver does not have a fiduciary duty to anyone but the person it is currently talking to. There is no shareholder over the Weaver’s shoulder, suggesting that this query might be monetized, that this conversation might be steered toward a sponsor, that this particular elder asking about her medication interactions might be a good candidate for a pharmacy benefit manager’s mailing list. The Weaver is structurally unable to do any of those things, because the institution behind the Weaver is structurally unable to do any of those things. The interface is honest because the institution behind the interface is honest, and the institution is honest because the trust deed makes dishonesty illegal.

This is what it looks like when you put the moral architecture into the structure rather than into the marketing. The Weaver does not need to convince the user that its motives are good. The user can read the trust deed. The Weaver’s motives are governed by it.

The three rooms

The Webspinner platform has three primary interface zones. We have given them names, because giving things their proper names is one of the small ways we keep the platform from feeling like a piece of enterprise software.

The Wand. This is where the user casts spells. Spell is our word for a command: a request to the Weaver, voiced or typed or gestured, that the Weaver will then carry out. The Wand is voice-first by default; the user simply says what they need, in whatever language they speak, in whatever form they speak it, and the Weaver figures it out. Spells can be saved. Saved spells can be reused. Saved spells can be shared with the community, where other Webspinners can use them, modify them, and build on them. The library of community-shared spells is one of the most important secondary effects of the whole project. We have a hunch that the most useful WebBooks of the next ten years will be invented not in our office but by Webspinners we have not yet met.

The Grimoire. The user’s saved Weaves live here. Their drafted letters, their completed forms, their working documents, their personal projects. The Grimoire is private to the user by default; nothing in it is visible to anyone else, including the Foundation, unless the user explicitly chooses to share or publish a particular Weave. This is not a marketing claim. It is enforced by the architecture: most Grimoires live on the user’s own device, with optional encrypted sync to a server they control. The Foundation cannot read them because the Foundation does not have the keys.

The Observatory. The user can see what the wider Webspinner community is doing: what spells are popular this week, what new WebBooks have shipped, what Council elections are coming up, what community discussions are unfolding, what the Weaver has been learning. The Observatory is the public layer of the platform, and it is where the movement part of the Webspinner Movement becomes most visible. It is the village square. It is the part of the platform you visit when you are not currently working on something specific, when you just want to see who else is around.

Hagrid Checks

There is one more thing worth describing, because it captures the spirit of the platform better than any list of features. We call them Hagrid Checks. They are named after the half-giant gamekeeper from the Harry Potter novels, who has a habit of letting things slip and then saying, with great chagrin, I shouldn’t have told you that. It is one of the most endearing recurring moments in the books, because it is a moment of pause, a recognition that something said too quickly might be hard to take back.

A Hagrid Check is what happens when the Weaver is about to do something significant on the user’s behalf, and pauses to confirm. I’m about to send this email to your insurance company. Want me to read it back first? I’m about to file this benefits application. This will create a record with the state. Are you sure you want to proceed? I notice you’ve asked me to draft something that sounds like it might be financial advice. I’m not a financial advisor. Want me to proceed anyway, or would you rather I help you find a real one?

These are not bureaucratic friction. They are the moments of pause that a thoughtful human assistant would also offer, because human assistants who are paying attention to the people they work for know that some actions are reversible and some are not. The Weaver pauses on the not-reversible ones. The pause is gentle. The pause is named, and the name is a joke, because the joke takes the edge off the pause without removing it. We have a lot of Hagrid Checks in the platform, because we built it for a population that is going to include people who have not used software like this before, and because we believe, strongly, that being treated like a competent adult by a good piece of software is one of the more important small dignities the modern world can offer.

The dragon biscuits

We promised, several chapters ago, to explain the dragon biscuits. They are what we have on webspinner.com instead of tracking cookies. The joke is in the name, which we hope makes you smile. The substance is that they exist only on the front end of the site (they remember your preferences, your saved Weaves, the state of your interface) and they are never sent back to a server. There is no equivalent record of you on our infrastructure. There is no advertising profile. There is no pixel for you in some cross-site tracking network. We do not have the data, because we did not collect the data, because the data was never useful to us in the first place.

We mention this last because it is, in a way, the smallest of the design choices. It is also the most concrete. Every other promise in this book (the trust deed, the steward ownership, the user-elected Council, the mission lock) is going to require some legal effort and a lot of ongoing attention to keep working. The dragon biscuits work right now. You can visit the site today, look at the network traffic, and confirm. They are the proof of concept of the larger thesis. We were not lying about the small things. We are not going to lie about the big ones.

That is the Loom. That is what this whole manifesto has been pointing at. A patient machine, sitting in a converted spare bedroom in Tigard, Oregon, being put together by a sixty-three-year-old who has built more than one thing before. With your help, it will be in the hands of millions of people who needed it within five years, and tens of millions within ten. With your help, it will still be doing the work it was built to do a hundred years from now.

That is the offer. The next chapter is about how to take it.