Midsummer
Fruit
Tools / Surnames & families

Surnames & families

7 of 7 working tools · editorial release pending

Surnames & families

Fantasy Family Names

Build a fictional house whose members share a surname without becoming interchangeable. Generate a coordinated family, preserve the people you have already chosen, and follow an orchard household deciding whether its record of belonging has room for someone the old register left out.

What makes it different

Invent house morphology and inherit it across the result group.

  • Invented house surname
  • Shared inheritance
  • Distinct given names
  • Locked family members
AN EDITORIAL EXAMPLEMara Briarward

The house surname is invented, with no historical meaning claim.

Read: The Unrecorded BranchComplete original fiction · human review pendingOpen the workbench
Surnames & families

Invented Compound Surnames

Shape a fictional family surname from original word combinations and compare how it feels as a label people carry together. Save the surname as a family identity, explore a workshop’s move to a new shore, and distinguish the household’s name from the business painted above its door.

What makes it different

Return compound boundaries and parts rather than a realistic given name.

  • Compound surname
  • Visible word boundary
  • Family-name card
  • Creative morphology
AN EDITORIAL EXAMPLEAshmere

The family's creative explanation belongs to this story. People keep Ashmere while the workplace receives a different label.

Read: A Name That Could TravelComplete original fiction · human review pendingOpen the workbench
Surnames & families

Blended Family Name Map

Create one household without forcing everyone into one surname. Keep established given names, choose a surname for each member and see the relationship map as a complete cast.

What makes it different

Generates only missing given names while preserving every row’s role and chosen surname. Household membership never automatically assigns descent, adoption or shared legal status.

  • name
  • household row
  • role
  • chosen surname
AN EDITORIAL EXAMPLENessa Vale

Nessa is a personal address Ada can use to ask for company. Felix’s Mum and Ada’s Mum refer to different existing relationships; sharing a flat does not automatically reassign those words or any surname.

Read: The Night Ada Said NessaComplete original fiction · human review pendingOpen the workbench
Surnames & families

Invented Generation Name Pattern Builder

Let a family’s names begin together without making every character answer the same way. Compose original generation elements, keep personal endings distinct and preserve a chosen exception. Follow Samira into a first lesson, where the familiar family sound has something new to ask of her.

What makes it different

Applies one authored word element per declared generation, with separate personal elements and explicit exceptions; does not model a real culture or simply share one surname.

  • person ID
  • generation
  • shared element
  • personal element
AN EDITORIAL EXAMPLERin Doveward

Rin retains her actual given name in the younger generation. Samira and Savenn share Sa but take different places in a beginner lesson; a generation element describes the authored family pattern, not skill or an obligation to help.

Read: The Shallow End on ThursdayComplete original fiction · human review pendingOpen the workbench
Surnames & families

Composite Surname Generations Planner

Follow an original family naming rule through two generations. Supply each side’s explicit surname components, decide their order and limit, and see exactly which parts are retained, repeated or omitted when the next partner joins. Executes component order, NFC/case deduplication, separator and overflow policy at two successive generations. The second step uses only the first step’s retained components; omitted names do not silently reappear. This is not simply joining two random surnames.

What makes it different

Executes component order, NFC/case deduplication, separator and overflow policy at two successive generations. The second step uses only the first step’s retained components; omitted names do not silently reappear. This is not simply joining two random surnames.

  • generation
  • full name
  • ordered source components
  • retained components
AN EDITORIAL EXAMPLEIris Hart-Field

The explicit two-component sequence gives Iris Hart-Field and then Lena Field-Reed. A proposed different surname must be a new choice, not an ancestor component silently returning; the story’s bicycle remains Mara’s decision.

Read: The Bicycle Mara SoldComplete original fiction · human review pendingOpen the workbench
Surnames & families

Fictional Family Archive Identity Linker

Organize an original story’s archive without turning every matching name into one person. Keep dated record labels, alternate spellings and author-confirmed links separate from possible or rejected connections, then choose a caption that preserves the uncertainty. Groups record IDs only through author-confirmed graph edges, preserves possible/rejected links and rejects contradictions with a confirmed chain. Identical spellings stay separate unless explicitly connected. This is an uncertainty-aware record planner, not a genealogy verification service or a list of aliases assumed true.

What makes it different

Groups record IDs only through author-confirmed graph edges, preserves possible/rejected links and rejects contradictions with a confirmed chain. Identical spellings stay separate unless explicitly connected. This is an uncertainty-aware record planner, not a genealogy verification service or a list of aliases assumed true.

  • label record ID
  • grouped record IDs
  • original name forms
  • fictional date labels
AN EDITORIAL EXAMPLERowan Vale

Rowan Vale and R Vale are explicitly connected in the fictional plan; the drum photograph’s identical Rowan Vale remains a different identity. Rowan Hart stays a possible connection, not an inferred surname transition.

Read: The Hinge No One Had SignedComplete original fiction · human review pendingOpen the workbench
Surnames & families

Fictional Place-Derived Surname Workbench

A surname can carry an old place without deciding where its bearer belongs. Build fictional family names from stems you approve, inspect every cut and join, and keep the branches separate when two places leave the same spelling behind. Preserve an exception without inventing its history.

What makes it different

References stable place and branch IDs and executes approved-stem clipping, casing and affix composition with a full trace. Unlike free fantasy syllables or parent-surname inheritance, provenance is explicit; place-label changes cannot silently change the surname.

  • Approved place stems
  • Visible construction traces
  • Distinct branches & exceptions
AN EDITORIAL EXAMPLELantren

Mae and Ro’s branch uses the approved stem Lanter from Lanter Steps: remove er and add ren. Seli’s unrelated Lanter Fen branch intentionally produces the same spelling; Ivo keeps Bracken while his rule preview is Cedaren. These are original fictional constructions, not real etymologies.

Read: A Window Facing Somewhere ElseComplete original fiction · human review pendingOpen the workbench