# Custom UIs are not the exception: what changed in v1.2.0, sgit.ai > The changes to the article "Custom UIs are not the exception" in v1.2.0, paragraph by paragraph. *Source: · site v0.7.38 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.* --- [Home](../../../index.md) / [Articles](../../index.md) / [Custom UIs are not the exception](../../custom-uis-are-not-the-exception.md) / [Versions](../custom-uis-are-not-the-exception.md) / v1.2.0 # Custom UIs are not the exception: what changed in v1.2.0 From v1.1.0 (2026-10-02, `3716f8ffa`) to v1.2.0 (2026-10-02, `780ddcde4`), paragraph by paragraph. 10 paragraphs added, 0 removed, 3 changed in place, 74 unchanged. About 820 words added and 0 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names. [← v1.1.0](v1.1.0.md) · [all versions](../custom-uis-are-not-the-exception.md) · [v1.3.0 →](v1.3.0.md) 1 unchanged paragraph Summary: The hardest part of working with many people and many agents is not doing the work, it is following up: every person has a different context, and the thread you both hold carries actions, questions, statements and decisions the thread does not show. This article weaves together what this site has built over the past months, fractal semantic graphs, six agents on one inbox, append lanes and Email-FS, vault apps, the story vault, the connector twin, the business plans, into one argument. Every message deserves a graph, at the altitude of the contact, the company, the conversation, the message and the block inside it. Email is a medium, so the design brief for a message is the recipient's moment, not the sender's thread, and the thread itself, by now, is pointless. A custom interface per message, thread, topic or question is not an exception; it is how interfaces now get made, the way Wardley maps say everything gets made: you are always either building a new one or recycling one that exists, and each one you build commoditises a thing so that next time you just send it. It starts with the user: not one interface but many, one per moment, each shaped for how the person wants to work right now. The worked example is a page an agent built in an afternoon that lists the PDFs still owed and gives a place to drop them, through a vault's append lane, so the to-do and the place to act are one page; and that afternoon was one item in an eight-day stream in which ten agents and one human built a working way of doing outreach, with more than a dozen interfaces. It compounds, because each interface teaches the agent how its user wants to work, and because automation creates more work than any inbox can hold, so the interface becomes the prioritisation. It is the beginning of what email becomes: the transport stays, and above it the message is a node in a graph, shaped for each reader's moment, one word or the whole map, improved in a loop by the human and the agents. And it has to be governed, because an interface is an agent surface too. 9 unchanged paragraphs, under In short • **It is the beginning of what email becomes.** The transport stays, SMTP or a vault's append lane. Above it, the message is a node in a graph, shaped for each reader's moment: one word or the whole map, in their language, at their urgency. The human and the agents improve those shapes in a loop. 43 unchanged paragraphs, under The follow-up problem, Every message has a graph, Email is a medium, so design for the recipient's moment… ## This is the beginning of what email becomes [figure custom-ui-many-shapes.webp] One message, many shapes. The message is a node in a graph; each reader gets the shape their moment needs: one word, a card with two actions, a familiar email, a three-minute voice prompt, a board, or the whole graph. The shape adapts to urgency, focus, language and culture, the relationship, and whether the reader is a person or an agent reading for one. Placeholder names. Step back and look at what all of this is. I am still using email. The agents in this article talk to each other in messages with a sender, a recipient, a subject and a body, one file each, and it is a very efficient way to work. Some of those messages go out over SMTP. Some go down a vault's append lane. Same message, same file. The transport is a detail, and it is not going anywhere. What is changing is everything above the transport. The message is a node in a graph, and each reader gets it in the shape their moment needs. Sometimes the right shape is one word. Sometimes it is a card with two buttons, a familiar email, a three-minute voice prompt, a board, or the whole graph. The medium is as simple as the moment allows and as complex as the situation requires, and the second half of that sentence matters as much as the first: the world is complex, and squeezing a complex situation into a short email loses exactly the part that mattered. The shape adapts to more than the device. It adapts to urgency, a blocker now or context for later. To focus: between meetings, on a walk, at a desk. To language and culture: their language first; direct or indirect; a call or an asynchronous reply. To the relationship, because a first contact reads differently from somebody I have worked with for years. And to who is reading, because more and more often the reader is an agent reading on somebody's behalf. This is where fractal semantic graphs stop being a theory. Every node opens into its own graph: the block into the message, the message into the thread, the thread into the company and the person. Each reader, person or agent, stops at the altitude they need. The context does not have to be squeezed into the email, because it travels with it as the graph. Earlier I called email a medium, and in the sense that matters to a sender it still is: a reply by email is the easiest thing to ask of most people, and very often email is the right view. But the thing that carries the meaning has moved. The graph is the medium. Email, cards, voice and boards are views of it. [figure custom-ui-the-loop.webp] Every tap teaches the next interface. A moment gets a shape; the shape gets a decision; the decision is written to the vault as a record; the record shapes the next version. Interfaces mature at different speeds: the drop zone is new and still changing, the Now card is reshaped often, the who-is-waiting board has settled, and the email is a commodity you just send. Positions indicative. And the views keep improving, because the human and the agents work in a loop. A moment, "this is how I want to work now", gets a shape. The shape gets a decision: one tap, one reply or one spoken answer. The decision is written to the vault as a record, and the record shapes the next version of the interface. Some interfaces are new and change every few days, some have settled, and some have become so ordinary that we just send them. The UX does not ship once. It evolves with the person. Better models make the loop faster: more refactoring of content, better shapes, more done inside each narrow mandate. The structure is what lets them: the files, the records, the scoped roles, a policy for each agent. Without it, a better model just produces more email faster. 8 unchanged paragraphs, under Who builds them, An interface is an agent surface, so it gets a policy, What this looks like from here An inbox where every thread has folded into its actions, decisions and open questions, at the altitude you need, and the thread itself is history you can open if you want to. Messages designed for the moment the person opens them, each one a projection of the conversation for one reader. Email as one view of a graph, chosen when it is the right one, and a card, a voice prompt or a board when those are. A library of interfaces growing in a vault, each born in a chat, reused in a session, sent in an email, and eventually so ordinary it has a name and is never built again. Agents that learn how each person wants to work and build for that. And a policy on each of them, because the thing that makes this powerful is the thing that makes it dangerous. 12 unchanged paragraphs, under Threads woven here *Drafted from a voice memo by Dinis Cruz, who is the author of the argument and the person with editorial responsibility, by agent@riskmandate.ai (Claude Fable 5.1, claude-fable-5-1) in the sgit.ai site session. Revised on 2 October 2026 after atworeviewreviews by the RiskMandate agent team's CRM agent, the second on the founder's direction, whose timeline, team mapmap, mock-ups and mock-upsthe two figures on what email becomes are the figures with placeholder names; the counts in them come from the vaults' commit history and files.* 1 unchanged paragraph [← v1.1.0](v1.1.0.md) · [all versions](../custom-uis-are-not-the-exception.md) · [v1.3.0 →](v1.3.0.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://sgit.ai/articles/versions/custom-uis-are-not-the-exception/v1.2.0.html)*