The future of agentic brands
Developing brand systems for clients to use alongside agents.
A typeface can be named in a guideline, but the reason it belongs to a brand requires further explanation. So does the difference between a composition that follows every rule and one that just feels right. So, how much of the thinking behind those choices can travel with a brand after we hand it to a client?
At Cara, that question is beginning to change what we consider a complete brand system.
An ecosystem of decisions and judgement
A brand identity takes shape through choices about what deserves emphasis, what can be quiet, and how much variation it can hold. Those choices give an identity its character. Some choices become clear rules, while others remain in the designer’s judgment. They stay visible across a body of work but difficult to recover from any single example.
We want to get more precise about the entire ecosystem behind a choice. A color value is easy to record, but explaining why that color occupies a small part of a composition asks more of a designer.
Writing this type of reasoning down is itself a design exercise. It can reveal where a system is coherent, where it depends on an unspoken preference, and where it needs room for interpretation.
So, what is this?
An agentic brand system brings those decisions together with the assets, guidance, and working examples an agent can use to make something. A template can show how a treatment belongs in a composition; code can preserve its behavior when the text or format changes. The guidance explains when to use it.
What we’re testing
Below is an example spec from our brand expansion work with Fuser Studio. The original brand work includes a documented visual library, templates, and a custom grid tool. We’re bringing selected parts into code and adding guidance an agent can read.
The browser below pairs those notes with rendered examples. This is a working study of how the original design decisions can become material to build with.
We’re adapting the brand-kit structure in Kortix’s open-source Suna repository, which draws on Little Plains’ model. A starting file directs the agent to the right guidance, a shared values file generates the tokens, and decision notes keep the reasoning and unresolved questions alongside the work.
Selected excerpts from the study. The agent-readable layer is a new experiment alongside the original work.
Continuity and adaptability
Handoff is only one moment in this process. The actual system begins taking shape much earlier, while an identity is still being explored and decisions are still open.
We’re interested in a practice where guidance develops alongside the brand. A template can test whether a rule is useful. A tool can make a particular visual technique available to more people. A new application can expose something the original system never resolved.
There is also an authorship question here. As more people and agents contribute, someone has to decide which changes belong to the brand. That reasoning should remain available to be understood, challenged, and revised.
A system that only reproduces the graphics already made tells us something about consistency. We’re more curious about what happens when the system is met with a brief the original designer never anticipated.
What we’re building towards
What do next steps look like? Right now, making guidance useful as the brand evolves. Decision approvals should carry through to the kit and its working examples, with enough context for someone new to apply it.
We’re exploring how to make that connection more dependable through current work.
If you’re building a brand and thinking about how your team will keep making work with it, get in touch. We’d love to explore this with you.
A quick note of thanks to Little Plains for sharing their thinking on agentic brands so openly. Their writing has helped shape this exploration.