# AI Edits Should Preserve The Layout You Already Approved ## Claim An AI content tool earns trust by changing only what it was asked to change and leaving the layout you already approved untouched. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds for iteration on existing, human-approved designs — the common case in Ollie's own framing, since most editor work is reworking content that already exists. - Less relevant when generating from a blank canvas, where there is no existing layout to protect and the AI's job is to propose structure, not preserve it. - Depends on the tool actually scoping its own changes correctly (content-only vs. content-and-layout) — the claim is about what the tool should do, not a guarantee that every implementation gets the scoping right. ## Evidence Ollie's group-level content regeneration selects a whole section and rewrites every piece of content inside it individually, explicitly without touching the design or layout — so the user keeps a layout they already liked and only the copy refits. This is framed as solving a real, named fear: that AI design tools will wreck a layout the user approved. > [!quote] > "instead of changing the design or anything like that, all it did was changed every bit of content individually without touching the design" ## Links - [[AI & the Future of Knowledge Work MOC]] — bounded change as the precondition for trusting an assistant with work you've already reviewed - [[3. Resources/Permanent Notes/AI Editing Tools Earn Trust By Re-Rendering The Real Platform]] — because extends: both are about scoping AI changes to exactly what was authorized and verifying nothing else moved — one verifies block structure after the fact, this one scopes the change before it happens. - [[3. Resources/Permanent Notes/Shipping Infrastructure Not Features Multiplies Who Can Build]] — because applies-in: this scoping discipline is one of the concrete features built on the WordPress 7.0 AI infrastructure discussed in that note. ## Tests / falsifiers - Diff the rendered layout (not just the content) before and after an AI content-regeneration pass — if structural markup or layout attributes changed when only content was requested, the tool violated this principle. - Find a case where users explicitly wanted layout changed alongside content and the tool's strict content-only scoping became a limitation rather than a feature — that would bound the claim to content-iteration use cases rather than all AI editing. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Readwise/Articles/AI-Powered Content and Design, Right Inside the WordPress Editor]] — Ollie's group-level content regeneration feature.