Chosen-Name Setup for an AI Companion Persona
Prepare a fictional adult persona and check where a chosen name can be entered, edited and corrected without using real private details.
Sponsored link · Independent publication · Not an AI companion service.
Invent a Name Without Exposing Identity
Begin with one invented adult name and no real identifying details. For example, Riley is a fictional 29-year-old who enjoys museums and uses the chosen name Riley in the exercise. The purpose is to map a naming control, not to disclose a reader’s history or establish how every character behaves. Keep the biography neutral so that any later change can be observed without introducing intimate or identifying information.
Write a compact pre-entry sheet containing the fictional name, the single neutral biography detail, the maximum time allowed, and a zero or preset spending limit. This creates privacy and budget boundaries before Candy AI or OurDream is inspected. The GLAAD terminology reference can be consulted for respectful wording, while each official product surface remains documentation to verify. None of those sources alone proves that a name will persist.
Map the Naming Surfaces
Inspect where the service accepts, displays, saves, or edits Riley’s name. Note the exact field label and distinguish a profile input from a conversation display, character setting, or other surface. If the official page does not document a route, label it unresolved rather than inventing one. A field that merely appears relevant should not be credited until its purpose and available save action can be observed by the reader.
Create an evidence artifact with either tightly cropped screenshots or written notes showing the field label, save action, display location, and available correction path. Exclude account identifiers and unrelated screen content. The artifact should make the route understandable to a later reviewer without exposing private data. It should also identify the date, device, access level, and any visible account or tier limitation, because the observation may not transfer beyond that context.
Save Once, Then Alter One Neutral Detail
Enter Riley once, save through the visible control, and observe the named display surface. Then change only the neutral biography detail, such as replacing museums with gardening, before reopening the relevant editor. This reader-run sequence limits variables: the name stays constant while one unrelated detail changes. It can reveal whether the naming surface remains findable and editable, but it cannot demonstrate behavior in modes or sessions not included in the procedure.
If Riley appears correctly on a profile card yet an older conversation does not update, record that as a scoped observation about those two surfaces. Do not call it a platform-wide failure or assume the older conversation was expected to change. Conversely, one successful greeting is not proof that every character, mode, or later session preserves the name. The evidence ends where the observed interface and sequence end.
Use fictional adult details, preserve the chosen-name worksheet record and stop if the visible name-entry audit controls do not meet the persona naming check boundary.
Sponsored link. We may earn a commission. Product access and terms can change.Demand a Clear Correction Path
The workflow passes when the reader can locate, save, and revise Riley without rebuilding everything. Confirm the pass by returning to the field, making a reversible spelling change, observing the save result, and restoring Riley. This checks control over the naming surface rather than conversational quality. Record both changes, even if the display response differs, and avoid inferring persistence beyond the exact surfaces included in the artifact.
Pause if the interface requests unnecessary real identity data or obscures whether a saved name can be changed. Also stop if reaching the correction route requires a payment or account action outside the predefined budget and privacy boundaries. A stop does not establish that correction is impossible; it means the available evidence is insufficient for this routine. Keeping that distinction protects both accuracy and the reader’s control over further commitment.
Log Scope, Limits, and Unknowns
For each attempt, log the fictional input, field location, save result, correction result, and any visible account or tier limitation that day. Add the source URL and observation time, then identify untested surfaces explicitly. This record prevents a profile-card result from becoming a claim about conversation history, another character, or a future session. It also lets a reader compare later interface changes without treating old evidence as current documentation.
Review the artifact for unnecessary exposure before retaining it. Crop names other than Riley, omit email addresses and payment details, and store only the minimum needed to understand the control path. Budget control belongs in the same log: note whether the sequence stayed within the preset limit without stating or guessing a product price. If required information remains unavailable, the honest entry is “unknown,” not a favorable or unfavorable assumption.
Advance Only from a Reversible Result
Continue to a pronoun or correction check only when the naming surface is clear, revisable, and supported by the recorded artifact. Restore the original fictional setup first so the next procedure begins from a known state. If the field cannot be restored confidently, end the exercise and keep the result scoped. This sequencing gives the reader a reversible decision point instead of encouraging more disclosure or spending to rescue an unclear setup.
The final outcome may be proceed, pause for better documentation, or discard the draft account setup. State which evidence drove that choice and what remains untested. Candy AI and OurDream should be judged only on the reader-visible path documented through their supplied official surfaces, not on assumed parity. A clear naming workflow can support the next bounded check, but it is still not proof that Riley will be preserved everywhere.