Dr. Sarah Okonkwo had been on Kepler-7 for eleven days when she heard the term that would change her research trajectory. She was in Ring C’s maintenance bay, recording device pressed against her palm, watching Maya Reyes recalibrate a quantum node that had been throwing errors for six hours.
“Ang bituin na ito ay nag-uumpisa nang maging patay,” Maya said to her pod-mate, Jun. The star is starting to die.
Sarah’s Tagalog was functional enough to catch the metaphor. She pressed record.
Jun handed Maya a diagnostic scanner. “Kailan mo huling nakita ang ganito?“
“Noong nakaraang buwan. Pero mas mabilis ngayon.“
Maya swapped out the node’s cooling assembly, checked the entanglement stability readings, then pulled back and wiped her forehead. The temperature in Ring C fluctuated between eighteen and twenty-six Celsius depending on which side faced the sun. Right now it was climbing toward twenty-four.
“Bituin na patay,” Maya said finally, pointing at the failed node. “Dead star.”
Sarah made a note: bituin na patay — catastrophic node failure. Etymology: star metaphor. First recorded use: Maya Reyes, 2089-03-15, 14:23 station time.
Later that day, she watched Arnel Santos file the incident report. He sat in his private cabin in Ring B, door open, typing with the careful precision of someone translating between worlds.
“Node experienced critical malfunction,” he wrote. “Cooling system failure led to entanglement destabilization. Replacement required.”
Sarah leaned against the doorframe. “Maya called it bituin na patay.”
Arnel looked up. His face showed the particular exhaustion Sarah had started to recognize in the supervisors — the weariness that came from being a bridge between languages that were drifting apart.
“Dead star,” he said in English. “Yeah. That’s Maya’s term.”
“But you didn’t use it in the report.”
“Earth-side doesn’t speak Technical Tagalog.” He turned back to the console. “They need Institutional English. ‘Node malfunction’ is the term in the manual.”
“But it’s not the same thing.”
Arnel’s fingers paused over the keyboard. “No,” he said quietly. “It’s not.”
Sarah had come to Kepler-7 to study orbital language evolution. What she’d found was more complex than simple creole formation. The crew operated in three distinct languages, each serving a different social function, and the boundaries between them were starting to blur.
Technical Tagalog was the work language. Filipino-based but heavily modified with invented terms for orbital engineering problems that had no Earth-side names. It changed constantly as crews encountered new malfunctions and coined new terms to describe them.
Institutional English was the administrative language. Formal, frozen, preserved from the station’s 2061 founding documents. It was the language of official reports, crew evaluations, communications with Earth-side management.
Bahay-Tagalog — home Tagalog — was the intimacy language. Pure Filipino with minimal code-switching. It was the language of crew quarters, of meals eaten in the cramped galley, of complaints and jokes and the small moments of connection that made eighteen months in orbit bearable.
Sarah had been documenting the lexical innovations in Technical Tagalog. But what she was beginning to realize was that the three languages weren’t just coexisting. They were pulling apart.
On her fifteenth day, Sarah interviewed Amihan Cruz in the observation module. Amihan was eight months into her first contract, young enough that her face still showed surprise at the Earth’s curve through the viewport.
“How’s the adjustment?” Sarah asked in English.
Amihan’s shoulders tensed. “Okay naman,” she said.
“Can we talk about the technical vocabulary?”
“Ah.” Amihan looked down at her hands. “Yes. The technical vocabulary is… challenging.”
The switch to English was deliberate. Amihan had learned that English signaled formality, competence, the performance of professional adequacy. But her Technical Tagalog was weak, and she knew it.
“What’s challenging about it?”
“May mga salita na hindi ko pa alam.” Amihan caught herself, switched back to English. “The terms change very fast. Maya and Jun, they use new words every week. I ask Maya to explain, but then next week there are more new words.”
“Do you use English when you’re working?”
Amihan’s face flushed. “Minsan. Sometimes. I know it sounds… ang formal. But I don’t want to use the wrong Technical Tagalog word and sound stupid.”
“What do the others think when you use English?”
“Hindi ko alam.” Amihan looked out the viewport. “Maybe they think I’m trying to sound… importante. Like I think I’m better than them. But I’m not. I just don’t know the right words yet.”
The mistranslation incident happened on day twenty-three.
Sarah was in the command deck when the alarm sounded. Array Delta was showing signal degradation. Arnel pulled up the diagnostic readout.
Maya’s voice came through the comm from Ring C. “May problema sa delta array. Ang kwantum na bituin ay may —” She paused, searching for the term. “Pagkasira ng tinig.“
Arnel’s hand hovered over the response button.
“Repeat that,” he said in English. “What kind of signal degradation?”
“Ang bituin ay —” Maya stopped. Switched to Technical Tagalog. “Pagkasira ng tinig. Ang signal ay nawawala nang unti-unti.“
Arnel typed into the console, pulling up the manual. The seconds stretched.
“Is it node decay or entanglement drift?” Arnel asked.
Maya’s frustration came through the comm clearly. “Hindi ko alam kung paano sabihin sa English. Tingnan mo lang ang readout.“
Arnel pulled up the data stream. His face went pale. “How long has it been degrading?”
“Sampung minuto.“
Ten minutes. The array had been failing for ten minutes while they argued about terminology.
Arnel slammed his hand on the emergency protocol button. “All crews, array delta offline. Rerouting traffic to gamma and epsilon. Maya, full shutdown procedure, now.”
The rerouting took six minutes. Six minutes of dead air across sixty percent of Earth’s interplanetary data traffic. Six minutes that would generate an incident report, an investigation, possibly contract penalties.
When it was over, Arnel sat back in his chair and pressed his palms against his eyes.
“What happened?” Sarah asked quietly.
“Pagkasira ng tinig,” Arnel said. “Voice damage. Signal damage. It’s a Technical Tagalog term for when the entanglement coherence starts to degrade but the node itself is still functional. It’s not in the manual because the manual is from 2061 and we didn’t understand entanglement degradation patterns until 2075.”
“So there’s no Institutional English term for it.”
“There’s ‘signal degradation,’ but that’s too broad. It could mean anything. Maya was trying to tell me it was pagkasira ng tinig specifically, but I didn’t recognize the term fast enough.”
The next morning, Sarah found Maya in the Ring C galley, eating breakfast alone. She looked like she hadn’t slept.
“Pwede ba akong maupo?” Sarah asked.
Maya gestured to the bench across from her.
“I wanted to ask about yesterday,” Sarah said carefully. “Ang pagkasira ng tinig.“
Maya’s jaw tightened. “Alam mo ba kung ano ang nangyari pagkatapos?“
“Arnel filed the incident report.”
“Oo. At sinabi niya sa Earth-side na ‘node malfunction.’ Hindi ‘pagkasira ng tinig.’ Hindi nila maintindihan kung gaano kaseryoso.“
Sarah pulled out her recording device. “Can I record this?”
Maya looked at the device, then at Sarah. “Para sa research mo?“
“Yes. But also because I think it matters.”
Maya shrugged. “Sige.“
Sarah pressed record. “Tell me about pagkasira ng tinig. When did you start using that term?”
“Mga tatlong buwan na. Nakita ko ang pattern sa readouts. Ang signal ay hindi nawawala nang bigla. Unti-unti. Parang namamatay ang tinig.“
“And you needed a term for it.”
“Oo. Kailangan namin ng salita para sa bagay na iyon. Kaya ginawa ko ang ‘pagkasira ng tinig.’ Ginamit ko ito kasama sina Jun at ang iba pang technicians. Naintindihan nila.“
“But Arnel didn’t.”
Maya’s hands clenched around her fork. “Si Arnel ay nasa Ring B. Siya ay supervisor. Hindi niya naririnig ang mga salitang ginagamit namin sa Ring C.“
“So when you needed to communicate during the emergency—”
“Wala siyang ideya kung ano ang sinasabi ko.” Maya pushed her plate away. “Pagod na pagod na ako sa pagsasalin. Bawat shift, kailangan kong mag-isip: Anong salita ang gagamitin ko? Technical Tagalog ba? English ba? Kung gagamitin ko ang maling salita, hindi nila ako maintindihan. Kung gagamitin ko ang English, tutulong akong peke.“
“What would help?” Sarah asked.
Maya looked at her for a long moment. “Magtanong ka kay Arnel. Siya ang tulay. Siya ang nakakaalam kung paano ayusin ito.“
Sarah found Arnel in his cabin that afternoon. He was reviewing maintenance logs, his screen filled with Technical Tagalog terms that he was systematically translating into Institutional English for the monthly report.
“Can we talk about the language problem?” Sarah asked.
Arnel looked up. His eyes were tired. “There’s no language problem. The system works.”
“Yesterday’s incident—”
“Was an operational error. I should have recognized the term faster.”
“But you couldn’t recognize it because you didn’t know it. And you didn’t know it because Technical Tagalog is changing faster than you can keep up.”
Arnel closed his screen. “Dr. Okonkwo. I’ve been on this station for four years. I’ve done two contracts. I’ve translated thousands of maintenance reports, hundreds of shift handovers, dozens of emergency protocols. The system works.”
Sarah pulled up her data on her tablet. “I’ve been mapping the lexical innovation rate. Three months ago, Technical Tagalog was adding an average of four new terms per week. Last month it was six. This month it’s nine.”
Arnel stared at the graph. “So what? Languages change. That’s normal.”
“But you’re the bridge between the languages. You’re the one doing the translation work. And the gap is getting wider.”
He rubbed his temples. “What do you want me to say? That I’m losing words? That there are Technical Tagalog terms I knew six months ago and now I can’t remember the English? That every month it takes me longer to find the right institutional term for a new technical concept?” He looked at her. “Yes. That’s what’s happening.”
He turned back to his screen, pulled up a maintenance log from two months ago. Pointed at a term: hanging na bituin.
“I used to know what this meant in English,” he said. “Unstable node. Fluctuating signal. But now when I see hanging na bituin, I just… know what it means. I don’t translate it anymore. I understand it directly in Technical Tagalog. And when I have to write the English report, I have to think backwards. Start from the concept, find the institutional term. It takes longer every time.”
“Have you told Earth-side management?”
Arnel laughed, but there was no humor in it. “What would I tell them? That the crews are inventing too many words? That Technical Tagalog is evolving too fast? They’d say: enforce Institutional English as the operational language. Make everyone use the manual terms.” He shook his head. “But we can’t. The manual is from 2061. It doesn’t have terms for half the things we deal with up here. Technical Tagalog exists because we need it.”
“So you’re trapped.”
“We’re all trapped,” Arnel said. “The crews need Technical Tagalog to do their work. I need Institutional English to communicate with Earth-side. And the gap between them keeps getting wider, and I’m the only one trying to hold them together, and I can’t—”
He stopped. Switched to Filipino. “Hindi ko na kaya.“
Sarah spent the next two weeks interviewing crew members across all three shifts. She recorded conversations in the galley, in the maintenance bays, in the observation module. She documented code-switching patterns, lexical innovations, mistranslation incidents.
What emerged was a picture of a system under increasing strain. The older crew members had built fluency in Technical Tagalog over years. The newer crew members were learning it as a foreign language, but the language kept changing before they could master it. The supervisors were exhausted from constant translation labor.
And Earth-side management, reading the incident reports in Institutional English, had no idea how serious the communication problem was becoming.
Sarah compiled her findings into a presentation. She titled it “The Lexicon Problem: Semantic Drift and Communication Failure on Kepler-7.”
She gave the presentation in the command deck on day forty-two. The entire gamma shift attended — Maya, Jun, Amihan, and eight other technicians from Ring C. Arnel came, along with two other shift supervisors. Even Commander Chen showed up, though she sat in the back and didn’t say anything.
Sarah pulled up her first slide: a graph showing lexical innovation rate over the past three years.
“Technical Tagalog is changing faster than it ever has before,” she said. “Three years ago, crews were adding about two new terms per week. Now it’s nine.”
She pulled up the next slide: a timeline of mistranslation incidents over the past year.
“Six months ago, there was one mistranslation incident every three months. Now there’s one every two weeks.”
She pulled up the final slide: archived communication data.
“This is the interesting part,” she said. “I requested archived maintenance logs from the 2086-2087 rotation. That crew had a lower mistranslation incident rate than you do. Their lexical innovation rate was also lower — about four new terms per week instead of nine.”
She zoomed in on a note in the archived files. “They had an informal glossary. A shared document where they recorded new Technical Tagalog terms along with their Institutional English equivalents. It was maintained by a technician named Luis Mendoza. He updated it every two weeks.”
Maya sat up. “Bakit hindi nila sinabi sa atin?“
“The glossary wasn’t official,” Sarah said. “It wasn’t part of the station protocols. When that crew rotated out, the document stayed in the archives. Your crew didn’t know it existed.”
Arnel was staring at the screen. “So we could stop this.”
“You could manage it,” Sarah said. “The drift won’t stop. But you could track it.”
The meeting ran for two hours. Crew members argued in three languages, switching between Technical Tagalog and Bahay-Tagalog and Institutional English depending on who they were addressing and what they were trying to say.
Maya wanted a comprehensive glossary. Arnel wanted Earth-side management buy-in. Amihan wanted learning support.
Jun spoke for the first time, his voice cutting through the argument. “Sino ang mag-maintain nito?“
The room went quiet.
“Isa na namang trabaho,” Jun continued. “Mayroon na tayong maintenance logs, shift reports, safety protocols. Ngayon gusto ninyo ng glossary din? Sino ang magsusulat? Sino ang mag-update bawat linggo?“
Maya turned to face him. “Ikaw ba ay tumutol?“
“Tinatanong ko lang kung sino ang magbabayad ng presyo,” Jun said.
The glossary would solve the translation problem by creating new documentation labor. Someone would have to do the work.
“Kaya nga collective ito,” Maya said. “Hindi isang tao lang. Lahat tayo.“
Jun shook his head. “Alam mo kung ano ang mangyayari. Magsisimula tayong lahat. Tapos unti-unti, tatapusin na lang ng iilan. Tapos isa na lang. Tapos wala.“
Commander Chen spoke from the back. “What if it’s part of shift protocols? Rotation duty, like maintenance logs.”
“Mas maraming paperwork,” Jun said. “Mas maraming oras na ginugugol sa pagsusulat kaysa sa aktwal na trabaho.“
Arnel stood up. His voice was quiet but steady. “I’ll do it. Initial documentation, first three months. If it works, if the mistranslation rate goes down, we make it official. If it doesn’t, we drop it.”
Jun looked at him. “Tatlong buwan ka nang mag-isa?“
“I’m already translating everything anyway,” Arnel said. “This just makes the translation visible.”
“I’ll help,” Amihan said quietly. “Para sa akin, learning tool ito. Kung tutulong ako sa pag-document, matututunan ko ang terms nang mas mabilis.“
Maya nodded. “Ako rin. Mga terms ko naman ang karamihan.“
Jun was silent for a long moment. Then: “Tatlong buwan. Tingnan natin kung gumagana.“
Sarah spent the next two weeks documenting Technical Tagalog terms. She compiled everything into a shared document: fifty terms with Technical Tagalog definitions and Institutional English translations. She included etymology notes and the names of the crew members who’d coined each term.
Bituin na patay (dead star): Catastrophic quantum node failure. Characterized by complete loss of entanglement coherence. Coined by Maya Reyes, 2089-03-15.
Pagkasira ng tinig (voice damage): Progressive signal degradation. Entanglement coherence decreases gradually over time. Requires node replacement before complete failure. Coined by Maya Reyes, 2089-02-20.
She showed the glossary to Maya first. They sat in the Ring C galley, Sarah’s tablet between them.
Maya scrolled through the entries slowly. Her finger paused on bituin na patay.
“Ginawa mo ito,” she said quietly.
“You made it,” Sarah said. “I just wrote it down.”
Maya looked up. Her eyes were wet. “Minsan naiisip ko na walang silbi ang mga salitang ginagawa ko. Na naglalaho lang sila sa hangin. Pero ngayon nakikita ko sila dito, nakalagay, may pangalan ko sa tabi…“
She stopped. Pressed her palm against the screen, over the entry for bituin na patay.
“Pero alam ko rin na ito lang ang unang hakbang,” Maya said. “Isusulat mo ang mga salita ko, at isasalin ni Arnel sa English, at ipapadala sa Earth-side, at gagamitin nila ang English term, at makakalimutan ang Tagalog. Ganyan palagi.“
Sarah didn’t have an answer for that. Because Maya was right.
“Salamat,” Maya said finally. “Kahit ganyan, mas mabuti pa rin ito kaysa sa wala.“
The glossary went live on day sixty-eight. Sarah posted it to the station’s internal network. Arnel added a note at the top: “Pilot program. Three-month evaluation period. Report errors or suggested additions to Dr. Okonkwo.”
The first week, Sarah received fifteen suggested additions. The glossary grew to seventy terms, then ninety, then one hundred and twelve.
Amihan started using it as a learning tool. Arnel started referencing the glossary in his incident reports. Instead of translating pagkasira ng tinig as “signal degradation,” he wrote: “Signal degradation (Technical Tagalog: pagkasira ng tinig; see station glossary for definition).” Earth-side management didn’t object.
The mistranslation rate fell. By the end of the first month it had nearly stopped — long enough that people started to believe it was working, which was different from it actually working, but close enough for now.
But Jun had been right about the labor.
Sarah watched the maintenance burden accumulate. Every week, new terms needed to be added. Existing definitions needed refinement. The glossary had started as Sarah’s research project, but it was becoming infrastructure, and infrastructure required maintenance.
Arnel spent two hours every Sunday updating entries. Amihan contributed definitions during her off-shifts. Maya reviewed technical accuracy whenever she had time between repairs. The work was distributed, but it was still work.
On day ninety, Jun stopped contributing.
Sarah noticed his absence in the weekly update meeting. Maya was there, Amihan was there, Arnel was there. Jun wasn’t.
“Nasaan si Jun?” Sarah asked.
Maya’s face tightened. “Ayaw na niya.“
They sat in silence with that.
On day ninety-four, Arnel called a meeting.
The command deck was crowded. All three shift supervisors attended, along with a representative sample of technicians from each shift. Commander Chen sat in the front row this time. Jun came, though he stood in the back.
Arnel pulled up a comparison graph: mistranslation incidents before and after the glossary implementation.
“The data is clear,” he said. “The glossary works. Mistranslation incidents are down seventy-three percent. Translation time for incident reports is down forty percent. Crew satisfaction surveys show increased confidence in technical communication.”
He looked at Commander Chen. “I want to submit this to Earth-side for official recognition. Make the glossary part of station protocols. Legitimize Technical Tagalog as a valid operational language.”
Commander Chen was quiet for a long moment. Then she said: “Earth-side will want to control it. They’ll want to standardize the terms. Lock them down.”
“That won’t work,” Maya said. “Ang drift ay hindi mapipigilan. Kailangan lang natin ng paraan para ma-track ito.“
“So we propose a living document,” Sarah said. “Updated monthly. New terms added as they emerge.”
“Who maintains it?” Commander Chen asked.
Sarah looked at Maya. “The crews. It’s their language.”
Arnel nodded. “I’ll coordinate with Earth-side. Make sure the translations are acceptable for official reports. But the Technical Tagalog side belongs to the crews.”
Jun spoke from the back. “At kung ayaw naming gawin?“
Everyone turned to look at him.
“Kung napagod kami,” Jun continued. “Kung mas gusto naming gumawa ng maintenance kaysa mag-update ng glossary. Ano ang mangyayari?“
Arnel met his eyes. “Babalik tayo sa dati. Mistranslations. Communication failures. Ako na naman mag-isa sa pagsasalin.“
“Kaya kailangan nating pumili,” Jun said. “Kailangan nating magpasya kung sulit ba ang trabaho.“
He looked around the room. At Maya, at Amihan, at the other technicians. At Arnel, exhausted from four years of translation labor. At Sarah, who’d documented their language and made it visible but couldn’t maintain it for them.
“Para sa akin,” Jun said, “sulit. Pero kailangan kong sabihin: ito ay trabaho. Hindi lang research project. Trabaho. At kailangan nating tanggapin iyon bago nating ipagpatuloy.“
Maya nodded. “Oo. Trabaho.“
Arnel looked at Commander Chen. “Three more months. We’ll run it for three more months. If the mistranslation rate stays down, if the crews keep maintaining it, I’ll submit it to Earth-side with a recommendation for adoption.”
Commander Chen studied the graph. “And if Earth-side says no?”
“Then we keep doing it anyway,” Arnel said. “Unofficial. Like Luis Mendoza did.”
Arnel’s negotiation with Earth-side took three months.
Sarah wasn’t there for most of it — her contract ended on day one hundred and eighty, and she transferred Earth-side while Arnel was still filing reports, making the case, translating the glossary’s value into language that management would understand.
But Arnel sent her updates.
Week 1: Submitted glossary proposal. Management wants cost-benefit analysis.
Week 3: Provided incident rate data. They want legal review. Concerned about liability if Technical Tagalog terms are used in official reports and something goes wrong.
Week 7: Explained living document concept. They hate it. Want fixed terminology. Trying to make them see that fixed terminology is why we needed the glossary in the first place.
Week 9: Stalemate. They want control. I want flexibility. Crews are still maintaining glossary but asking when it becomes official. I don’t have an answer.
Week 11: They offered a compromise. Official recognition if I agree to quarterly standardization reviews. Every three months, Earth-side reviews new terms and decides which ones are “approved for institutional use.” I said no. Crews said no. We’re back to stalemate.
Week 12: New contact at Earth-side, someone who actually read the incident data. She’s sympathetic but has no authority. Going to try to route it through the technical standards committee instead of legal. Don’t know if this helps or just adds another layer.
Week 13: They approved it. Sort of. Official status as “station-specific supplementary technical documentation.” Not part of core protocols but recognized as valid reference. Monthly updates allowed but subject to annual audit. It’s not what I wanted but it’s something.
Sarah sent back: What did it cost you?
Arnel’s response came three days later.
Contract extension. They wanted someone to “ensure consistency” between Technical Tagalog and Institutional English. I’m now the official glossary coordinator. Eighteen more months.
Arnel sat in his cabin when he sent that message. The contract extension paperwork was still open on his screen. He’d read it three times before signing.
He knew what it would cost. The exhaustion that had settled into his shoulders would go deeper. The words he was already losing would slip further away. The gap between the languages would keep widening, and he would keep trying to hold them together, and eventually he would fail. The thought arrived not as fear but as a simple accounting, the way you might note the weight of something before deciding to carry it.
He pressed his thumb to the signature pad. Watched the contract lock.
“Sige,” he said to the empty room. Okay.
Sarah published her paper six months after leaving Kepler-7. She titled it “Negotiated Stability: Semantic Drift and Collective Coordination in Orbital Technical Creoles.”
The glossary became infrastructure. Standard practice. A model for coordination in isolated technical communities. People cited the paper at conferences. Sarah presented it twice. The paper was the thing that traveled.
Arnel’s contract extension ended on schedule. The new shift supervisor was named Mariz Villanueva. She’d done one previous contract on a different station. She spoke Technical Tagalog adequately. She understood the glossary’s purpose.
She maintained it for four months.
Then she got busy. Incident reports piled up. A new array installation required overtime. The monthly glossary update meeting got postponed. Once. Twice.
Maya kept adding terms on her own.
The first missed meeting, Mariz sent an apologetic message to the crew network: Sorry, array installation running long. Will reschedule for next week.
Next week became the week after. The week after became when things calm down.
What Mariz did not send — what she did not say to anyone — was what she thought when the weekly update notification appeared in her queue on the third postponed week, which was: I know what this is. I know what I’m doing. She looked at the notification for a moment, the way you look at something you’re about to put down in a place where you might not find it again. Then she opened the array report instead.
Maya showed up to the rescheduled meeting six weeks later. She was the only one there. She sat in the empty command deck for a while, her tablet open to the glossary, three new terms she’d wanted to add highlighted and ready.
No one else came.
She closed the tablet. Went back to Ring C. Didn’t mention it to anyone.
The glossary had 173 terms by then. Half of them were outdated. A quarter were duplicates with slightly different definitions. The newest entries had no etymology notes, no usage examples, just bare Technical Tagalog and rough English translations.
Jun noticed. He didn’t say anything. Being right didn’t feel like vindication. It just felt like watching.
Six months after Arnel left, Mariz stopped updating the glossary entirely. She didn’t announce it. There was no meeting, no decision. She just stopped opening the document.
New crew members still looked up terms occasionally. The glossary was there, accessible, a snapshot of Technical Tagalog from 2089-2091. But it wasn’t alive anymore.
Maya sent a message to the crew network: Kailangan natin ng meeting tungkol sa glossary. Nawawala na ito.
Twelve people showed up. Not enough.
They talked for an hour. Made a plan. Assigned responsibilities. Agreed to monthly updates.
The plan lasted six weeks.
Then someone rotated out. Someone else got assigned to a different shift. The meeting time stopped working for people’s schedules.
The glossary didn’t disappear. It just stopped being maintained.
Three years after Sarah left Kepler-7, she received a message from Maya.
Kumusta, Dr. Okonkwo. I hope this finds you well. I wanted you to know: the glossary stopped being maintained about a year ago. We tried. But without Arnel, without regular meetings, it just became too much work on top of everything else. Some of us still use it but it’s outdated now. The drift continued. Mistranslation incidents are up again.
I thought you should know. For your research.
The words I made are still in the glossary. Bituin na patay. Pagkasira ng tinig. My name is still next to them. That matters to me. Even if no one uses the glossary anymore, even if it’s just an archive now, my words are there. Documented. Real.
Salamat for everything. For seeing us. For writing it down.
Sarah read the message twice. She opened a reply window, then closed it.
Maya’s words were still in the glossary. Bituin na patay. Pagkasira ng tinig. Still there, with Maya’s name beside them.
Sarah filed the message under Kepler-7 — field correspondence. Went back to work.
On Kepler-7, Maya was working the overnight shift in Ring C when a node in sector seven began showing a pattern she hadn’t seen before. Not pagkasira ng tinig — different from that. The degradation moved in pulses rather than a continuous fade. Rhythmic. Like something breathing.
She watched the readout for a long time.
Humihinga, she thought. Breathing. Ang humihinga na bituin. The breathing star. Not dying, not damaged. Just — breathing. Which meant it was about to stop.
She said it aloud, quietly, to check how it felt in her mouth. “Humihinga na bituin.“
Jun was across the bay. He looked up.
“Ano?“
“Tingnan mo ang sector seven,” she said. “May bago.“
Jun crossed to her station, looked at the readout, and understood immediately — not from any glossary, not from any manual, but from the pattern and from Maya’s face and from four years of learning to read what she meant when she invented something.
“Humihinga na bituin,” he repeated.
“Oo.“
He started pulling tools. She started the shutdown procedure.
The word existed now. It lived in their mouths. It would spread to the other technicians in Ring C, and the next rotation would hear it and use it without knowing Maya had made it, and someday someone would make it again not knowing it had already been made, and the glossary would never record it at all.
Maya knew this. She had always known this.
She initiated the protocol and did not stop working.
cafebedouin.org 