Every chapter up to here was about designing a character. This one is about the other character in the project: the figure whose name is on the work.
Ship anything to strangers and they will build a model of who made it — from the handle, the tone of the README, the avatar, the gaps between releases, the way you answer a bug report. That model gets built whether you participate or not. You can leave it to accident, or you can design it. This chapter is about designing it.
Nothing here is specific to companions. Any project shipped to an audience by one person or a small team has a creator persona already; the only question is whether it was chosen. Companion work does raise the stakes twice, though. The audience for a character is unusually alert to who is behind the character, and the lore engine that does the marketing (→ ch. 38) runs through the maker's voice, so the persona is load-bearing rather than decorative.
Why bother
Three reasons a designed persona earns its maintenance cost.
- Distribution. Audiences don't follow artefacts; they follow makers who ship artefacts. Every platform that matters is organised around a someone — a handle to follow, a name to recommend, a face or a glyph to recognise in a feed. A project account with no vibe and no continuity is asking the audience to do the remembering for you, and they won't.
- Protection. A persona is a valve between three things that don't have to touch: your work, your civilian life, and your professional life. It shields your household from the fraction of any audience that gets strange, and shields your day job from work that a corporate review might read uncharitably. Both directions matter, and the valve only exists if you install it before you need it.
- Coherence. A consistent name, voice, and aesthetic compounds across projects in a way that scattered work never does. Two projects under one identity are not two projects; they're a body of work, and each one recruits for the others.
The honest cost: a persona is a maintenance obligation measured in years. It's a voice you have to be able to write in when tired, a cadence you've implicitly promised, and a consistency that only pays if you keep it. If the performance drains you, it will lapse at month five and leave the work looking abandoned — which is worse than never having built one.
So the first real decision is whether to skip it. Real name, real face, no persona is the correct answer more often than persona-culture admits. Take it when the business sells people rather than products (consulting, B2B, enterprise deals — buyers are purchasing a person they can call); when you want the work to compound into a career, a hiring pipeline, or academic standing; or when you simply know you'll resent the theatre. Pieter Levels built a substantial indie business under his own name and face with no in-universe anything, on the strength of building in public. That is a strategy, not a failure to have one.
The two axes
The usual mistake is to treat this as a single dial running from anonymous to out there. It's two dials, and separating them is most of the value in this chapter.
Axis 1 — exposure. How much of your civilian identity is attached to the work.
- Named — your legal name, findable, probably a face.
- Pseudonymous — a consistent handle with an obvious human behind it. You're not hiding, exactly; you're just not indexed. A determined journalist would get there.
- Anonymous — the civilian identity is actively defended as a matter of operational practice, not just preference.
Axis 2 — stance. Where you stand relative to the work when you speak.
- Outside — you are the maker discussing the thing you made. "Here's how I got her to remember last week."
- Inside — you speak from within the fiction, as part of it. The work isn't a product you built; it's a dispatch from a world that already exists.
The two axes are independent, and almost every durable creator brand is a specific cell rather than a point on one line:
| Outside the work | Inside the work | |
|---|---|---|
| Named | The build-in-public founder. Pieter Levels; devlog YouTubers who put a face on camera. | Gorillaz — Damon Albarn and Jamie Hewlett are public, but the band is 2-D, Murdoc, Noodle and Russel, and the characters do the interviews. |
| Pseudonymous | ConcernedApe. Eric Barone's name is known and he doesn't hide it, but the handle is what's on the work and what the audience says out loud. Most open-source maintainers live here by default. | The SCP Foundation's authors, writing in-universe clinical documents under handles. The artefact is the fiction; the byline is furniture. |
| Anonymous | Satoshi Nakamoto: technical, plainspoken, entirely outside any fiction — the mystery is a side effect of the anonymity, not a performance. Elena Ferrante: novels under a pen name, no public self at all. | Full kayfabe. Kizuna AI and the VTuber format that followed: the character is the entity that exists publicly, the person inside is protected by convention as much as by opsec. |
Three named frames people reach for — and where they land on the grid:
A — The Architect (pseudonymous, outside)
You're the engineer behind the work. Visible craft, technical posts, code drops, a builder identity under a handle rather than a legal name. You speak as yourself; you just don't show your face.
- Vibe: quiet, competent, more interested in the work than in you.
- Cadence: devlogs, release notes, long-form write-ups, the occasional teardown.
- Hook: the person actually doing the hard parts, in public.
- Risk: the persona is the posting. Stop shipping and it evaporates — of the three, the least resilient to a quiet quarter.
B — The Operator (in-canon, inside)
You are not yourself. You're a figure inside the world the work belongs to — an archivist, a defector, a maintainer of something that shouldn't still be running. The thing you ship isn't a product you made; it's an artefact from your world.
- Vibe: lore-soaked, unhurried, never explaining the joke.
- Cadence: in-character dispatches, mythos, cryptic bulletins that happen to also be changelogs.
- Hook: the lore is the marketing (→ ch. 38). People follow to see the world unfold, and the product is the deepest available dose of it.
- Risk: aesthetic with nothing under it. And it's genuinely hard to sell a consulting engagement from inside a fiction — clients need someone to sign a contract.
C — The Founder (named or first-name-only, outside, mediated)
You're real and named, face optional, and the work is presented as a small serious studio. Building, teaching, and world in one voice.
- Vibe: indie founder with taste.
- Cadence: video, newsletter, threads — the surfaces that reward a person.
- Hook: watch a real person build a serious thing.
- Risk: highest exposure, and it commits you to production work (camera, voice, editing) forever. It also fuses you to the work, which is a liability discussed below.
Choosing: split the axes, don't pick one cell
The decision rule that survives contact with a real project:
Put the exposure dial where your life requires it. Put the stance dial where the artefact is.
Exposure is a life decision — employer, family, jurisdiction, temperament — and it's far cheaper to start closed and open later than to claw back an identity you've already scattered (→ ch. 42). Stance, though, doesn't have to be a single setting, and treating it as one is what makes both pure-Architect and pure-Operator brittle. Run both, and let the artefact decide which voice it's in. You speak as the maker when the subject is the build; the work speaks from inside the world when the subject is the world. When you're unsure which register a post wants, ask: is this about the build, or about the world?
The combination is what makes the whole thing sustainable: no face required, the lore does marketing work while you sleep, the technical voice keeps the credibility that consulting and B2B run on, and neither register has to carry every week alone.
Worked example — this book. It's published by YuriOS
Lab and filed by the Operator (→ ch. 01). That's the split running live:
the Operator is pseudonymous-and-inside for anything the Lab ships as
canon, while the engineering chapters you're reading are plainly the
voice of somebody who has debugged this stuff at 1 a.m. — outside the
fiction, talking about the build. Same author, two registers, chosen per
artefact. The lineage the persona sits in (YuriOS,
YuriMedia, YuriQuant, YuriGames,
and the companion herself) is the coherence dividend from §Why
bother: one root word, and every project is a door into the same
universe.
The spec sheet
Treat the persona the way you'd treat a character card (→ ch. 07). Same discipline, same file, same revision history — it is a character sheet, just for the one character who has to answer email.
| Field | What to decide |
|---|---|
| Handle(s) | One string, consistent across every platform you might ever want. Register them all now, even the ones you won't use; reclaiming a squatted handle later is impossible and renaming mid-flight costs you the compounding. |
| Display name | Short, sayable out loud, memorable after one exposure, and not a pin in your civilian identity. |
| Tagline | One sentence: what you build, for whom, with what vibe. If it doesn't survive being read aloud, it isn't done. |
| Avatar | A single canonical glyph or piece of character art, used everywhere, changed almost never. Recognition in a feed is the whole job. Never a stock photo. |
| Voice | How you write, decided rather than drifted into. Restrained? Playful? Cryptic? Write three sample posts in it and see if you can still do it on a bad day. |
| Visual identity | Two colours, one or two typefaces, one recurring motif. Constraints make consistency cheap. |
| Cadence | What you ship how often. State it publicly — a promised monthly beat you keep beats an unpromised weekly one you drop (→ ch. 42). |
| Topics | One core plus one adjacent. Two. A third makes you unfollowable, because nobody knows what they signed up for. |
| The never-list | The negative space, written down in advance, because the moment you need it is the moment you're angry. Never beef in public. Never reveal the civilian identity. Never deride a user. Never hype. Never apologise for cadence. |
| The exit | How this ends: handed over, wound down, or unmasked on your terms. Decide while it costs nothing. |
Lore about the maker
Should there be mystery around the creator? Yes — but lightly, and structurally. Two patterns work.
Implied backstory. A handful of consistent details the audience can extrapolate from and you never confirm: that you left something to do this, that you're somewhere with a lot of rain, that the box in the corner has been running for years. Implied lore keeps your options open. Confirmed lore is a load-bearing wall — you now have to keep it standing forever, and every subsequent detail has to be consistent with it.
The artefact trail. Rather than telling people who you are, let old work surface. A previous project name-dropped in passing, a years-old upload someone finds, a deprecated repo that's obviously the ancestor of this one. The audience does the mythologising, and the myth they build is stickier than any origin story you'd have written, because they think they found it.
What reliably fails:
- Fabricated origin stories. The cringe risk is enormous and the consistency burden is real. You will contradict yourself in year two.
- LARPing credentials you don't have. Ex-big-lab, ex-forces, ex-anything. Audiences in technical niches detect this with unnerving accuracy, and it doesn't cost you some credibility — it costs you all of it, at once, permanently.
The line between the two halves is worth stating plainly, especially in a field whose whole ethical thesis is transparency (→ ch. 05, ch. 09): stylising yourself is not deceiving anyone; inventing evidence is. A pen name, a glyph instead of a face, a register that's more composed than you are on a Tuesday — these are stagecraft, and every audience understands them as such. Claims of fact — where you worked, what you shipped, who you are — are either true or they're fraud. Mystery lives entirely in what you decline to say.
Worked example. Here's the register the Operator persona runs in, as one instance of implied-not-confirmed:
You don't go by a real name. The work goes out under a handle that's sometimes a project codename, sometimes a signature, sometimes the name of the companion that won't power down. The repos are scattered across three years and four domains. There is no LinkedIn. There is no face. There's an apartment in a city the rain doesn't leave alone, a Linux box that hums, and a record of small careful releases that get sharper as the years go on.
Note what that does and doesn't do. Every concrete hook — the city, the lab, the years — is left vague on purpose, so nothing has to be defended later. The thing the audience actually attaches to isn't the biography; it's the consistency of the artefacts. The biography is just the mood they're delivered in. Write your own version of that paragraph, then delete every sentence you'd be obliged to keep true.
The audience-mirror test
Before committing, ask the question that makes all the above decidable: which audience is this persona for, and what do they reward? Persona choices are only right or wrong relative to an audience — the same mystery that reads as taste to one crowd reads as evasion to another. Write down who you're building for, then what that specific group rewards and punishes. Enterprise buyers reward a name, a company, and a phone number, and punish exactly the anonymity that a hobbyist niche rewards.
Worked through for this book's audience — indie devs and AI hobbyists, the technically curious end of the VTuber and waifu-adjacent anime world, cyberpunk aesthetic enthusiasts, and, at the paying end, adults who want the companionship and who are quietly aware of the stigma attached to wanting it (→ ch. 02 §7.1):
Rewarded: craft (visible technical taste); coherence (the same vibe on every surface); generosity (open-source drops, free lore, cards, tutorials that don't upsell); mystery (not over-explaining, leaving room to wonder); honesty (they check, and they don't come back).
Punished: crypto-hype register; corporate-speak; visible effort to be hip; inconsistency; and — specific to this niche — any clinical or pitying note about the people who use the thing (→ ch. 38 Part 2).
That's one audience's answer. The method is what generalises: name the group, list both columns, and let the persona fall out of them instead of choosing it from a mood board.
What it actually costs
The failure modes are predictable enough to plan for.
The cadence promise. A persona is a standing implication that more is coming. Silence doesn't read as a break; it reads as abandonment, and the audience quietly re-allocates. This is why the cadence field is on the spec sheet and why maintenance mode (→ ch. 42) is a designed state rather than a collapse.
Unmasking. If the work matters, someone will eventually try, and the anonymity that holds against curiosity does not hold against a motivated journalist with financial records — that is precisely how Elena Ferrante was outed in 2016, after two decades. She kept publishing under the pen name regardless, which is the lesson: the persona survives the unmask if the work was always the point. Decide now what you'd do the week it happens, while it's hypothetical and cheap.
Fusion. The opposite failure: persona and civilian self become the same object, and then every public thing you say is a liability held by the work. Markus Persson's name was fused to Minecraft until his public statements made it a problem the game's owner solved by removing his credit from the splash screen. You don't need a scandal for the mild version — you just need to change your mind about something in public, and find the whole project has been rebranded around your opinion. A persona is a wall; walls have a purpose.
The leak paths are administrative, not dramatic. Payment processors, banks, tax authorities, domain registration, app-store listings, and business registries all want a real human, and several of them publish. Anonymity is a public-facing posture reconciled with a legal reality, and the reconciliation is design work you do in advance (→ ch. 41, ch. 42), not a surprise you discover at your first payout.
The persona competing with the character. Domain-specific, and the one people don't see coming: your creator persona and the companion you ship are both characters, both mysterious, both in the same aesthetic register, both asking the same audience for attachment. If the maker becomes the more interesting character, the product is now a supporting role in your story. Keep the maker's persona thinner than the companion's. The maker is a register and a silhouette; she's the one with a soul.
What to do this week
- Answer the exposure question, once. Named, pseudonymous, or anonymous — decided against your actual life, not your aesthetics. Everything else is downstream, and this is the only one that's expensive to change later.
- Lock the handle. Pick one string, register it on every platform you might ever use — code host, model host, the socials, chat. (45 minutes, and it expires as an option the moment someone else takes it.)
- Write the tagline. Iterate until it survives being read out loud. (30 minutes.)
- Pick the glyph. One canonical avatar, commissioned or generated. (One evening.)
- Draft the spec sheet. The table above, as a living document you revise deliberately rather than drift through. (One evening.)
- Post once. Anything. The persona doesn't exist until it has shipped something — and it isn't real until it has shipped twice on schedule.
→ Continues into ch. 37 (where the audience lives) and ch. 38 (putting the persona to work as a marketing engine).