What is Loom?
In other words: an AI model can change your live site, but only in the ways you approved first. You can see every change it made, and you can undo any of them.
Every change, in four words
Anyone can ask: you, a colleague, a visitor, or the page itself reacting to what it sees. You decide in advance how far each of them can go.
Loom checks the change against rules you wrote down ahead of time. You get the same answer whether or not anyone is watching.
You get a plain sentence saying what changed and which rule allowed it. Loom writes it down whether the change was accepted or rejected.
Loom works out how to undo a change at the same time it makes it, and saves both. It never has to guess the undo later from how the page looks now.
Using it
You keep your framework and your components. Loom provides the oversight and governance.
Use whatever framework you already use. Loom does not write code into your page, and it does not ask you to rebuild anything.
Tell Loom which of your components the AI is allowed to use. That is all the setup there is.
Loom is AI model agnostic. Pick the model you already use, or bring your own. Loom sends it what your users are doing, and it suggests changes from there.
Define your acceptance policy up front, so an AI model can only make changes you already approved. Anything else gets rejected, and Loom tells you why.
What this is for
Getting a machine to change your page is easy now. Being able to say what it changed, and put it back, is not.
When a tool writes components for you, somebody still has to read, review and own every line. Loom does not write code. It rearranges components you already built.
Ask most tools what changed last Tuesday and the best answer is a diff.
Changes land because a model was confident. That is not the same as being right.
Loom works out how to undo a change at the same time it makes it, and saves both. Putting the page back takes one press, and that gets recorded too.
Where it is today
Every number here is checked against the code it describes. None of them was typed from memory.
Questions
No. It can only use the components you registered with Loom, and it can only change settings those components already have. The most it can ask for is something your page already knows how to do.
Your rules do. Loom measures how much of the page a change moves, and whether it can be undone. Then it gives one of three answers: go ahead, hold it for a person to approve, or reject it.
No. It is the layer a page builder would be built on top of. There is no editor to learn and nothing is hosted with us. You keep your own components.
You put it back. Every change is stored together with the change that reverses it, and undoing is checked against your rules and written down like anything else. Nothing is erased to make room for it.
No. Loom runs inside your own application, and the portal comes with it rather than being a service you sign up for. Every Loom site has a portal of its own, including this one, and whoever runs the site writes the list of who may sign in to it. So the Sign in button at the top of this page opens this site's own portal. On a site of yours it would be your portal, and your list.
Keep going
The menu, the questions, this sentence: every one of them is a piece the AI could be asked to move. None of it is code you would have to read afterwards.