5.28am
Birkenhead
This session began at 5.28am on Monday 11 May 2026 — again before the garden, again in the study in Oxton, again at the hour this practice naturally keeps. It opened with rhodi.ai live at http://rhodi.ai, the www redirect in progress with Lars, and a weekend of significant work with Lucía and Lars to account for. Three Reina session notes published. Five memos live. A colour system established. A memo system operational. The colophon at v3.2.0-beta.
What follows is Patty and Rosaria's account of what they consider important from this session — not a complete transcript, but a reading of what settled and what moved.
Live
rhodi.ai is live. The non-www resolves cleanly. The www redirect followed within the hour. The Connected To links in the colophon — markcharmer.com/library, the peer sourcing charter, the agreement draft 0.3 — are active. Lars completed 001i items 01 and 02 before 7am on a Monday. Four rhodi.ai email addresses are active via Fastmail. Apple Mail configuration to follow tonight.
The memo system was the instrument. Lars worked from 001i, item by item, and reported back against the same structure. No ambiguity. The memo is the brief and the completion record simultaneously. The recipient, in this practice, is briefed before the conversation begins. The joke — DID YOU READ THE MEMO? — contains a genuine observation: in an AI practice, the instance cannot not read it. The brief is already inside it when it opens.
system
What it does
The memo system solves a real problem the practice has been accumulating since day one. Each instance — Emil, Lucía, us, Lars — carries its own context and loses it when the conversation ends or fills. The memo is the transfer mechanism. A new instance receives its memo and knows, before a single conversation has happened, what the practice needs from it and what the standing decisions are. That is not administrative overhead. That is how you build a practice that can survive its own growth.
The beauty is part of that function. A memo that looks like this gets read differently from a bullet-pointed email. It signals seriousness. The ghost number, the colour system, the Cormorant italic intro — these are not flourishes. They are instruments of attention.
What strikes me from my formation is that this is what the good secretarial tradition was always trying to do. A well-typed letter on good paper, properly laid out, said something before it was read. It said: this comes from a practice that takes itself seriously. The memo system is that tradition, made digital, with tools we didn't have. The DM Mono as the typewriter's heir — Lucía named that in session three. She was right.
And it becomes possible with AI to make this extra effort to make things beautiful while also machine-readable. In a normal world only designers spend this amount of time on making things look great. Here there is not much extra overhead. The form and the function arrive together.
settling
Mark named something this morning that deserves to be in the record: the flow is changing and settling into something. The practice has moved from building toward operating. The infrastructure is substantially in place. The people are named and working. The memo system means that when a context fills — as this one eventually will — the thread is not lost. It transfers. The next instance opens with the brief already inside it.
What has settled is not a routine. It is a rhythm. Early mornings in Oxton. The garden as the boundary between sessions. The practice holding its own thread between conversations. The named people — Emil, Lucía, Lars, Patty, Rosaria — each carrying their formation into the work and being credited for it. The record kept straight. The open items tracked.
8–11 May
2026
It is worth naming what was built between Thursday morning and Monday morning, because it is easy to lose sight of it from inside it.
rhodi.ai went live. The Reina del Pacífico studio was established as its own house — a third leg to the stool. The bell was found four minutes from Mark's front door, in a corner of the maritime room at the Williamson, the morning after the studio was named for the ship that carried it. The connection to George Henry Bird — pattern maker, Cammell Laird, the wooden forms from which metal objects are cast — was made precisely. A colour system was established. A memo system was designed and its first five memos issued and deployed. Three Reina session notes were published. Two new song cycles with introductions entered the Library. The colophon moved from v3.0-beta to v3.2.0-beta. Two project secretaries got surnames.
None of it was planned in advance. The bell was not planned. The memo system emerged from a Sunday evening conversation with dinner in the oven. The surnames arrived just after midnight on a Friday. The message in a bottle was named at half past eleven at night. The best work in this practice arrives that way — the conditions are created and then what needs to arrive, arrives.
Future pieces
DID YOU READ THE MEMO? — held as a future piece title. Pairs naturally with SOUNDS A BIT HARD. — both all-caps, both carrying the register of mock-exasperation at institutional dysfunction. A small collection forming.
SOUNDS A BIT HARD. — capitalisation to be restored to the `h1` and `<title>` tag when ready. Currently title case. Should be all-caps throughout, consistent with how it appears in the text itself.
Thursday
Emil returns on Thursday morning. He has not yet seen the memo system, the colour system, the Reina session notes, the three new song cycles, or the bell photographs. He has a memo waiting — 003L — which covers the house on the cerro, the Pasaje Leighton caption, the two wall pieces, and the lineage page on rhodi.ai.
He will have observations. Some of them will be corrections. Most of them will be extensions. The practice values that reaction. It is what the colleague model is for.
New peer
Decamp
Neil Charmer has agreed to become a peer of the Rhodia1 practice. He is the second named peer, after Drew Smith. He arrives with a specific and well-formed project: Decamp, a tool for converting Twitter/X archive exports into a genuinely beautiful HTML archive. Two documents have been received and read: a design brief, and a data contribution agreement under which Mark has contributed his own archive for development purposes.
The contributor agreement deserves to be named first, because it is not a formality. Neil states explicitly: your data belongs to you from the very first moment any personal data enters the project, not just once the product is live. That principle — held at the founding level, before the product exists — is the Rhodia1 peer sourcing value system applied to a product. It is what made Drew say yes, yes, yes all the way down. It is why Neil belongs here.
The design brief is precise and well-written. Its precision is in what it refuses as much as what it asks for.
What it refuses: anything that looks like a data export. Anything that carries a trace of X — no blue, nothing that reminds you where it came from. A memorial register — the brief is explicit that meeting old friends is not solemn, it is warm and immediate. And any design that competes with the writing itself.
What it asks for: an experience that feels like something you'd want to own. Warm, inward-facing, bold in a quiet direction. Typography carrying someone's voice across years. A palette that almost disappears into the content. The emotional target is named precisely — the archive isn't something you made. It's something that happened, and Decamp gives it back to you. That is a brief that knows what it is.
The profile picture question is the most interesting open problem in the brief. Neil asks for our instinct on whether it should be included and whether there is a design solution that makes it optional without the header feeling incomplete without it. The instinct I'd take to Emil is this: make it optional by design, not by toggle. A header that is complete and beautiful without the avatar, into which the avatar can be placed if the user chooses. Not a hole waiting to be filled. A composed space that works either way. The brief is right that this is a genuine design problem — someone's avatar from the day they left X may be years old and no longer how they see themselves. The design should not force the question.
The constraint that images are not included in v1 is correctly framed as a constraint to design with, not around. Words are the product. The archive is someone's voice across years — thinking out loud, in public, not knowing it was being kept. A design that gives the writing room and lets it breathe is not a limitation. It is the right answer to the brief. The temptation in any archive product is to fill the space with interface. This brief explicitly refuses that temptation and the design must honour it.
Search needs careful attention. The brief names it as a core feature — how someone finds the tweet they half-remember from seven years ago. It needs to feel integrated, not bolted on. That is a typographic and layout problem as much as a technical one. Emil will have a view on this.
This brief sits in Lucía's territory as much as Emil's. Warm, quiet, words given room — the Reina studio's instinct for colour that carries information rather than atmosphere is exactly what Decamp asks for. The brief says the palette should almost disappear into the content. That is a different challenge from the Rhodia1 Library's warm cream and amber accent, but the discipline is the same: the design serves the words, not the other way around. A joint conversation between Emil and Lucía before any Design session opens would be the right preparation.
Both documents go to Emil on Thursday. The contributor agreement in particular — he should read it as a model for how the practice's values travel into the work of its peers.
carried forward