The fictional brief
A small science-fiction setting follows maintenance crews between three orbital stops. The vessels need personal identities, the stations need navigational clarity, and the route needs an umbrella name. Giving everything a star-related title produces a beautiful but indistinct manifest. The working solution separates naming structure by function.
Stations use place and task
Draft labels are Lantern Hub, Spindle Platform, and Orchard Anchor. Each combines an image with a functional noun. The nouns remain visible on the route display, so a player can recognize a station even when the map is zoomed out. The names are invented labels, not claims about actual space infrastructure or scientific terminology.
Ships use portable, ordinary images
The three working vessel names become Paper Heron, Quiet Parcel, and Copper Loop. They are spoken as names rather than as complete technical descriptions. Registration codes sit in separate fields. A route announcement can say “Paper Heron departing for Spindle Platform” without forcing the player to decode a string of similar identifiers.
Choose a collective that does not compete
The network is called the Neighbor Route. It describes the relationship the crews try to maintain rather than adding another object to remember. “Neighbor Route manifest: Paper Heron, Orchard Anchor” gives three distinct levels of information. The collective title should not look like a fourth ship or an additional destination.
Write one ordinary inconvenience
A delayed plant delivery keeps Orchard Anchor’s public garden closed during a station holiday. Quiet Parcel carries the replacement parts, while Paper Heron returns an empty crate. The names stay clear because the actions and entity types reinforce them. A routine schedule can reveal the setting’s values without a dramatic crisis.
Review before expansion
Add a fourth imaginary station and another vessel using the same rules. If every new label requires an exception, the system is too narrow. If any random noun pair feels equally plausible, add a stronger material or institutional constraint. This exercise shows a design method; it does not claim that these particular names have passed audience testing or rights clearance.
A manifest can introduce the whole naming hierarchy
Place the collective service, vessel, destination, and berth in separate fields: Neighbor Route; Paper Heron; Spindle Platform; a short berth reference. Read the same information as an announcement without the visual columns. If the sentence blurs a ship into a station, revise the names or the wording. The audience should not have to memorize a technical code before understanding who is leaving and where they are going. Registration identifiers can remain available in records, but they do not need to replace every ordinary name. This small list tests the structure before the setting expands to many more stops.
Give stations different everyday purposes
Lantern Hub handles transfers, Spindle Platform maintains shared equipment, and Orchard Anchor hosts a garden and gathering room. These fictional roles justify the functional second words. The first images give the audience something to remember, but they do not need to explain every technical detail. A public directory and a crew member’s informal directions should connect the full station name with a recognizable local landmark. When another station is added, choose a role that fits the network rather than repeating the same orbital adjective simply to make the catalog appear uniform.
Let vessel names belong to crews
Paper Heron, Quiet Parcel, and Copper Loop are working candidates chosen as ordinary portable images, not official astronomical classifications. A crew can tell a short story about a folded bird or repeated delivery to explain the name. Another crew member can dislike it without creating a different vessel. Keep the registry form, radio form, and any private nickname linked in the project notes. If a name changes after a major event, show the connection clearly before the next route scene depends on recognizing it. A chosen identity can evolve while the audience still follows the same craft.
The delayed plant delivery supplies a real decision
The replacement parts for Orchard Anchor’s garden compete with a routine cargo slot. A dispatcher can delay the public holiday, reroute Quiet Parcel, or ask another station to lend a component. The names remain useful because each entity has a distinct role and the announcement repeats the hierarchy. The story’s interest comes from the choice, not from spectacular danger. A player learns why the garden matters when residents adjust their plans, giving the station’s image a social association supported by action rather than a generic paragraph explaining that orchards always mean hope.
An old label can complicate a route fairly
A maintenance crate uses the station’s earlier construction title. The current manifest does not, so an inexperienced clerk initially sends it to the wrong field. A dated record connects the former label to Spindle Platform. This establishes a rule for obsolete names before a later mystery uses another forgotten route. Keep the old wording distinct from the vessel names on the same screen, and add a brief line explaining the connection. The audience can enjoy a layered fictional history without being punished for an author’s inconsistent naming or asked to infer that every unexplained code is a new destination.
The final system is a method, not a validated standard
The study proposes functional station nouns, portable vessel images, and a collective title based on a shared service. It has not established a universal science-fiction convention or passed a real radio usability study. A production team would test noisy announcements, actual map views, localized strings, and neighboring names. The useful handoff includes the naming rules, exceptions, role labels, and one plain manifest sentence. It also records why a fourth ship should not accidentally resemble a new station. The resulting vocabulary supports expansion because a collaborator can explain each level’s job without copying the exact original candidates.
Make the next draft your own.
Try the method in a tool, keep a candidate in your notebook, and revise it against your actual project.
A correction or a question about this piece? Contact Drafitlem.