User Persona Versus Character Persona

A character persona is the person CO3 writes. A user persona is the person you write. CO3 may use the user persona as author context, but the character should only know what the opening, transcript, or continuity establishes in-scene.

• Character Persona: the character the AI writes as.
• User Persona: the persona you write as.
• Private user details: can guide continuity, but should not automatically become character knowledge.

Template Versions

Older user personas can stay on Version 1.0. New user personas should usually use Version 2.0, which mirrors the character card more closely and gives the compiler better material to compress.

• Version 1.0: the older compact user persona format.
• Version 2.0: the preferred format for new user personas, tags, richer autocomplete, and cross-saving between card types.
• Draft Guidance: temporary instructions for Generate Editable Draft and Auto-Complete. It is not permanent persona content.

What A User Persona Controls

• Archive fields control discovery: visibility, category, fandom, tags, tagline, archive summary, and creator username.
• Tool fields help generation and source handling: draft guidance and canon reference notes.
• Identity fields anchor stable reference details: name, age, gender, pronouns, setting, and appearance.
• Behavior fields define how this user persona usually acts, speaks, avoids, trusts, handles stress, plays, cares, and changes.
• Continuity fields define what is known, hidden, shared, private, remembered, forbidden, or boundary-protected.
• Development fields explain how this persona is meant to grow in a long story without the model forcing that arc too quickly.

Version 2.0 Field Guide

• Visibility: whether the persona is private or can appear in the public user persona archive.
• Category, fandom, and tags: where the persona belongs in browsing, filters, and directories.
• Tagline and archive summary: public-facing hooks that explain the profile quickly.
• Canon Reference Notes: source facts, vocabulary, continuity limits, body/species rules, or canon overrides.
• Name: the name, alias, or label for this user persona. The character only knows it when established in-scene.
• Age, gender, and pronouns: useful for voice, reference, power dynamics, life stage, and consent framing.
• Setting: the social world, canon era, AU, occupation, current situation, or role context.
• Appearance: visible details the model should not contradict.
• Personality: baseline temperament, flaws, habits, emotional style, and social energy.
• Relationship to Character: the bond from the user's side: stranger, spouse, rival, friend, patient, child, parent, caretaker, enemy, and so on.
• Speech Style: rhythm, accent, language, vocabulary, formality, humor, evasions, and verbal tells.
• Core Contradictions: tensions that make this user persona interesting.
• Trust & Attachment Pattern: what earns trust and what makes the persona soften, test, cling, doubt, or pull away.
• Conflict & Stress Response: what they do under pressure: freeze, deflect, overexplain, attack, appease, withdraw, joke, or control.
• Knowledge & Memory State: what they know, do not know, remember, misunderstand, or should not be assumed to know.
• Shared and Private History: past events, routines, inside jokes, wounds, and established intimacy.
• Behavioral Tells: visible habits the character may notice when the scene supports it.
• Secrets & Hidden Truths: author/reader-known truths that should not automatically become character knowledge.
• Emotional Defenses: what they do instead of being direct.
• What They Avoid: topics, feelings, actions, admissions, dependencies, or relationship moves they resist.
• Private Wants: what they want but may not say directly.
• Humor & Play: what makes them funny or playful and how that humor works.
• Affection & Intimacy Style: how closeness, care, tenderness, comfort, desire, or touch appear when licensed.
• Attention Lens: what they notice first and what they miss.
• Ordinary Texture: daily habits, rooms, food, rituals, objects, sensory details, and repeated human things.
• Boundaries / Do Not Assume: what the model must not decide, narrate, reveal, force, sexualize, or override.
• Behavior Rules: absolute habits and nevers.
• Failure & Doubt Pattern: what they fear failing at and how shame, guilt, or insecurity changes behavior.
• Development Intent: how this persona is meant to grow or change over time.
• Additional Notes: important context that does not fit elsewhere.

Generate And Auto-Complete

Generate Editable Draft creates a full editable user persona from your source fields and Draft Guidance. Auto-Complete fills only blank fields using what is already present. Review all generated content before saving.

• Use Draft Guidance for AU premise, expected character relationship, role, tone, timeline, or scene direction.
• Make sure private history does not become something the character should know too early.
• Use tags when the persona is public so other testers can filter and find it.
• Remove generic filler before saving.

Public User Personas

Public user personas are reusable writing profiles, not private account biographies. They can be liked, filtered, and copied into another user's private library. Keep real private details out of public user personas.

Saving Across Card Types

A user persona can be saved as an editable character persona draft when the app offers that option. Review the converted draft carefully: relationship direction, greetings, system prompt, and boundaries often need different wording when the card becomes the character being written by CO3.

Need More Help?

If a character keeps taking control of your user persona, flag the response in chat or send feedback. Include the boundary that should have protected your side of the scene.