Resonance, design tokens everywhere, and five releases in one week

First, an apology. If your inbox has started filing me under "frequent shippers", that is fair. It has been a creative sprint: five releases in one week, and i regret only the parts where you had to read five changelogs. So here is everything worth knowing since i last wrote, in one place, no version numbers, and then i promise to disappear for a few days. More on that below.

Resonance: your AI forgets your site every session. Your site remembers now.

Until this week, every AI session met your site like a stranger: asked about your builder again, reached for raw HTML again, and occasionally redecorated the one page you told it, three chats ago, to leave alone. As of this week, your sites carry a memory. Tell your assistant something once, "always native modules, never stock photos, and never touch the checkout", and every future session starts already knowing it. From any AI you connect, because the memory lives in the site, not in the chat.

The part i am proudest of: rules are enforced, not suggested. Mark the checkout protected and the plugin refuses AI writes to it, server side, no matter how persuasive the prompt was. Your assistant can add protection during a conversation. Only you can remove it, from your dashboard. Included on Builder and Studio plans at no extra cost. See how Resonance works, or read the launch post.

A color the AI cannot paraphrase

When Respira converts a design, your brand color used to be pasted as a value into every block it touched. Values copied into many places drift, because an AI regenerating a section produces something near enough, and near enough compounds into a slightly different website. Now, converted designs register colors and typography as named design tokens, in each builder's own global styles: the block editor and its family, Elementor, Divi, Bricks, Beaver Builder, Breakdance and Oxygen. The converted page references the token by name rather than keeping a copy, the agent never handles the raw value, and a color it never touches is a color it cannot paraphrase. Builders that keep no global style store register nothing, and say so honestly.

The quiet releases: control you can verify

Three quieter things that make the loud ones trustworthy. Access profiles: one switch that decides what a connected agent may do, from everything, to content only, to look-but-do-not-touch, enforced on the server rather than politely requested. Write receipts: every edit now returns proof of whether stored content actually changed, so a write that did nothing can no longer report success. And a sealed activity log: entries are chained together so that if anything is ever altered or goes missing, the log itself tells you exactly where.

Show off with me

Are you happy with what Respira brings to your project? i want to start showing off, together. i am building a wall of the companies and sites that build with Respira, and i would love yours on it. Email me at word@respira.press with your logo and a link, and i will feature you. Thank you in advance. Let's show up for each other.

And now, the disappearing act

Tomorrow i complete trip number 45 around the sun, and my family has gently confiscated my keyboard for the rest of the week. They cited precedent: five releases in seven days, apparently, is "not a personality, it is a cry for a vacation". So Respira and i are both taking some well needed R&R.

i will still read every email, because i always do. Replies resume next week, rested and possibly wiser, though at 45 i make no promises about the second part.

There is a small birthday offer in the email edition; if you are reading this online, subscribe below and you will not miss the next one.

Thank you for building with Respira. It is a strange and wonderful thing to spend a birthday week knowing your work is out there editing thousands of sites, carefully.