siren 𝜗𝜚

಄ ⋆ BACKGROUND

to bring to light why i wrote this, while reading an otherwise enjoyable fanfiction, i encountered a line in which Heian-era sukuna was addressed by "ryomen" as though it were his given name, and this had been a repeated trend i've seen in Jujutsu Kaisen sukuna fanfiction. this tiny detail—which objectively should not have occupied my thoughts for as long as it did—sent me down an unfortunate rabbit hole regarding naming conventions in Japanese media, translation practices, and the tendency for English-speaking fandom to reconstruct unfamiliar linguistic systems into something more recognizable. names are rarely "just names," even within simplistic language systems. across different cultures, they carry distinct systems, conventions, and social functions that determine not only what a person is called, but why they are called that in the first place. English-speaking fan communities frequently interpret foreign naming systems through familiar Western frameworks.

಄ ⋆ SIGNIFICANCE

i believe it is well known that fanfiction often rewards emotional accuracy over linguistic accuracy (not saying disparagingly). however, repeated reinterpretations of foreign naming systems can gradually become accepted as "common knowledge" within fandom. examining why this occurs reveals less about individual writers and more about how language shapes the way audiences understand unfamiliar cultures.

಄ ⋆ CHAPTER 1. WHAT DOES A NAME DO?

to start, i must quote unnecessarily, "i think therefore i am." this does not mean anything, i just really wanted to use it because it's funny. before discussing why fandom repeatedly misinterprets foreign names, we first have to answer a surprisingly difficult question. what exactly is a name? a name, linguistically, is a term used for identification by an external observer and it can identify a class, a category of things, a single thing (people, places, objects) either uniquely, or within a given context. the entity identified by a name is called its referent. a naming convention is a set of agreed, stipulated, or generally accepted standards, norms, social norms, or criteria for naming things. it is important to note that names have rules. at first glance, a name looks like a label. a chair is a "chair," a table is called a "table," it's a very simple concept. but people are not objects, human names do not just classify, they distinguish. when i say "dog," i've identified a category; when i say "hachiko," i've identified one specific individual. so therefore, names are referential rather than descriptive. their primary purpose is to let which person is being talked about, not what kind of person they are. that's why names can be completely arbitrary, because it's simply a pointer. names also don't just identify people. they also encode relationships, telling you by who calls you what something about your relationship hence, the difference of someone calling you Jonathan, John, Johnny, Dad, Mr. Sherlock, Big John. They are all referring to the same person but every choice communicates something different; familiarity, hierarchy, affection, respect, distance, and intimacy. and i'm sure a bunch of other things. English-speakers often unconsciously assume that [First Name, denoting who they are] [Middle Name, denoting a specifier] [Last Name, denoting from where they came] is the default and universal human format. it isn't obviously, different cultures answer completely different questions. some emphasize family, ancestry, then some emphasize birthplace or achievements. some religion, some ranks. that's why some cultures have patronymics, some don't have surnames, some have courtesy names, some names change throughout their life.

಄ ⋆ CHAPTER 2. NAMES HAVE JOBS, NOT ALL JOBS ARE NAMES

there are several different categories in which names fall in (sources i'm using are very broad, but i'll link them below), that are often unused, unheard, or underutilized in the English language. having established that names are social tools rather than arbitrary labels, we now encounter another problem: English frequently treats every identifier attached to a person as though it were simply "their name." linguistically, however, many of these identifiers perform entirely different functions. They may indicate family lineage, social status, profession, achievement, respect, or reputation rather than personal identity itself. the most important question isn't "what is this called?" when talking about names, but instead "what job is this word doing?" so consider the sentence, "Professor Smith spoke to John." both "Professor" and "John" identify the same individual in different contexts, but they do not perform the same linguistic function.one indicates institutional status, while the other functions as a personal identifier. so? words attached to people aren't interchangeable.

⋆ personal identifiers a given name is a name that identifies the individual within their family or community, it's typically a name assigned to an individual at birth or later in life. in English, this is often the first name. it primarily serves toto distinguish them from other members of the same family. examples are John, Satoru (悟), Yor, Leon. a family name (surname) is a name that identifies a person's family lineage and is shared among relatives. depending on the culture, it may appear before or after the given name (while stylistic choices are of course welcomed, standard practices adopt the original culture's naming order). examples are Gojo (五条), Smith, Liu (劉). a middle name is an additional personal name placed between the given and family name. its purpose varies widely between cultures and may commemorate relatives, saints, or simply provide another identifier. examples include John Fitzgerald Kennedy, Leon Scott Kennedy. a patronymic is a name derived from one's father (or sometimes a male ancestor). it indicates parentage rather than functioning as a hereditary surname. the female version, a matronymic, is derived from one's mother rather than father. it is less common globally but exists in several naming traditions. examples: Ivan Ivanonich ("son of Ivan"). a clan name identifies membership in a larger kinship group rather than an immediate family. multiple unrelated households may share the same clan. examples are Gojo (術師家) and the Uchiha (うちは一族).

⋆ social identifiers a title is a name that denotes rank, occupation, office, or status rather than identity. titles answer the question of "what are you?" rather than "who are you?" examples include: King, Doctor, Professor, Lord, Captain. an honorific is a word or title or grammatical form that conveys respect, familiarity, or social hierarchy between speakers. unlike titles, honorifics describe the relationship between people rather than the identity of the individual. examples include: in Japanese, -san (used to convey respect used between any age), -sama (used for individuals with a higher rank than oneself, -kun (used to refer to people of junior status or men in general), in English, Mr., Mrs., Sir, in Indonesian kak, mas, mbak. a house name denotes the membership in a noble or dynastic house. example: House Stark, House Windsor. a courtesy name is an additional name adopted upon reaching adulthood or entering society. It is often used by peers instead of the person's birth name. this is historically common in Chinese naming traditions. example is Confucius' (Kongzi) courtesy name Zhongni (仲尼). a temple name is a name bestowed after death upon monarchs in several East Asian traditions and is primarily used in historical or religious contexts. a posthumous name is a name granted after death and often reflects the person's achievements or character. unlike a birth name, it was never used by the individual during life. a regnal name is a name adopted when someone ascends to a throne or other high office. example: Pope Francis, Queen Elizabeth II. a religious name/dharma name is a name adopted upon entering a religious order or undergoing initiation. Ii often symbolizes spiritual rebirth or new identity.

⋆ descriptive identifiers an epithet is a descriptive word or phrase attached to a person's name that highlights a characteristic, reputation, or distinguishing feature. unlike a given name, an epithet describes rather than identifies. examples: Alexander the Great, Ivan the Terrible, Richard the Lionheart, Ryōmen ("two-faced") Sukuna. a sobriquet is an informal descriptive nickname earned through reputation, personality, or achievement. unlike a legal name, it develops through public use. a byname is an additional identifier attached to distinguish someone from others with the same personal name. it often describes appearance, occupation, birthplace, or family. many historical epithets function as bynames.

⋆ chosen identifiers a nickname is an informal alternative used by friends, family, or acquaintances. nicknames often shorten, modify, or replace a person's given name. examples: Jonathan → Jon, Katherine → Kate. meanwhile an alias is an assumed name used instead of one's legal identity, often for privacy, disguise, or professional reasons. an art name is a name adopted by artists, scholars, or writers as part of their creative identity. this is a also called a pseudonym or moniker. examples are Su Shi also known as Dongpo Jushi, Takashi Murakami, KAWS. a pen name (nom de plume) is a pseudonym adopted by an author for publication. a stage name is a professional identity used by performers instead of their legal name. a username identifies an individual within a digital environment. unlike legal names, usernames are chosen, platform-specific, and need not correspond to real-world identity.

notice that every category above identifies a person in some capacity, yet none performs exactly the same job. English often collapses these distinctions under the broad concept of a "name," whereas many other naming systems preserve functional differences between personal names, titles, honorifics, and descriptive epithets. while all of these may appear beside a person's identity, they are not interchangeable. some identify the individual, some identify their family, some describe their reputation, and others communicate social relationships. referring to all of them simply as "names" obscures the distinct roles they perform within their respective cultures. if these distinctions are so common across cultures, why do English-speaking readers so frequently flatten them into a single naming system?

಄ ⋆ CHAPTER 3. WHY ENGLISH SPEAKERS MISREAD FOREIGN NAMES

having established that names perform different social functions across cultures, we arrive at another question: if these distinctions exist, why are they so frequently overlooked in English-speaking fandom? the answer is surprisingly mundane. it is not usually a failure of research (though it's the second most common reason), nor a lack of intelligence. rather, it is a consequence of how humans process unfamiliar information. the first reason is that our brains simply do this because of pattern recognition or schema activation, something i spend much time on in thinking. we as humans are extraordinarily good at categorization. we don't read every unfamiliar thing from scratch—we compare it to something we already know. linguists call these mental shortcuts schemas but for this, i simply call it 'already knowing enough' (larping). when English speakers encounter "Ryomen Sukuna," our brains don't consciously ask what naming convention is being used. they see two capitalized words and immediately retrieve the closest familiar template. a lot of what contributes to the reason of why people mistake foreign names so badly, especially names with their own alphabet, and especially with vastly different scripts, is due to once transliterated into the Latin alphabet, these names become visually familiar to English-speaking audiences. they appear to follow the same structure as English names—two capitalized words separated by a space—despite often operating according to entirely different cultural conventions. this visual familiarity encourages readers to unconsciously apply English naming expectations where they may not belong. humans also do chunking. you don't read Tanjiro as T-a-n-j-i-r-o, but Tan-Ji-Ro. you don't read my username as kayuekou but it gets mentally segmented as kay-ue-kou. or if you come from a more East Asian linguistic background, ka-yue-kou. and this isn't ...nearly all your fault. after being immersed in English naming conventions, ie. Jane Doe, Peter Parker John B. Smith, our brains automatically shove Ryomen Sukuna, Kuroki Tomoko, Kamado Tanjiro into the same system. Ryomen Sukuna is chunked into Ryomen (first name) - Sukuna (last name).

಄ ⋆ CHAPTER 4. EVERYTHING GETS ENGLISH'D

so now, having established why English-speaking readers naturally reinterpret unfamiliar naming systems, it becomes apparent that this phenomenon extends far beyond Japanese media, my original grievance. whenever a naming system differs significantly from English conventions, readers often simplify, reorganize, or reinterpret it into something more immediately recognizable. in practice, what does this look like?

first, mistaking family names as first names because of the Eastern name order (family name first, given name second), obviously this is most commonly seen in East Asian names. my examples will primarily derive from Japanese, mostly due to its almost uniquely similar structure to English when transliterated. this is often seen in Japanese fan media, which i found most prominent in fanfiction made pre-2021, such as mistaking Gojo for Satoru's given name. specifically in Japanese, starting from the Meiji Restoration in 1868, the Western name order was primarily used among the Japanese nobility when identifying themselves to non-Asians with their romanized names. as a result, in popular Western publications, the order became increasingly used for Japanese names the following decades (Shinzo Abe, Osamu Dazai, Satoru Gojo). however! in 2020, the Government of Japan reverted the Westernized name order back to the Eastern name order in official documents, and has recommended that the same format be used amongst general Japanese public; they also requested Western publications to change this. this is a big reason why Japanese becomes quite confusing when you dip your foot in and understand what the Eastern naming order looks like, because sometimes you don't know if they're using the Western or Eastern order. unlike the Chinese and the Koreans who have never used Western name order (Chinese leader Xi Jinping not being referred to as Jinping Xi, Moon Jae-in is not Jae-in Moon).

second, names getting split strangely. i recently saw in a fanfiction (that i've put on hold simply because of this) that the author named the fanon interpretation of the Gojo twins as Sato and Toru. this is most likely because they assume those are natural halves of "Satoru." Except Japanese morphology doesn't work that way. likewise, my name has been mistakenly used quite a lot, my nickname from my moniker kayuekou sometimes become kay because "Kay" already exists in English. but this is especially frustrating once you understand that the kanji system, derived from hanzi, uses a logographical system. meaning, the Japanese writing for a name, almost always has a set meaning. "五条悟" or Gojo Satoru is split into "Gojo" or "五条" meaning 五 five, 条 an article or clauses, and 悟 meaningly enlightenment or to understand. the second you strip away Satoru and become Sato, that has become a completely. new name. in some dictionaries, maybe Sato as 悟 could happen, and i've checked myself on jisho that there is a given name called Sato with that exact kanji, but now it's a matter of logic and accuracy. Sato is almost alway used as a surname; Sato as 葛巻, Sato as 郡, Sato as 慧. there are rules to what a kanji can or cannot do in a name, but i will not deep dive into that in this essay.

third, in Russian, and a classic example, Ivan Ivanovich Petrov is often frequently read by English-speakers as Ivan, Middle name Ivanoich, Last name Petrov when the "middle name" is actually just telling you whose son he is. fourth, a fascinating one because it almost flips the problem, are Thai names. Thai people commonly have long legal names (due to surnames needing to be legally unique, therefore combining many words and subsequently creating incredibly long surnames) and short nicknames, sometimes ones that don't have any relation to their legal name. many foreigners sometimes assume the nickname isn't their "real" name, when culturally, it's often the primary everyday identifier.

although each example arises from a different language, the underlying mechanism remains remarkably consistent. readers encounter an unfamiliar naming system, identify superficial similarities to English, and unconsciously reorganize it according to English expectations. the details differ; the cognitive process does not. a worthwhile minor topic to touch is things that English speaking writers accidentally normalize. such as the tendency of first-name basis immediately, honorific inconsistencies, modern Western flirting in Eastern historical settings, school culture assumptions, legal names vs epithets. i would touch the topic but i'm no fiddler.

಄ ⋆ CHAPTER 5. NOT EVERYTHING IS A GIVEN (NAME)

by this point, we have established three things. firstly, names are not merely arbitrary labels, but social tools that identify individuals within a cultural system. secondly, not every identifier attached to a person performs the same function. lastly, English-speaking readers naturally interpret unfamiliar naming systems through frameworks they already recognize. we now arrive at one of the most common consequences of this process: assuming that every identifier attached to a person is a given name. not every word attached to a person is attempting to answer the same question. like we discussed in the previous chapters, a given name answers, "who are you?" a family name answers, "which family do you belong to?" a patronymic answers, "whose child are you?" a title answers, "what is your rank, occupation, or position?" an honorific answers, "how should I address you?" an epithet answers, "what are you known for?" these may all appear beside one another when referring to a single person, yet they are not interchangeable. they perform different linguistic and social functions despite identifying the same referent. epithets are probably the clearest example of this distinction. an epithet is not another personal name, but a descriptive identifier attached to an individual because of a notable characteristic, achievement, reputation, or physical trait. history is full of them. Alexander the Great, Richard the Lionheart, Ivan the Terrible, Erik the Red, and William the Conqueror are all remembered through epithets. English speakers immediately recognize that "the Great" is not Alexander's surname, nor is "Lionheart" Richard's given name. these descriptors tell us something about the individual rather than functioning as the individual's personal identity. the interesting part is that this intuition often disappears when the epithet originates from another language. once romanized into the Latin alphabet, foreign epithets lose many of the visual and cultural cues that distinguish them from ordinary names. rather than seeing a descriptive title, English-speaking readers often see another capitalized word occupying the same position as a conventional first name. without consciously realizing it, the epithet is reassigned a new job. it is no longer interpreted as a description, but as a personal identifier. this distinction matters because misunderstanding an identifier is not simply a matter of pronunciation or terminology. it changes the role that identifier plays within the naming system itself. an epithet interpreted as a given name no longer functions as a description; it becomes an identity. a title mistaken for a surname no longer indicates social position; it becomes ancestry. in other words, the word has not changed—but the job we assign to it has. so anyway. this brings us to another important question. if these distinctions are meaningful, why do official translations, subtitles, and fan translations so rarely communicate them? more importantly, are translators responsible for preserving these naming systems, or are readers simply encountering the unavoidable limitations of translation itself?

಄ ⋆ CHAPTER 6. TRANSLATION FUELS THESE MISTAKES

so now that we've established that identifiers perform different linguistic functions and that English-speaking readers naturally interpret unfamiliar naming systems through familiar frameworks, another question inevitably follows: if these distinctions are important, why do translations so rarely preserve them? the answer is not that translators are careless. rather, translation itself is an exercise in compromise. contrary to popular belief, translation is not simply the process of replacing one word with another. every translator must constantly decide what should be preserved. should priority be given to literal meaning, readability, cultural context, historical accuracy, emotional impact, or natural dialogue? more often than not, preserving one inevitably sacrifices another. names are particularly difficult because they rarely carry meaning in isolation. instead, they exist within larger cultural systems that are often invisible to those who already understand them. a Japanese reader generally does not require a footnote explaining the function of an honorific, the order of family and given names, or whether an identifier is an epithet rather than a personal name. these conventions are already understood. an English-speaking audience, however, approaches the same text without that shared cultural framework. romanization further complicates this process. when Japanese is written in its native scripts, it is immediately recognizable as a different writing system. readers instinctively understand that they are encountering another language. once those same names are transliterated into the Latin alphabet, however, they become visually familiar. two capitalized words separated by a space resemble countless English names, despite following entirely different cultural conventions. the alphabet remains familiar even when the language does not. this creates what i consider one of romanization's greatest paradoxes: it increases accessibility while simultaneously creating an illusion of familiarity. readers correctly recognize the letters, but unconsciously assume they also recognize the system behind them. translation, therefore, often preserves the words while inevitably losing parts of the framework that gives those words meaning. again, this is not unique to Japanese. consider honorifics such as -san, -kun, or -sama. many English translations omit them entirely because there is rarely a natural English equivalent that carries identical social nuance. likewise, patronymics in Russian are frequently interpreted as middle names, while Chinese family names are often mistaken for given names simply because the translated text cannot pause to explain an entirely different naming convention every time a character is introduced. doing so would be impractical. imagine a subtitle interrupting every conversation with a linguistic lecture explaining why a particular identifier is functioning as an epithet rather than a personal name. accurate? perhaps. readable? absolutely not. translation, after all, is intended to communicate a story—not to teach an entire course in comparative linguistics. this is where fandom enters the equation. readers naturally fill in the missing pieces using the only framework they possess: their own. one fanfiction assigns an English role to an unfamiliar identifier. another writer adopts the same convention. a hundred readers encounter it repeatedly. eventually, what began as an unconscious interpretation slowly transforms into accepted fanon. the reinterpretation is no longer questioned because, through repetition, it begins to feel canonical. translation does not create these misunderstandings on its own. it merely provides the conditions under which they become possible. the actual reinterpretation occurs in the minds of readers, where unfamiliar linguistic systems are quietly reorganized into something that feels comfortably familiar.

಄ ⋆ CHAPTER 7. CASE STUDY

which leads to a minor footnote, and the inciting example on why i made this post. one of my favorite little linguistic quirks in JJK is that "Ryomen Sukuna" isn't really a given name in the way a lot of English-speaking fans read it. the historical figure that inspired Jujutsu Kaisen's Sukuna is traditionally known as Ryōmen Sukuna. the term Ryōmen (両面) literally means "two-faced" or "two-sided," referring to the figure's unusual appearance. rather than functioning as an ordinary personal name, it is widely understood as a descriptive epithet attached to Sukuna. as discussed in chapter 2, epithets perform a fundamentally different function from given names. they describe rather than identify. however, once romanized into the Latin alphabet, "Ryōmen Sukuna" visually resembles a conventional English first name–surname pairing. the epithet is therefore reassigned a familiar role: first name. this interpretation is further reinforced through repetition. once a sufficient number of fanworks address Sukuna as "Ryomen," subsequent writers encounter the convention repeatedly and naturally assume it reflects canon. over time, the reinterpretation becomes self-perpetuating, not because readers consciously reject the original naming system, but because the English framework has already become normalized within the community. modern AUs present a somewhat different situation. since these settings intentionally remove characters from their historical and cultural contexts, writers are free to assign entirely new naming conventions if they wish. someone may choose to reinterpret "Ryomen" as a legal first name simply because it functions conveniently within the world of their story (but still, when you take into account kanji, and you should, it becomes messy). fanfiction is, after all, transformative by nature. admittedly, none of this prevents me from visibly twitching every time Heian-era Uraume solemnly addresses Sukuna as "Ryomen" with the energy of someone calling Alexander the Great "Great." that, however, is a personal problem rather than a linguistic one. not everyone is a nitpicker. ultimately, the question is not whether fanfiction is "allowed" to call Sukuna "Ryomen." fanfiction has never depended upon strict historical or linguistic accuracy. rather, this example demonstrates how easily unfamiliar naming systems become reorganized according to the expectations of another language. what appears to be a single naming choice is, in reality, the product of translation, cognition, and community convention acting together.

಄ ⋆ CHAPTER 8: WHAT CAN YOU DO?

if this essay has accomplished anything, i hope it has not convinced you that your fanfiction is "wrong." rather, i hope it has convinced you that naming conventions are often far more culturally complex than they first appear. the purpose of this essay has never been to argue that every writer should become a historian, a linguist, or a professional translator before opening Google Docs. fanfiction is transformative by design. writers are free to alter names, settings, relationships, and entire worlds if doing so serves the story they wish to tell. the distinction lies in intentionality. there is a meaningful difference between deliberately changing a naming convention because it better suits your story and unconsciously changing it because you assumed it worked like English. the former is a creative decision. the latter is simply a assumption. fortunately, assumptions are surprisingly easy to challenge. when writing characters from another culture—particularly historical settings—it is often worth asking a few simple questions before assigning an unfamiliar identifier a familiar role. is this actually the person's given name? could this instead be a title, epithet, clan name, patronymic, courtesy name, or honorific? am I following a convention because the source material suggests it, or because other fanfiction does? if i removed my English expectations, would i still interpret this name the same way? the answer, of course, may still be "I'm going to write it this way anyway." and that is perfectly acceptable. the goal is not perfect authenticity. absolute historical accuracy has never been the defining characteristic of fanfiction, nor should it be. creative writing thrives on reinterpretation. what matters is understanding what you are reinterpreting. once you recognize that names are cultural systems rather than isolated words, small details begin to reveal themselves everywhere. family names stop looking like first names. patronymics stop looking like middle names. epithets stop looking like legal names. romanized words stop feeling automatically familiar simply because they share the same alphabet. most importantly, you become aware of your own assumptions. language is remarkably good at making itself invisible. we rarely notice the frameworks through which we interpret the world until we encounter one that functions differently. by then, our brains have often already attempted to reorganize the unfamiliar into something comfortably recognizable. that tendency is not a personal failing. it is simply how humans make sense of the world. the challenge—and, perhaps, the fun—is learning to recognize when our own language is quietly filling in gaps that another culture never intended to leave. and if nothing else, perhaps the next time you encounter an unfamiliar name in a piece of media, you'll pause for just a moment before asking the question that inspired this entire essay: "is that actually their name... or have i simply given it an English job?" oh and start using dictionaries.

಄ ⋆ CONCLUSION / TL;DR

this essay began because one (1) line in one (1) fanfiction annoyed me far more than any reasonable person should probably admit. human beings are exceptionally good at recognizing patterns, therefore English speaking consumers and writers interprets foreign naming systems through a framework they're already familiar with. the result is not usually malice, laziness, or ignorance—it is simply the remarkably human tendency to organize unfamiliar things into familiar categories. this essay therefore is not an argument for linguistic perfection, nor is it a declaration that fanfiction must adhere to strict historical authenticity. rather, it is an invitation to become more conscious of the assumptions we bring into the media we consume and create. understanding that names have different jobs, that translation cannot preserve every cultural nuance, and that fandom often reinforces its own conventions allows us to appreciate foreign naming systems on their own terms. and if, after reading all of this, you still decide to call Heian-era Sukuna "Ryomen" anyway... well, i cannot stop you. i can, however, quietly sigh, open another tab, and begin drafting the sequel to this essay.

಄ ⋆ BIBLIOGRAPHY (IT"S JUST WIKIPEDIA)

English honorifics (Wikipedia) given names (Wikipedia) honorifics (Wikipedia) Japanese honorifics (Wikipedia) names (Wikipedia) personal names (Wikipedia) surnames (Wikipedia)

◟ ㅤ© kayuekou, 2026 𖥻 do not copy, reconstruct, or upload on other platforms nor feed my works into generative AI.

note ꩜ hi edit. it’s 1am i forgot to link my sources. i’ll add it to the bibliography in like a couple hours after i sleep. sorry everyone. oh and also, deleted the second paragraph of my background because apparently it got duplicated

"we have class in thirty minutes" you whisper.

"maki can wait" he grumbles, his arm winding around your waist to pull you closer, effectively pinning you to the mattress. "stay. just for a bit."

it's rare to see him this soft, stripped of the "prodigy sorcerer" title and just being a tired teenager who wants to spend five more minutes in bed with the person he loves.

he smells like laundry detergent and a hint of sandalwood, and for a second, the curses and the missions feel miles away.

the moment you try to sit up, his grip tightens just a fraction. he's still mostly buried in the pillows, but he reaches out. his hand sliding around your waist to pull you back down into the warmth. he doesn't say anything.

just a low, contented hum against your skin as he tucks his face into the space between your shoulder blades. his skin is warm, and for a second, he's just a heavy, sleepy weight holding you tethered to the bed.

then, with a sharp exhale that signals he's finally accepted the day, he lets go.

he sits up, running a hand through his dark hair—which is somehow even more gravity-defying in the morning—and blinks slowly at the wall. "fine. i'm up" he mutters, though he looks like he's still fifty percent asleep. which just makes you chuckle quietly.

he stands up, stretching until his joints pop, and gives you one last lingering look before heading toward the bathroom. "don't fall back asleep. i'm not dragging you to class."

while the sound of the shower starts up, you shuffle into the small kitchenette area.

the dorm is quiet, save for the muffled spray of water and the clink of mugs. you move on autopilot, reaching for the coffee grounds. it's a quiet, domestic rhythm you've both fallen into. you know exactly how he likes his—strong, black, no sugar—because he claims the bitterness helps him "actually function."

by the time the steam is rising from the two mugs, the bathroom door opens. he emerges in his high-collar uniform, looking much more like the stoic fushiguro megumi the world knows, though his hair is still damp at the tips.

he stops when he sees you standing there, steam curling around your face as you hold out his mug. the sharp, focused look in his eyes softens immediately. he takes the cup, his fingers brushing yours for a second longer than necessary.

"thanks" he says softly, taking a slow sip and closing his eyes as the caffeine hits. he leans back against the counter, watching you over the rim of his mug with a look that's far too soft for 7:00 a.m. "go get ready. i'll make you a butter bagel."

you nodded once with a soft small, taking a sip of your coffee to then go wash up and change into your uniform. It doesn't take you long. you don't want your coffee to get cold. as you step out he's sitting, the bagel with butter spread already made. his eyes focused on the window.

you sit next to him then "thank you" your voice soft as he just hums. breakfast passes quickly as you both fall into a light chatter about yesterday's movie.

"you fell asleep 30 minutes in, fushiguro" you reproached

"not my fault the movie was that boring" he murmured making you let out a fake offended gasp making him chuckle. The way his eyes crinkled made your heart skip a bit. he looked so soft, so light.

"next time just clip your eyelids open" you teased. his head shaking as he rolled his eyes smiling.

"yeah, sure. come on, let's go." he got up then, picking up the plate and mugs rinsing them as you stretched and went to put your shoes on. he did the same as he was done.

as soon as the door opened, the one next to his did too. Yuuji was stepping out right then.

"morning lovebirds" the pink haired guy said with a smile

you rack through your memories, replaying every single moment from you entering to park to the last time you saw him.

the food stalls.

you grip sukuna’s arm harsher than needed, albeit it does not hurt him, and march towards the stalls.

sukuna starts asking the vendors for a kid with a similar hair color to him. they all shake their heads mumbling excuses.

“nonsense” sukuna mutters to himself, “everyone here is a fool”

“not more than us” you sigh gripping your chest in an attempt to slow down the incoming panic coursing through your veins.

“listen” sukuna suggests, “we should split up”

“bad idea, better we stick together unless we start going in circles” you breathe hard, gasping out the last few words, worst case scenarios flashing through your mind.

sukuna grabs you by both your arms, you shake your head in protest and he grips you harder, not bruising just firm.

“listen to me” he speaks and you nod, “we’ll find him okay? and damn the heavens if i leave this place without my son”

you lick your lips, “yeah let’s..um call me, text, whatever just..”

the world seems to move in a blur.

you’d been so happy, all of you, yuji insisted on coming here and you obliged ofcourse, you’d do anything for your son. yuji’s laughter on the rides, sukuna carrying yuji on his shoulders, yuji’s cotton candy stuffed cheeks.

you inhale shakily.

“i will,” sukuna calls out starting to walk away.

you turn around in haste, praying, praying, praying.

please let my baby be safe.

until—

“may we have your attention, please.”

your pulse jumps in your throat.

“the parent or guardian of a young boy waiting with our lost and found team is requested to proceed to the main entrance.”

you turn around searching for sukuna to find his eyes already on you.

“again, the parent or guardian of a young boy waiting with our lost and found team, please make your way to the main entrance. thank you.”

before your mind could catch up, you’re running. with sukuna only a step behind you, you both make for the main entrance.

closing up to it you spot him instantly, and you stop in your tracks.

sukuna walks ahead, speaking to the security guard who just laughs while saying something, but you’re too busy to notice. your eyes are frantic you scan your son head to toe.

he’s fine, he’s okay.

the rope of panic that had tightened around your chest loosens. you watch from a distance as yuji bounces on his feet, asking sukuna to pick him up while your husband rubs his neck, thanking the security guard for keeping your son safe.

and then yuji’s eyes flick over to yours.

“mama!!” he comes running.

you hadn’t realized how much that sound had meant to you, not until you’d been faced with the possibility of losing it.

you bend down scooping baby!yuji up into your arms and peppering his face with kisses, while he squeals and giggles.

opening up his hand, yuji proudly shows you a fidget spinner as if nothing had happened, as if he hadn’t been lost “gun man gave me a gift!”

children were so clueless.

and you were too elated to speak, this just the act of holding your son, having him in your arms again meant everything.

“did you say thankyou, to the security guard?”

“duh” he droned, already looking around for some mischief to get up to.

you felt sukuna’s arms close around the both of you pulling you into a hug. he kissed the side of your head for a moment too long and you understood.

this had been just as frightening for sukuna.

though he’d never admit it.

but you knew, just from the way he slightly rubbed your shoulder and listened to yuji’s rambles attentively.

“he’s smart” his voice came out rough,

you leaned your head back against his chest, raising a brow in question.

“found the security guard himself, told him that he couldn’t find his mama and papa” he chuckled slightly, “brat didn’t even cry one bit”

you buried your nose in yuji’s hair and sighed contentedly.

“and here i was losing my mind” you murmured.

sukuna shrugged, “…and here we were”

yuji crawled out of your grip onto sukuna’s shoulders, cheerfully pointing around,

“can we go on that next?”

firefly; i’ve had this idea for so long, i just figured out how to execute it ❀ུ͏