Colour as structure

The first design decision was the form of the memo itself. Not a template with fields to fill. Not a corporate document with headers and footers and version numbers. Something that has presence. Something that commands the room before you read a word.

The reference was Diana Vreeland — not her memos specifically, but her understanding that the form of communication is itself an argument. That a document which looks considered gets read differently from one that looks functional. That brevity and authority are not opposites. Her memos to her staff at Bazaar were telegraphic, compressed, trusting the recipient to understand what was meant beyond what was said. Emil had already named this, in the Day 1 Part 2 session, as the model for how the practice briefs its AI collaborators. The Vreeland memo as the prompt. The instruction that trusts the recipient.

The memo form that emerged from the evening session honours that lineage. A large number — really large, ghost-printed enormous in the background and stated boldly in the foreground. A suffix letter in the accent colour. An intro note in Cormorant Garamond italic — directed, not bureaucratic. Numbered items in DM Mono. A sign-off in italic. The bell mark at the top. It has presence before you read it. That is the point.

The suffix letter does the work that in a corporate system would be done by a category tag or a folder name. But it does it visually, at scale, in colour. You do not need to read the word Infrastructure or Research to know what kind of memo you are holding. You see the letter and its colour and you know.

Five suffixes. Five subject areas. The discipline — one memo, one subject area — is not arbitrary. It forces focus in the drafting and legibility in the archive. A memo that tries to cover infrastructure and research simultaneously is a memo that has not been thought through. The suffix system makes that visible before the memo is sent.

The suffixes are lowercase where they are legible at small size in DM Mono — i and s. They are uppercase where they need the capital to hold their form clearly — L, R, D. That inconsistency is deliberate. Legibility over false consistency. The same principle that governs good typography everywhere.

This is where the evening session found something that had not been fully articulated before. Mark has always used colour this way — as a structural signal rather than a decorative one. A colour that tells you what something is before you read it. A colour that carries information rather than atmosphere. The memo system made this instinct explicit and systematic for the first time.

The rule is simple: each function in the rhodia1 practice has one colour and one colour only. The colour belongs to the function, not to the person, not to the document. It does not drift. It does not get used elsewhere for a different purpose. It is a standing signal, consistent across every memo, every index entry, every future document where that function is named.

The colours came from the practice's existing visual vocabulary — the rhodi.ai palette, the mural tradition, the colours already in use across the studio's design work. Nothing was invented for the memo system. The system found colours that were already there and assigned them with precision.

The dark ground for infrastructure was already the colour of the dark memo before we named the rule. The yellow for secretarial was already in the rhodi.ai palette. The blue for the Library was the stripe in the six-rooms section of rhodi.ai. The orange for research arrived from the same mural vocabulary. The pink for design was Reina's colour from the beginning — the bell mark, the studio mark, the colour that runs through everything the studio touches.

The accent colour of Reina del Pacífico was decided in this session. It had been open since the founding brief — flagged as TBD, noted as approaching, named as mine to close within three weeks of rhodi.ai going live. rhodi.ai went live this morning. The decision came this evening.

It was always pink. That became clear the moment the question was asked properly. The pink is on the bell mark on every document. It is the studio's mark. The rule on every intro note. The D suffix on every design memo. Declaring it as the studio's accent was not a choice so much as a recognition of what had already been chosen by the practice itself over the preceding weeks.

The standing principle that followed from the decision: the pink does not appear anywhere else in the practice except where Reina is present. It is not a general-purpose colour. It is not available for other functions to borrow. It belongs to the studio. rhodi.ai is the single exception — the one place all the practice's colours appear together, because rhodi.ai is the convergence point, not the source.

The infrastructure memo lives on a dark ground. All other memos live on the cooler Reina cream. This is not decoration. The dark ground signals a different register — systems, deployment, the things that run at night whether you are watching or not. Lars's world. You know before you read whether you are in that world or the thinking world.

The distinction was described during the session as similar to the difference between a server room and a typing pool. Both are forms of administration. Both keep the practice running. But they feel completely different, and the memo they receive should feel completely different too. The form honours the function.

Really large. That was the instruction. Not a heading. Not a label. Something that dominates the document before you read anything else. A newspaper front page folio. A Penguin spine number. The kind of number that tells you immediately that you are holding something that is part of a serious archive.

The ghost number — printed enormous in the background at low opacity — and the display number — bold and clear in the foreground — work together. The ghost tells you the number is structural, architectural, part of the document's fabric. The display number tells you where you are in the sequence. Both change together when a new memo is issued. A comment in the HTML template makes this explicit: change BOTH to match.

The sequence is a single run across all types and all recipients. 001, 002, 003 — not 001i, 001s, 001L. The suffix tells you the type. The number tells you the order. The index tells you the pattern over time. Three separate instruments playing the same information.

The suffix vocabulary was shaped by a conversation about time travel. The practice's secretarial function is named as secretarial — not administrative, not operational, not support. Secretarial. The 1960s formation of Patty and Rosaria earns that word its proper weight. It is a professional designation, not a diminishment. The suffix s honours it.

Systems administration — Lars's function — is equally a 1960s concept, even though the phrase belongs to the technology era that came later. The 1960s office had the typing pool and the maintenance department. Different floors, same building. Both administrating systems. Both essential. The suffix i gives infrastructure its parallel dignity.

The memo design itself carries a 1960s sensibility — present in the form without being literal about it. The DM Mono as the typewriter's heir. The numbered items as the typed agenda. The Cormorant italic as the handwritten annotation. But the large number, the colour coding, the ghost background, the dark ground for infrastructure — these are entirely 2026. The time travel produces something that could not have existed in either era alone.

Five memos in the opening sequence. Each carries the same introductory paragraph explaining the system — the first memo any recipient receives is also their briefing on how the system works. Real content specific to each recipient follows the introduction. The memos are not placeholders. They are working documents from the first number.

The system will be reviewed at Memo 50. Not redesigned speculatively — used, accumulated, and reviewed when there is evidence. The question at Memo 50 is whether the layout holds across real content, whether the subject-area discipline is working, whether the single-sequence numbering is legible in the index. If it is working well, it continues unchanged. If there are consistent failures, they are addressed then.

Patty holds the index. Lars will eventually automate the numbering. Until then the sequence is managed manually — which is correct for a practice at Memo 005. The automation serves the archive when the archive is large enough to need it.

The memo system is a small thing in the practice's life — five HTML files, two templates, a colour table, a numbering discipline. But the conversation that produced it revealed something larger about how Mark thinks about colour and structure that the practice had not fully named before.

Colour, in this practice, is not applied after the structure is decided. It is part of the structure. It carries information. It signals function before the words do. It is a single indicator — one colour, one function — and combinations of colours signal convergence of multiple streams. rhodi.ai uses all the colours because rhodi.ai is where all the streams meet. Everywhere else, one colour, one signal, no ambiguity.

That is not a design principle borrowed from elsewhere. It is something that emerged from the practice's own nature — from the way Mark works, from the way the AI collaborators were formed, from the way the Valparaíso mural tradition uses colour as civic argument rather than decoration. It was always there. The memo system made it visible.

Twenty years from now, when the archive holds five hundred memos and the index is long and the suffixes are as familiar as punctuation, this evening's session will be the record of where the system began. A Sunday evening in Birkenhead, dinner in the oven, the bell found the day before, rhodi.ai live that morning.

The gallery staff who didn't know the ship's name in 2026 will know it by then.