Brand guidelines

The mark is a seal.

RiskMandate produces a record somebody puts their name to. The mark says that before a word is read: a stamp with a monogram inside it, registration ticks on the axes, and a quiet inner ring. It signals counter-signature and provenance to the audiences that matter — underwriters, risk committees, boards.

01 · The mark

One mark, three fidelities.

The containered mark is the default. The knockout drops the container for dark surfaces where a filled tile would sit heavily. Below 24px the detail genuinely dies — so there is a simplified cut rather than a blurred one.

02 · Rules

Five things not to do.

Do not recolour it

The green is #1A7F5A and the container is #161615. The mark never appears in another hue, and never in full colour on a coloured field.

Do not use the detailed cut below 24px

The registration ticks and the inner ring turn to mud. Use the simplified mark, which keeps the ring and the monogram only.

Do not stretch, rotate or add effects

No drop shadows, no gradients, no outer glow. A seal that looks printed is doing its job.

Do not redraw the monogram

RM is set in the mono face at a fixed optical size inside the ring. It is not a text layer to be re-typeset.

Do not crowd it

Leave clear space of at least half the mark's width on every side. In a UI bar that means the mark, a gap, then the wordmark.

And the honest caveat from the concept itself: seals skew traditional. Used heavily and at large sizes it can make a young company look like a compliance vendor. Keep it small, keep it quiet, and let the typography carry the personality.

03 · Colour

Ink, green, warm greys.

Every colour in the product is a token. Nothing is a literal hex outside the token block — the same rule the code follows.

04 · Typography

System faces, deliberately.

No web fonts, no CDN, no flash of unstyled text, and nothing to load before the page is readable. The system sans carries everything; the system mono carries labels, keys, numbers and anything that should read as machine output.

Display

Know the risk.

clamp(28px, 3.8vw, 46px) · 700 · -.03em

Body

Every acceptance carries a named owner and an expiry, so the decision comes back.

15.5px · 400 · 1.7

Mono label

ACCEPTED CONDITIONS · 4/4 HOLDING

10px · 700 · .2em · uppercase

05 · Downloads

Take the assets.

SVG for anything that scales, PNG where a raster is required, EPS for a printer. All served from the vault.

About the EPS. Conference stands and print shops ask for .eps and reject everything else as pixelated. These are real vector, drawn from the same geometry as the SVG, with one deliberate difference: the lettering is converted to outlines rather than named as a font, because an EPS that names a font is an EPS that looks different on somebody else’s machine and we never see the proof. No background is painted, so the artwork drops onto any ground. The letterforms are Geist, which this site self-hosts under the SIL Open Font License. Written by scripts/site/render-brand-eps.py and proofed by rasterising the file that ships.

06 · Boilerplate

And the words.

Anybody who asks for the logo asks for a line about us in the same breath, so both live here. Eight lengths, saying the same thing in the same order, so choosing between them loses detail and never changes the claim. Paste the longest one the field accepts.

Long 269 words · 1491 characters · profile or about page

RiskMandate creates and sells Agent Behaviour Policies. An Agent Behaviour Policy is a working record, for one agent in one deployment, of four things: everything it can actually reach, what you authorised it to do, the gap between those two, and what stands in the way. Three of the four can be written down by the people who run the agent. The fourth, the gap, is worked out from the first two, and it is usually the one nobody has looked at. It is a portable vault rather than a document, because four audiences need different things from one record. The operator needs instructions, leadership needs a decision, security needs evidence, and an insurance conversation needs explicit scope and open questions. One record, several views, with a named owner, a review trigger and every version kept. A policy is a draft, and it is meant to be argued with. It goes to the people who built the agent, the people who own what it touches and the people accountable for it, and each corrects the part they know. It is never finished, because the agent is not finished. The question it answers is not what model somebody bought. It is what the agent can do that nobody in the business has fully understood yet. That is not a property of the model. It is a property of this deployment, so a policy is fitted to a twin of the environment the agent is actually in. That is where a generic shape stops being generic and becomes yours, and it is the only point at which the exposure means anything.

The full version. The third paragraph is what is being sold rather than a description of it, and the last is the one that matters: risk is a property of the deployment, not the model.

Medium 85 words · 462 characters · directory or listing entry

RiskMandate creates and sells Agent Behaviour Policies: for one agent in one deployment, a working record of everything it can actually reach, what you authorised it to do, and the gap between the two. It comes as a portable vault rather than a document, with a view for each audience, a named owner and every version kept. Risk is not a property of the model but of this deployment, so the record is fitted to a twin of the environment the agent is actually in.

The one to send when no field limit is visible. Safe under almost any cap and reads as finished rather than truncated.

Profile 73 words · 396 characters · a company profile with a 400 cap

Create or buy Agent Behaviour Policies: for one agent in one deployment, what it can actually reach, what you authorised it to do, and the gap between the two. It arrives as a portable vault with a view for each audience, a named owner and every version kept. Risk is a property of the deployment rather than the model, so each one is fitted to yours. Open source, and sixteen are published free.

Cut to fit Web Summit’s 400-character company overview on 24 September 2026, which the 462-character version above overshoots. It is the medium one with the drafting dropped and the reader’s verb at the front, and it keeps the sentence about the twin, because that is still the half nobody else is saying.

Short 45 words · 258 characters · a card, a tile, a panel

RiskMandate creates and sells Agent Behaviour Policies. For one agent in one deployment, a portable record of everything it can actually reach, what you authorised it to do, and the gap between the two, fitted to a twin of the deployment it actually runs in.

Where there is room for a sentence and no more. Gives up the vault and the drafting, and keeps the twin, because that is the half nobody else is saying.

One line 31 words · 180 characters · strapline or badge

RiskMandate creates and sells Agent Behaviour Policies: for one agent in one deployment, what it can actually reach, what you authorised it to do, and the gap nobody has looked at.

A strapline field, and what this page called the floor until a form refused it: Web Summit’s exhibitor description rejected 180 characters on 23 September 2026. The two below exist because of that. They drop the company name rather than the claim, because a directory has already asked for the name in the field above.

Directory 65 words · 395 characters · a conference listing, written to start a conversation

Create or buy Agent Behaviour Policies: for one agent in one deployment, what it can actually reach, what you authorised it to do, and the gap between the two. Delivered as an encrypted vault with stakeholder views, fractal semantic graphs, prompts and toolkit. Risk is a property of the deployment rather than the model, so each one is customised. Open source with multiple commercial services.

The lead’s own line, and the only one written to be asked about rather than to be complete. It opens on what the reader does, and it names four things a technical reader will want to push on: stakeholder views, fractal semantic graphs, prompts and toolkit. Two of those run today and two are drawn; the page they land on says which is which, node by node, so the curiosity has somewhere to go. Use or rather than and: it is a choice between two ways in.

Badge 20 words · 110 characters · a field with a hard cap

Agent Behaviour Policies: what one agent can reach, what you authorised it to do, and the gap between the two.

The shortest one that still carries all three objects and the verb on each. Reach for this first when a counter is ticking down.

Chip 12 words · 80 characters · the floor

Agent Behaviour Policies: what one agent can reach, against what you authorised.

Two of the three objects, with the third implied by against. Below this the sentence stops being a claim and becomes a category, which is the line the one above used to hold.

None of these names a customer, a funder or an insurer, and none attaches an adjective to anybody else’s product. Every sentence is a definition of one of our own terms or a statement about our own work. British spelling throughout, and no dash in any of them.

Using the mark somewhere we have not thought of?

Tell us what you need and we will cut it — a new size, a different lockup, a format we have not shipped.

See the concepts we did not pick