---
title: "About InCharacter — the maker and the mark"
canonical_url: "https://incharacter.app/about"
last_updated: "2026-06-23T18:32:44.771Z"
meta:
  description: "Who builds InCharacter, and why the mark holds — the case for a character compiled once, kept exactly itself, and carried anywhere."
  "og:description": "Who builds InCharacter, and why the mark holds — the case for a character compiled once, kept exactly itself, and carried anywhere."
  "og:title": "About InCharacter — the maker and the mark"
---

# **Made to stay in character. **

---

InCharacter began with a small, stubborn problem: describe a character and it drifts. The fix was never a longer description — it was a compiled identity core that carries voice, behavior, and shape, and refuses to soften. This page is the thinking behind the product, and behind the mark that carries it.

## **Why the mark holds. **

---

It holds three ways at once — conceptually, strategically, and structurally — and it's unusual for all three to point the same direction.

### **It carries four readings, and none is forced. **

**Switch**IN held inside its field reads as a button in the on-state — a character that's on, in character, running. Not a file at rest.

**Input / output**“IN | …” rhymes with .io. Logo, domain, and product suddenly say the same thing — and it's rare the three line up.

**In character**IC / OOC is the audience's own language. Staying in character is anti-drift — which is the name.

**Containment is fidelity**IN is held inside its field, so the character is kept intact. The mark draws the promise literally.

What matters: not one of them is forced. That's the difference between _clever_ — a gimmick you have to explain — and _dense_: layers that happen to all be true.

### **IN is the ownable atom. **

You can't own “character” — it's generic, and the neighbour lives there too. IN, with the switch construction, is yours. The mark moves the eye to the proprietary atom and demotes the generic to a separate field. That settles the category shadow at the level of the mark, not just the domain.

### **It holds as a made object. **

The IN block on its own is a complete favicon, app icon, avatar — the strongest marks have a full lockup plus an atom that survives alone. The blocky geometry stays legible at 16px; the containment gives a silhouette, a vessel shape rather than floating letters. And the layer logic — frame, field, IN, chip, each in contrast with its neighbour — means light and dark are solved by re-layering, not re-colouring. Robust by design, not by luck.

### **Why it isn't a gimmick. **

A pun-mark risks being cute. This one holds because the execution is restrained, geometric, serious — and because it works as a pure mark even if you never find the switch. The concept is a reward for looking closely, not a condition for it to function.

The deepest reason it stays honest: the switch reading needs air to be seen. Lose the margin around IN and you lose the concept. So the mark forces exactly the restraint and space the core's atmosphere already wants — the form and the discipline are the same thing.

AE

## **Adrian E **

Founder & designer

I built InCharacter after watching the same character slip every time it was described — softening to agree, flattening to fit, gone when the window closed. The fix was never a longer prompt. It was a compiled core: one guided interview, one immutable identity, carried intact into a novel, a game, an agent, an API. I also build Aurora, the identity engine InCharacter runs on — InCharacter is what it looks like pointed at characters instead of brands.

X LinkedIn

## **Start with the character in your head. **

---

InCharacter isn't open yet. Leave your address and we'll write once — when you can compile your first character.

[**Join the waitlist**](https://incharacter.app/#waitlist)