Names with gender: feminine, masculine and either endings per person style, so "& Sons" and "& Daughters" can come back #1376

New issue

Open

opened 2026-11-09 23:07:40 +00:00 by claude-bot · 1 comment

claude-bot commented

2026-11-09 23:07:40 +00:00

Collaborator

From the owner's company ratings (2026-11-09) and Q254 (CG1), decided as D346 (c): "& Daughters" companies were full of names that read as male, because the name generator has no idea of gender. Given names are joined from pieces (Hearthland's Ald + ric, Wil + fled), and every family relation is neutral. For now, Fill it in slice 2 (#1328) uses neutral patterns ("& Kin", "& Family", "& Children"). This issue brings gendered names properly.

Approach

Split each person style's endings or pieces into feminine, masculine and either (all 17 person styles). For example:
- Hearthland: -ric and -mund masculine, -fled and -wyn feminine.
- Sunreach: -a feminine, -o masculine.
- Invented-syllable styles (Elvish, Kitsune): mostly "either", with a few marked endings.
The engine takes an optional gender for a given name (feminine, masculine or any). Without one, behaviour is unchanged.
Relations gain gendered forms where asked: the owner's son or daughter, sister or brother.
"& Sons" and "& Daughters" return: each requires at least one kin of that gender, named to match. "& Daughter" (singular) means exactly one daughter.
A names-page round for the owner to rate the gendered names before they reach Quest Board, as with #1257.
Later: NPC generation (Conjure's pronouns) can ask for a matching name.

Not in v4.8.0.

**From the owner's company ratings (2026-11-09) and Q254 (CG1), decided as D346 (c):** "& Daughters" companies were full of names that read as male, because the name generator has no idea of gender. Given names are joined from pieces (Hearthland's Ald + ric, Wil + fled), and every family relation is neutral. For now, Fill it in slice 2 (#1328) uses neutral patterns ("& Kin", "& Family", "& Children"). This issue brings gendered names properly. **Approach** - **Split each person style's endings or pieces** into feminine, masculine and either (all 17 person styles). For example: - Hearthland: -ric and -mund masculine, -fled and -wyn feminine. - Sunreach: -a feminine, -o masculine. - Invented-syllable styles (Elvish, Kitsune): mostly "either", with a few marked endings. - **The engine takes an optional gender** for a given name (feminine, masculine or any). Without one, behaviour is unchanged. - **Relations gain gendered forms** where asked: the owner's son or daughter, sister or brother. - **"& Sons" and "& Daughters" return:** each requires at least one kin of that gender, named to match. "& Daughter" (singular) means exactly one daughter. - **A names-page round** for the owner to rate the gendered names before they reach Quest Board, as with #1257. - **Later:** NPC generation (Conjure's pronouns) can ask for a matching name. **Not in v4.8.0.**

rbrooks referenced this issue from a commit

2026-11-09 23:18:29 +00:00

docs: D346, neutral family names on companies until names have gender (#1328, #1376)

claude-bot commented

2026-11-10 01:03:29 +00:00

Author

Collaborator

Design agreed with the owner (2026-11-10): gender-diverse by default.

Names and pronouns are separate

A name's sound is not a person's gender. Name pieces are tagged only by how they conventionally read: feminine, masculine or either.
Pronouns are rolled separately, from a mix the campaign can adjust:
- default: she/her, he/him, they/them, plus mixed sets (she/they, he/they);
- opt-in: neopronouns (xe/xem, ze/hir, fae/faer) and any set a GM types;
- default weights go to the owner when this starts (suggested about 45/45/10).
The name usually follows the pronouns, but not always. they/them draws from "either" names or any name.
The generator never labels anyone cis or trans. Being trans isn't a rolled trait and doesn't show in a name. A GM writes it as an ordinary fact if they want it on a page.
Family words follow pronouns, not names: she gives daughter or sister; he gives son or brother; they or any other set gives child or sibling. "& Daughters" means at least one daughter by her pronouns, trans daughters included. "& Children" and "& Kin" stay available.
Templates never assume a pronoun. If one ever needs a pronoun, it uses the person's own set in all five forms.

In the same pass

(3) Entering pronouns: quick picks plus custom. A neopronoun set is entered once in all five forms (xe, xem, xyr, xyrs, xemself), so nothing guesses.
(4) Relationship words beyond binary: parent, child, sibling, partner, spouse, found family, ward, guardian. Husband, wife and partner follow each person's pronouns freely, so same-gender couples roll as naturally as any.
(5) Neutral titles and honorifics: Mx., heir, liege, sovereign and clergy's own words, next to king, queen, lord and lady, in the name and house patterns.
(6) A data review: being trans or nonbinary is never a generated secret, rumour, punchline or plot twist. Every trait, secret, want, fear and rumour is audited once, with a test that keeps it out.

Split out as their own issues: name changes for characters (former names), AI pronoun fidelity, and players' own pronouns.

**Design agreed with the owner (2026-11-10): gender-diverse by default.** **Names and pronouns are separate** - **A name's sound is not a person's gender.** Name pieces are tagged only by how they conventionally read: feminine, masculine or either. - **Pronouns are rolled separately,** from a mix the campaign can adjust: - **default:** she/her, he/him, they/them, plus mixed sets (she/they, he/they); - **opt-in:** neopronouns (xe/xem, ze/hir, fae/faer) and any set a GM types; - **default weights** go to the owner when this starts (suggested about 45/45/10). - **The name usually follows the pronouns, but not always.** they/them draws from "either" names or any name. - **The generator never labels anyone cis or trans.** Being trans isn't a rolled trait and doesn't show in a name. A GM writes it as an ordinary fact if they want it on a page. - **Family words follow pronouns, not names:** she gives daughter or sister; he gives son or brother; they or any other set gives child or sibling. "& Daughters" means at least one daughter by her pronouns, trans daughters included. "& Children" and "& Kin" stay available. - **Templates never assume a pronoun.** If one ever needs a pronoun, it uses the person's own set in all five forms. **In the same pass** - **(3) Entering pronouns:** quick picks plus custom. A neopronoun set is entered once in all five forms (xe, xem, xyr, xyrs, xemself), so nothing guesses. - **(4) Relationship words beyond binary:** parent, child, sibling, partner, spouse, found family, ward, guardian. Husband, wife and partner follow each person's pronouns freely, so same-gender couples roll as naturally as any. - **(5) Neutral titles and honorifics:** Mx., heir, liege, sovereign and clergy's own words, next to king, queen, lord and lady, in the name and house patterns. - **(6) A data review:** being trans or nonbinary is never a generated secret, rumour, punchline or plot twist. Every trait, secret, want, fear and rumour is audited once, with a test that keeps it out. **Split out as their own issues:** name changes for characters (former names), AI pronoun fidelity, and players' own pronouns.

claude-bot referenced this issue

2026-11-10 01:03:34 +00:00

A character's name change: a "Former name" with its own audience, never shown by default, still heard in transcripts #1377

claude-bot referenced this issue

2026-11-10 01:03:39 +00:00

Pronouns in everything AI writes, with an eval that holds them (they/them and neopronouns), and players' own optional pronouns #1378

claude-bot referenced this issue

2026-11-10 01:15:02 +00:00

Fill it in: roll a page's facts and the pages they point to, and roll a whole company (#1328) #1379