Midsummer
Fruit
Surnames & families / A MIDSUMMER FRUIT TOOL

Fictional Place-Derived Surname Workbench

Let a fictional surname carry a place without turning a map label into a family tree. Bind each branch to an approved place stem, inspect the exact construction, keep exceptions and compare matching spellings without merging people.

✳ Free to useBrowser-local savingOriginal fiction
YOUR SPECIALIST WORKBENCHRuns locally · No sign-up
A SMALL START, YOUR OWN DIRECTION

Try a complete example first.

See what the tool makes, then change the names or rules that matter to your story.

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.

Uses the visible fictional setup and replaces the form settings. Your saved library is unchanged. Examples are editorial drafts; trying a setup creates fresh candidates.

Start with the identities you already know.

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.

Try a fictional starter above, or open Edit names & rules to use your own source settings. Your spelling and relationship choices remain yours.

Story settings & practical comparisons

Lantren

Surname of Mae and Ro’s explicitly declared branch · Mae and Ro share a branch; Seli’s matching name is separate; Ivo keeps an exception.

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. Inspect the two matching Lantren branches, then the Bracken exception. Change only a place label and rebuild to see its approved stem remain unchanged. Use reject to require resolving the intentional collision.

Exact parameters used by this story
surnamePlaces
steps | Lanter Steps | Lanter fen | Lanter Fen | Lanter reach | Cedar Reach | Cedar
surnameConstructions
fold | | ren | 0 | 2 | preserve | none append | | en | 0 | 0 | preserve | none
surnameBranches
mae | Mae and Ro family | steps | fold | seli | Seli family | fen | fold | ivo | Ivo family | reach | append | Bracken
surnameCollisionPolicy
warn
A fixed surname outside the construction rule

Bracken

Authored practice · editorial review pending; separate from the public story.

  • Bracken
  • Lantren
  • Lantren

Fictional family branch / approved place stem

Bracken is a settled exception; the derivation preview does not invent an earlier surname or a genuine etymology. A place label and its author-approved stem remain separate.

Exact practice settings
surnamePlaces
steps | Lanter Steps | Lanter fen | Lanter Fen | Lanter reach | Cedar Reach | Cedar
surnameConstructions
fold | | ren | 0 | 2 | preserve | none append | | en | 0 | 0 | preserve | none
surnameBranches
mae | Mae and Ro family | steps | fold | seli | Seli family | fen | fold | ivo | Ivo family | reach | append | Bracken
surnameCollisionPolicy
warn
The same branch uses the declared construction

Cedaren

Authored practice · editorial review pending; separate from the public story.

  • Cedaren
  • Lantren
  • Lantren

Fictional family branch / approved place stem

Removing the explicit exception lets Cedar plus en produce the authored surname instead. Two branches sharing a spelling are not automatically one family.

Exact practice settings
surnamePlaces
steps | Lanter Steps | Lanter fen | Lanter Fen | Lanter reach | Cedar Reach | Cedar
surnameConstructions
fold | | ren | 0 | 2 | preserve | none append | | en | 0 | 0 | preserve | none
surnameBranches
mae | Mae and Ro family | steps | fold | seli | Seli family | fen | fold | ivo | Ivo family | reach | append |
surnameCollisionPolicy
warn

Favorites and history are stored only in this browser. Clearing browser data can remove them. Export a backup.

What this workbench actually controls

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.

Dedicated inputs

Fictional places and approved stems
1–16 rows: place ID | place label | approved stem. Supply a stem deliberately; it is never guessed from the label.
Authored constructions
1–8 rows: rule ID | prefix (may be blank) | suffix (may be blank) | drop-start count | drop-end count | preserve/lower/upper | none/hyphen/space. Explicit counts 0–12, measured in Unicode graphemes.
Family branches and exceptions
1–24 rows: branch ID | branch label | place ID | rule ID | fixed surname (blank to derive). A shared place or surname does not create a family relationship.
Matching surname policy
Warn preserves distinct branches. Reject asks you to revise a construction or author an explicit exception.

Naming constraints

  • Keep place labels independent from explicitly approved stems. Never infer a real etymology, residence, birthplace, ownership or kinship.
  • Normalize the stem to NFC, clip complete graphemes, retain a letter, apply the selected mechanical case, and join nonempty affixes with the authored separator.
  • Preserve a declared surname exception exactly and show its rule preview as a comparison, not its claimed formation.
  • Compare NFC/case/whitespace spelling for branch collision cues; accents remain significant. Matching names do not merge branch identities.
  • Changing any source invalidates the previous local scene; full snapshots keep their original plan.

Result dimensions

branch surname and stable branch ID · source place ID and label · approved and NFC-normalized stem · removed start, retained stem and removed end · cased stem, prefix, suffix and joiner · rule preview and explicit exception status · grapheme count and matching-spelling branches · complete versioned source plan

Compare workbench capabilities →
A FEW CONSIDERED BEGINNINGS

Lantren

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.

Mae Lantren had brought a measuring tape to the town where her mother grew up. Ro had brought an apple, a folding hat and no apparent interest in measuring anything.From A Window Facing Somewhere Else · original fiction
AN ORIGINAL MIDSUMMER FRUIT STORY

A Window Facing Somewhere Else

Mae brings a measuring tape and a family surname to a room near her mother’s old home. A wall, another Lantren and a borrowed workshop window undo the view she thought she had inherited.

Characters & relationships in this story

Mae Lantren · A traveller considering a room she has connected to a family memory · Address: Mae

Ro Lantren · Mae’s mother, whose remembered drawing window was a borrowed workshop seat · Address: Ro

Seli Lantren · A room owner from a separately declared fen branch, no kinship established · Address: Seli

Ivo Bracken · A workshop maker who keeps an explicit surname exception · Address: Ivo

Mae Lantren ↔ Ro Lantren: Daughter and mother; a shared surname does not prescribe the daughter’s home

Mae Lantren ↔ Seli Lantren: Prospective occupant and owner; matching surname without established kinship

Ro Lantren ↔ Ivo Bracken: Old friends connected by a borrowed place to draw

Mae Lantren ↔ Ivo Bracken: New acquaintance distinguishing a hypothetical construction from a kept surname

Editorial demonstration · human review pending. Characters and events are fictional. Creative name explanations are not etymologies.

The room with the family name

Mae Lantren had brought a measuring tape to the town where her mother grew up. Ro had brought an apple, a folding hat and no apparent interest in measuring anything.

“The room may already have a table,” Mae said as their bus climbed past the harbour.

“Then you've brought a tape to meet a table. A sensible first introduction.”

Mae unfolded the letting notice. A small upstairs room was available near the old Lanter Steps, where Ro's family had once lived. She could afford it if she gave up the larger room she shared inland and kept her travelling work. The owner wanted an answer before evening. Nothing required Mae to decide that day; she had made the deadline feel final by arriving with a suitcase.

She wanted the room because of its window. She had not seen the window yet. Her mother had spoken of standing at a window as a girl, with gulls moving beyond it and enough light to draw by until supper. Mae had placed that description inside the room on the notice without checking whether the two windows belonged to the same house.

Ro watched the harbour disappear behind a row of roofs.

“Are we going to look at a room,” she asked, “or at your idea of my childhood?”

“Both, if they're conveniently next to each other.”

Ro offered half the apple. Mae took it. On the back of the notice she had written LAN TREN in two careful blocks, as though a family name could supply a second address when the printed directions grew uncertain.

A short way through Lanter

At the steps, Mae stopped beside a board which now called the area Bay Gardens. Beneath the newer lettering, a narrow wooden strip still read Lanter Steps. The stone stairway continued behind it, too steep for the suitcase to enjoy.

“That's us,” Mae said, pointing to the old strip.

“That's a place,” Ro replied. “We were some of the people who lived near it.”

Her grandfather had kept Lanter as the approved stem in the family's own naming notes. He shortened its end to Lant and added ren, making Lantren. It was their invented construction. He had not supplied a rule for everybody else who lived on the hill, nor a claim that every Lantren came from these particular steps.

Mae knew the pieces. She had copied them as a child, enjoying the way a place could be folded into something small enough to write on a schoolbook. She had forgotten how much of the folding was a choice.

“Would we be Bayren now?” she asked.

“Only if you let that board fill in our forms.”

Ro put on the hat. Its front folded down over one eye. Mae reached to straighten it and was told, with dignity, that the sun was coming from that side.

They carried the suitcase up together, one holding the handle and the other lifting the wheels over each shallow edge. The name had not made the stairs less steep. Halfway up, Ro stopped to look at the harbour through a gap between two houses.

“That's a good window,” she said.

“It isn't a window.”

“No rent, either.”

Another Lantren at the door

Seli Lantren opened the upstairs room. Mae had assumed the owner was a distant relative, an assumption she had not mentioned because she hoped the discovery might happen pleasantly over tea.

“My people used Lanter Fen,” Seli said when Mae asked about the name. “Different place, beyond the inland ferry. Same stem in our notes, same little ending. We haven't established anything more interesting than that.”

Ro nodded. Mae put away the question she had prepared about cousins.

Seli's room was clean, with a narrow bed, a table and the promised window. The window faced a wall. Above the wall there was a slice of sky, wide enough for a gull to cross if it chose its route obligingly.

Mae set the suitcase beside the bed. She had imagined putting her worktable under the window and calling her mother from it on bright mornings. The table was already there. It fitted perfectly into an arrangement she no longer wanted to picture.

She took out the tape anyway. Between the table and the bed there was room for her knees, but not for the low box in which she kept her paper. She measured again with the box imagined under the table instead. Seli waited while she moved the chair.

“You can try it the way you'd use it,” she said.

Mae put her sketchbook down and sat. For a minute she looked at the page instead of the window. Her shadow covered the place where she would draw. She turned the book, moved the chair and found a workable angle. It was useful to know that she could work here. It was a different question from whether she wanted to.

“The wall belongs to the next house,” Seli said. “I can't offer to move it.”

“I wasn't going to ask.”

“People do. In an indirect way.”

Mae smiled because Seli was watching her kindly and because it was easier than explaining how specifically she had wanted a view that nobody had advertised.

Ro tested the chair. It did not wobble. She opened the window and listened. Somewhere below, a man was counting while someone else tried to play a stubborn musical phrase.

“That's new,” she said.

“Every afternoon,” Seli replied. “They improve some days.”

Mae looked at the wall again. She could already hear herself describing it as a temporary compromise, although she had come looking for a place she would not need to explain away.

The window Ro remembered

Ro's old room was farther along, above a shop which now sold lamp shades. Its present occupant had put a fern in the window. Mae stood across the street and tried to fit the remembered gulls around the plant.

“The buildings have changed,” she said.

“Of course. But that wasn't the window I meant.”

Ro took a folded drawing from her bag. Mae recognized the paper. It had been inside an old sketchbook for years, without anyone treating it as a document which needed a protective sleeve. The drawn view showed a rail, a wooden post and water beyond them. In one corner a hand had begun a gull and changed it into something resembling a spoon.

“The room I lived in faced the back yard,” Ro said. “The good window was in Ivo's workshop by the water. He let me use the end of his bench after school.”

“You always said your window.”

“It was mine for an hour. I had to move whenever he needed the vice.”

Mae looked from the drawing to the fern. She had mistaken permission to sit somewhere for possession of the room around it. Ro had never said the light belonged to the family house.

She wanted to knock at the shop and ask whether she could see upstairs, if only to replace one imagined room with an actual one. The occupant had not offered a visit. She kept her hand on the suitcase instead.

Ro tucked the drawing away.

“Is Ivo still there?” Mae asked.

“Shall we find out?”

For the first time that morning, the question concerned something neither of them had already arranged an answer to.

Bracken by the water

Ivo Bracken's workshop door was open to the harbour. He was fitting a handle to a drawer when Ro called his name. He put the handle down before looking up, as though recognition deserved both hands free.

“I still have your spoon-bird,” Ro said.

“An experimental species.”

He found three chairs which had apparently arrived from three different kitchens. Mae's chair was lower than the others. She took it without attempting to turn the difference into a sign about being the youngest.

On a shelf lay one of Ivo's small place cards, written for a local map display: Cedar Reach, approved stem Cedar, possible construction Cedaren. Bracken was written beneath it in a different ink.

“Were you Cedaren before?” Mae asked.

“No. Bracken is the name we kept. The construction on that card was a possibility for the display, not my childhood.”

He turned the card over. There was a list of drawer handles on the back. Mae liked him immediately for declining to make the object more solemn than it was.

Ro took the old seat beside the window. A storage rack occupied half the view now, and a yellow buoy interrupted the line of the water. She moved the chair a little to the left.

“Still works,” she said.

Ivo asked what she was drawing these days. Mae waited for her mother to bring out the old sketch. Instead Ro described the awkward angle of a bicycle outside her present kitchen and the neighbour who kept parking it beneath a different tree.

They began arguing about whether the bicycle needed the tree. Neither remembered to make their conversation into an account of how much the town had changed.

The walk without a destination surname

Mae went outside while they talked. From the end of the quay she could see the hill and the backs of the houses near the steps. She tried the room again in her mind: table, bed, sky above the wall, the unfinished musical phrase from below.

It was a possible room. It had not become a bad room because her borrowed view would not fit inside it. Someone might like the small sky and the way the table stood out of the draught. Seli had offered precisely what was there.

Mae had wanted her name to make the choice easier. If the room belonged to a story she already knew, perhaps she would not have to decide whether she wanted to live in it now.

A gull landed on the quay rail and looked at her suitcase. She moved the apple peel away from its reach. The gull remained unimpressed by the care with which she was arranging her future.

Ro came out carrying the drawing. Ivo had lent her a pencil with a large rubber on its end, apparently on the condition that she improve the spoon-bird before returning it.

“Would you be disappointed if I didn't take the room?” Mae asked.

Ro looked up at the hill. “Would you?”

“I don't think so. I might be disappointed not to have wanted it.”

“That happens.”

They walked without consulting the letting notice. At the harbour corner Ro pointed to a bench which faced the water, and Mae sat down before calculating whether they had time for it. Her mother's hat had acquired a soft dent where it had leaned against the workshop wall.

Mae took out the tape and measured the bench between them.

“Enough room?” Ro asked.

“For this table's entire introduction.”

Ro laughed and put the pencil on the empty space.

A room can be looked at twice

Mae called Seli before the evening bus. She thanked her for showing the room and said she would not take it. She did not blame the wall, the notice or a family history that had failed to provide the expected view.

Seli said she appreciated the definite answer. Someone else wanted to come the next morning. There was no wounded speech about wasting a journey and no miraculous second room with a perfect harbour window.

Ro was drawing while Mae made the call. She had left the old bird on its old page and begun a new one on the back of the letting notice. Mae watched the pencil stop before the wing. Her mother looked at the actual gull, which had chosen that moment to fold both wings and become difficult.

“You could use the old one,” Mae said.

“I could. I want to see this one.”

On the bus home, Mae kept the notice flat between the sketchbook covers. The room's address remained on one side, the new drawing on the other. Neither had to become the explanation for the whole journey.

They reached the turn where the harbour disappeared behind the roofs. Ro was looking inland this time. She had remembered something about the bicycle and wanted Mae to come for supper the next day, when the light beneath the kitchen tree was better.

Mae checked her work before saying yes. Then she put the measuring tape back in the suitcase. Lantren was on the luggage tag, just where it had been when they arrived. It could travel with her without pretending that every place in its story was somewhere she ought to stay.

The naming notebook

A source connection is smaller than a destination

Mae knows how Lanter becomes Lantren in her family’s invented construction. That accurate connection does not tell her which window Ro remembered or whether the advertised room will suit her. The story lets the name support a specific question while exposing the larger answer Mae has supplied herself. Keep the source place under a stable ID and approve its stem separately from its display label. Bay Gardens can appear on a new sign without silently rewriting the family’s choice. None of this is evidence about a real surname, a historical settlement or who has a right to enter the upstairs room.

Let a matching surname remain an unresolved family connection

Seli’s Lantren comes from a separately declared Lanter Fen branch. The common stem and ending produce the same spelling, but the story does not invent cousins to reward Mae’s expectation. A matching-name warning is useful precisely because the underlying records stay distinct. Compare the place IDs and branch labels before deciding whether the similarity is intentional. Reject mode asks for a revised construction or an explicit exception; warn mode permits the deliberate echo. Neither policy settles genealogy or proves whether readers will confuse the characters. Give the people different actions and spoken addresses as well as separate author records.

An exception must not acquire a false history

Ivo keeps Bracken while Cedaren remains a construction preview. The map card is a possible naming exercise, not proof that he changed his name. This distinction belongs in both the result and the private fragment: an exception can be compared with a rule without being explained by it. The borrowed workshop window also limits what Mae can inherit from the story she has heard. Ro can value the old seat and still draw a new bird elsewhere. The final journey carries a surname forward without turning it into a requirement to stay, purchase, return or reproduce somebody else’s view.

Write place IDs, labels and approved stems separately. In the story, a newer Bay Gardens sign does not rewrite the approved Lanter stem or the family surname.

Inspect Lanter → Lant → Lantren as an authored construction. The surname does not tell Mae which window her mother used or where she must live.

Keep Seli’s fen branch separate from Mae and Ro’s steps branch, despite matching spelling. The model records a source connection, not a genealogy.

Mark Bracken as Ivo’s explicit exception. Cedaren remains a possible construction preview; it must not be presented as his former name.

Use full private plan exports for source records and the per-branch formation text for an explanation you choose to copy. Review fictional facts before adapting them to a researched cultural setting.

Lantren: 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. Inspect the two matching Lantren branches, then the Bracken exception. Change only a place label and rebuild to see its approved stem remain unchanged. Use reject to require resolving the intentional collision.

BEFORE YOU CHOOSE

Questions from the workbench

Will changing Lanter Steps to Bay Gardens change Lantren?

No. The display label and approved stem are separate fields under a stable place ID. Change the stem or construction explicitly if you want a different surname, then rebuild.

Why are Mae’s and Seli’s matching names not merged?

Their separate branches reference different fictional places. Matching normalized spelling is a review cue, not evidence that people are related. Warn retains both; reject asks you to choose a deliberate alternative.

Is Bracken explained by the Cedar construction?

No. Bracken is an authored exception. Cedaren is the rule preview for the approved Cedar stem, not an asserted former surname or etymology.

Does the tool know where the family actually lived?

Only the place reference the author supplies is recorded. It does not infer birthplace, residence, historical ownership or access to a room from a name.

Why can clipping not remove the whole stem?

A derived surname must retain at least one letter from the approved stem. If the family keeps a separate name, use an explicit exception while keeping a valid comparison construction.

Does uppercase provide a culturally correct surname form?

No. Preserve/lower/upper performs Unicode-default casing only. Supply and verify language-specific morphology separately; the workbench makes no such cultural claim.

Practical naming reading

Scope & sources

Original fictional planning only. Unicode casing and grapheme operations are mechanical, not language-specific morphology or pronunciation. No cultural authenticity, global uniqueness, property claim or commercial clearance is established. Human literary review pending.

Midsummer Fruit original creative dataset · CC0-1.0
Original word selections, fictional combinations, explanatory content and narrative; not researched etymology. Internal spelling and structural review only; cultural authenticity not established.

↑ Back to naming tool