Change requests: describe the change and keep everything else
Once something is built, you change it by typing what you want, such as "make it dark", "add an FAQ page" or "the prices should be in euros". Simple changes are applied straight away by the design engine. Anything else goes to the model, which is told to change only what you asked. Every change then runs the same checks, and a line in the log says whether anything from before went missing.
The fear with AI revisions
Anyone who has tried to edit website with AI prompts knows the risk: you ask for a new button colour and get a different headline, a missing section and a contact form that no longer submits. Regenerating from scratch is the cause. Anticode avoids it in two ways: it handles the most common changes without a model at all, and when the model is needed it edits the existing work rather than rewriting it, then checks the result against what was there.
Changes applied instantly, with no model call
For pages from the design engine, the builder first tries to understand the request itself. These work without an account and cost nothing:
| Say something like | What happens |
|---|---|
| "Make it Swiss" or "try brutalist" | Switches to that design system, with its typeface |
| "Bolder" or "calmer" | Steps the hero headline scale up or down |
| "Dark" or "light" | Switches to the system's dark or light palette |
| "Make the buttons green" | Sets the action colour, checked for contrast in both themes |
| "Add pricing", "remove the FAQ", "add a booking calendar" | Adds or removes that section |
| "Add an about page and a contact page", "put it all on one page" | Adds or removes separate pages; a removed page's sections return to the home page |
| "Call it Northside Climbing" | Renames the site |
The change log lists exactly what moved, such as "Direction: Editorial → Swiss (Inter Tight)".
Changes the model writes
If nothing in the request matches those, it's a change in your own words, and the model handles it. That needs a signed-in account with a confirmed email, and it's measured against your allowance like a build.
- Pages. The Architect rewrites the plan with your change applied to the current one. The list of separate pages only changes when your request was about pages, so rewording the hero can't quietly drop your About page.
- Apps. The model edits the existing program with small, targeted replacements. It's told to do all of what you asked and nothing else: not to restyle, rewrite or reorder what you didn't mention, to use exact colours, prices and wording as given, and never to invent facts. If your message is a question, it answers in a sentence and leaves the app alone.
- Point at it. In an app, turn on pointing, click the element you mean, and your request is tied to it ("About the button 'Start'"), so "make this bigger" has an unambiguous "this".
Checked against the previous version
After a change to a page, the builder compares the new page with the one before it: every section, form and link that existed is looked for again, and only removals you asked for are allowed. The log then shows either Nothing broke, with a count of what's still there and confirmation that every in-page link lands, or a warning naming what's missing, with a button to show it on the builder map. The design and security checks also run again, so the status line updates with the result.
Undoing a change
Every change is saved, and version history keeps the most recent versions, up to your plan's number, so you can bring back an earlier state. Apps also have Undo and Redo steps between their builds, and you can simply say "undo that" or "take it back out" about an earlier change.
Limits
- Pages are rebuilt from a plan, not hand-edited. For an exact word or colour on a page, the visual editor is quicker and doesn't use the model.
- Pointing works in apps. On design-engine pages, select text in the visual editor instead.
- Requests are capped in length. Keep each one to a clear sentence or two; long lists of changes are better sent one at a time.
- The model can still misread you. Read the log and the preview after each change, and restore if needed.
Questions people ask
Which changes are free?
Switching direction, theme, action colour and headline scale, adding or removing sections and pages, and renaming are applied by the design engine with no model call. Changes in your own words use the model.
Will a change undo my manual edits?
Text you edited yourself is stored separately from the generated copy, so a design switch keeps it. A model rewrite of the plan can change generated copy you didn't touch.
Can I attach a photo to a change?
Yes. Photos and videos sent with a change go to the model, which places them where the change says.
What if a change breaks something?
The log will name what's missing. Ask for it back, or restore the previous version from History.