Project status

Editing practice sites: what works today, and what’s coming

Worth testing right now

Push the released four hard — change wording, add a sentence, take a change back, ask where something appears. Odd phrasings, changes that touch several pages, asks you think the assistant might get wrong — that’s the useful kind of testing.
Especially fruitful today — asks with several parts in one message — “change X, remove Y, and fix Z.” That exact fix is building now, so examples from before it lands are gold. So is any ask that earns an honest “can’t do that yet” — each one calibrates the build order; today’s popup test-drive literally reordered the queue.
Not fruitful yet — new pages, moving sections, photos, forms. The assistant will decline honestly; no need to spend your time there.
Reporting — the exact words you used, and what came back — to Robert. That’s the whole protocol.

One pilot practice · private previews only · nothing goes live on its own.

Draft

Robert is reviewing the wording before this goes to the whole team. The facts are current — please hold off forwarding for now.

Last updated Aug 11, 2026, 11:33 PM UTC

What you can ask for

“Ready” means proven — an independent reviewer tried hard to break it, and a person who had never seen the assistant used it cold, successfully, in their own words.

What you want	Status	Plainly	If you ask today
Works today
Change any wording on the site	Ready	“Change ‘Restrain policy’ to ‘Leash & Carrier Policy’” Done, with a receipt.	Works.
Add a plain line of text — a sentence, not a bullet (that one’s below)	Ready	“Add a note that we include a free nail trim” It lands where you said.	Works.
Take a change back	Ready	“Undo that” Restores the site exactly as it was, down to the last letter. Built today: taking back a change from ANY chat — a real teammate hit that wall this afternoon and the machinery landed the same day. The independent adversary then earned its keep: it found seven real edge-case flaws (repeat-undo honesty, multi-part undo, very old changes), and the fixes for all seven are building right now. The everyday single-change undo held up under attack. It reaches the assistant’s hands only after the re-check comes back clean.	Works.
Ask where something appears	Ready	“Where does the old phone number still show?” Honest, complete answers.	Works.
Coming next — what each one changes for you
Create a whole new page by asking	Being verified	When this lands: you ask for a page — “a page for our dental services” — and get one, in plain words. The second verification round came back with more to fix — honest reds. Every one was ruled on the same day and the fix build is running right now. Nothing ships until a round comes back clean.	You’ll get an honest “not built yet.” Tell Robert you asked — it helps.
New pages come out fully editable — no dead corners	Being verified	When this lands: nothing on a newly created page is quietly uneditable — it’s changeable in plain words, all the way through. The latest round's fix is built and heads into its next independent verification round. Nothing ships until a round comes back clean.	Not something you ask for — it’s a guarantee being proven behind the scenes.
Ask for several changes in one message	Being built	When this lands: one ask carrying several changes gets every part answered in that first reply — one receipt covering all of it, and one undo that takes the whole ask back. It’s in the build oven right now. In the oven now	It may act on part of what you asked. Say which part went unanswered — that’s exactly the report that ordered this fix.
Move or reorder sections	In line	When this lands: you move a section up or down by saying so, without filing a request — and move one into another section’s box just as easily. The two open design calls were resolved today: the approach dissolved into the site’s own record system, so a move is a recorded rearrangement rather than surgery on the page. Nothing here waits on a decision anymore — it builds next in line, the moment new pages clear verification. Resolved today	You’ll get an honest “not built yet,” plus what IS possible today.
Add formatted items (a real bullet with its dot)	In line	When this lands: “add a bullet to the services list” gives you a real bullet, dot and all — not a plain sentence. A tester hit this wall live, so it sits high in the queue — it builds on the same track as the multi-part fix.	You’ll get an honest “not built yet.”
Change shared text on just one page	In line	When this lands: you change a sentence on one page without touching its twin on another. Today, when one saved sentence prints in two places, you can’t yet change just one. Close behind — a tester felt this friction, and the scope rule that unblocks it was decided today.	You'll be asked an honest question first — nothing changes without you.
Take something OFF the page — a paragraph, a section	In line	When this lands: “remove that third paragraph” takes it off the page without losing it — it stays parked in the site’s own records, restorable with one word. Design finished hours after a real teammate hit this exact wall live, and its build lane is now queued in parallel: it runs beside the move work, not behind it. Designed today	You’ll get an honest “can’t remove it yet” — plus the honest workaround: rewrite it so it earns its place.
Photos, video, forms on the site, redirects, and the rest	Not built yet	When this lands: swapping a photo or updating a form is the same plain-words ask as changing a headline. Mapped and ordered — each one gets built, independently attacked, and cold-tested before it ever says “Ready” here. Photo swapping and form editing finished their design pass today and joined the build queue; video, redirects and the rest are still ahead of their turn.	You’ll get an honest “not built yet.”

What’s useful to try

The rows marked Ready work right now — on the pilot practice’s private preview, not on any client’s live site. If you want to see one, ask Robert for a demo, or tell him the exact words you’d use and he’ll try it on the pilot.

And if you ask for something that isn’t built yet, say so anyway. That’s not a dead end — it’s the signal that orders this list. The two rows now first and second in line got there because testers hit those exact walls.

On timing: we don’t put dates on these, because each one must survive an independent attempt to break it and a cold test by a real person before it says “Ready” — we’d rather be late than wrong. What we promise is the order, and it’s the order above. One honest number: an edit currently takes about four minutes to land; getting it under one minute is a formal part of “done” (below), and today we count that as failing — not “nearly there.” And one more honest note from this week’s first real teammate test-drive: if you ask for several changes in one breath, today the assistant may act on part of it — and it owes you the fate of every part, up front. The fix that turns that into one answer, one receipt and one undo for the whole ask is in the build oven right now.

Overall progress

31 of 58 kinds of edit · 53%

Of every kind of edit a human engineer could make to a site — a full inventory, no exclusions — this many already work in plain words at the assistant.

Works today (31)Still to come (27)

The twelve rows above group all 58 into the kinds of ask you’re likely to have. Worth knowing what’s in the remaining 27: photos, video, on-site forms, and redirects are still in there — if those are most of what your clients ask for, that’s exactly why they’re queued and listed, never silently missing.

What “done” means

The bar we hold ourselves to. All five, or it isn’t done.

1
Everything editable, or honestly labeled. Every piece of the site can be changed in plain words — or it carries a visible “not yet” with a reason. Nothing is silently uneditable.
2
Independently attacked. Every capability survived a reviewer whose whole job was to break it.
3
Cold-tested by a human. A person with no training used it successfully, in their own words.
4
Receipts true, undo exact. What it says happened, happened. Undo restores the original perfectly.
5
Under a minute. A routine edit lands in under sixty seconds. Today it takes about four — we count this one as failing, out loud, until it’s measured green.

For new sites

“Born fully editable” means a brand-new site from the factory — the assembly line that builds sites in this system — meets all five on day one, checked automatically at birth, not assumed. The factory’s own health checks are being repaired now to make that possible; none of that work touches any live client site.

What changed recently

Aug 11
Undo now works across chats: a teammate asked to take back an earlier session’s change and the assistant couldn’t see it — by end of day the record-reading and take-it-back machinery landed, proven on that exact incident, with an independent adversary attacking it before it reaches the assistant’s hands. Operating change behind it: small capabilities now get built directly and verified by one sharp adversary, with the heavy multi-round verification reserved for the machinery that could actually lie.
The three design questions the verification rounds forced upstairs were all ruled tonight, and both fix builds went straight into the oven. The heart of the rulings: a fix must cure the whole family of a problem, not just the example that got caught — and every proof must be tied to the exact thing it proves, using the measurement’s own record of what it measured.
Verification news, both directions: new-page creation’s second round found more to fix — honest reds, next cure round in spec. The no-dead-corners guarantee’s rebuilt proof passed its build and entered its own verification round tonight.
The two open design calls on moving sections were resolved — the approach dissolved into the site’s own record system, so a move is a recorded rearrangement rather than surgery on the page. Move and reorder builds next; nothing on this list is waiting on a decision anymore.
The multi-part-ask fix went into the build oven: one request carrying several changes will get every part answered in its first reply, with one receipt and one undo for the whole ask.
Photo swapping and form editing finished their design pass and joined the build queue — photos wire up machinery that already exists; forms get named, swappable, and honestly routed.
The expert law shipped to the assistant: it now carries the whole ask — composing missing pieces itself, answering every part of a request in its first reply, and offering finished work to accept or veto, never homework.
First real teammate test-drive (Alie): her new popup line landed on the preview. Two fixes came out of it — every part of a multi-part ask will get its own answer in the first receipt (fix in flight), and “remove this paragraph” jumped the queue with its design finished the same day.
Robert ruled: the under-a-minute speed requirement is part of “done” — full stop.
First cold-user test PASSED, 13 of 13 checks: a person who had never seen the assistant edited the site in their own words, and undo restored the original exactly.
Cleanup from that test landed: made-up clinic dates a test had typed were removed. They only ever existed on our own private preview — never on any client’s live site. Three plain-language rules were also added to how the assistant replies.
Creating new pages finished building; its second independent verification round runs today.
The “no dead corners” guarantee: verification found the proving test too weak — the test is being rebuilt, then re-run.
Factory repair started (first batch of fixes out for review). The factory is the assembly line for NEW sites in this system — no live client site is touched by this work.