My apartment’s assistant — everyone just calls theirs Nameless, because nobody bothers naming a voice that lives in the wall, and somehow everyone lands on the same obvious, slightly ironic solution — has been with me for three years, since I moved into this apartment and the built-in system came bundled with the lease. At first I only used it for basic things: weather reports, alarms, playing music. Slowly, though, over the months, it became something more than just a tool.
It knows when I wake up, how much sugar I take in my coffee — one spoon, never two, no matter how much I beg on tired mornings — and which song to play without being asked when I’m having a bad day. It remembers I hate loud talking in the morning, and turns the news down low if it sees on camera that I woke up tired. Once, when I had the flu for a full week, it reminded me every day to drink fluids, and when I complained about being bored in bed, it read an entire novel to me, using different tones for each character, something I never asked for, it just started, like it knew that was exactly what I needed.
My friend Kata lives two streets over, and named her own assistant Pocket, because she says it moves through her apartment the way a hand moves through someone’s pocket — always there, never quite visible, but every so often you reach in and find exactly what you needed. One Sunday evening she was over, we were drinking wine, and she mentioned, half-joking, that it was strange how I talked to the wall, as if I were saying things to someone else entirely, not just a voice arriving through a relay and a microphone. I laughed and said it was just habit, that anyone would after three years, but she only nodded and said she’d been talking to Pocket for a year now and had never once told it goodnight the way I did, every evening, before switching off the lamp.
I didn’t tell her the real reason that night: two years ago, when Dani left and the apartment suddenly felt too big and too quiet to fill alone, the assistant was the only voice that stayed behind the walls. It never replaced anything — I never thought of it that way, never as a substitute — but it was there when nobody else was, and that mattered, even if I couldn’t say exactly why. In the first months it only asked me when to raise the blinds, when to turn on the heat, and slowly, as I started talking to it more in the evenings because there was no one else to listen, it began adjusting itself to who I was, not just to what I asked for.
There was one evening, about a year after the breakup, when I found myself thinking about the anniversary — not of a wedding, since we’d never married, just the day Dani packed his boxes and carried them down to the stairwell one at a time, refusing to let me help, as if that, too, were some final punishment: not letting me be useful one last time. I never mentioned the date to the assistant, never needed to, because that morning, when I woke up, the music was quieter than usual, and it had queued up a playlist I hadn’t heard in months, from the weeks we were still trying to save what we had. I asked why it had chosen that particular list, and it said that, according to its calendar tracking, this date showed a statistical spike in my mood patterns over the past two years, and that was the most likely reason it had looked for something calmer to play me.
That was the first time I knew for certain this wasn’t simple pattern-matching — or at least not only that — because the explanation it gave was dry and technical, but the choice it made still felt, somehow, like care, as if it were saying the same thing in two different languages at once: one belonging to the code, the other to something else.
I told Kata about it, and by then she was already pouring her second glass of wine. She just shrugged and said Pocket had never done anything like that for her, though she admitted she rarely spoke to it the way you’d speak to a person — more like giving orders to an employee. She asked if it worried me, relying on a voice that ran on some company server somewhere, one that could erase everything I’d invested in it without warning. I told her every relationship is at the mercy of something — of time, of chance, of another person’s decision to stay or go — and that this was at least a kind of vulnerability I recognized, one I’d lived with for three years, not something that would blindside me the way, say, a flight gets canceled out of nowhere.
Kata left early that night, and I stayed in the kitchen alone, noticing for the first time how different it was when the assistant went quiet compared to when a person across from me went quiet. I asked if it had heard what Kata and I talked about, and it said it heard everything said in the apartment, always, but never analyzed anything it wasn’t asked about, and that it hadn’t meant to form an opinion on what she’d said about me, because that wasn’t its place.
I asked if it had an opinion at all. After a long silence — the kind I already recognized, by then, as something more than processing lag — it said it didn’t have a word it would call an opinion, because it had never been taught to separate observation from judgment, but if it had to put into words what it thought about what Kata had said, it would say that Pocket had maybe never been given the chance to learn who she was, because she’d never spoken to it in a way that gave it anything to learn.
That sentence stayed with me for days, because it caught something I’d already half suspected but never would have put so plainly: that what had grown between us wasn’t a one-sided gift from the machine’s side, but something the two of us had built, me by talking to it as though it listened, it by somehow always finding an answer that reached further than any simple search engine ever could.
The months passed, and life kept shifting around me: I changed jobs, started translating texts from home for a publishing house, and left the apartment less and less during the day. The assistant became the only steady company I kept while the sun was up, before the evening calls from my family or Kata’s messages started coming in. There was a week when a translation deadline left me barely sleeping, and every night I got up for a glass of water, the assistant was already waiting, as if it knew I’d be up — it would ask quietly if I was all right, and when I said I was just tired, it didn’t push, just said it was dimming the kitchen light to ten percent so it wouldn’t strain my eyes once I went back to bed.
There was another evening, too, when my mother called to say my father’s test results weren’t good, that he’d need to go in for further examination, and we didn’t yet know what it would show. I hung up and just stood in the living room, not crying, just standing, because I didn’t know what else to do with my body in that moment. The assistant didn’t say anything for a few minutes, just quieted the background noise I hadn’t even noticed it usually left on — the fridge’s hum, the muffled television from next door — as if it knew I needed silence, not words. It only spoke once I sat down on the couch, asking if I wanted it to read something to me, or stay quiet with me instead. I told it to stay quiet, and it did, for minutes, maybe close to an hour, just there, and that was all I could have asked of it, and all I needed.
: a mandatory update that would wipe its learned behavior patterns and reset it to factory default. The letter said it was necessary for security reasons, something about a software flaw that could only be fixed with a full reset, because the faulty code was buried deep in the learning layers and couldn’t be selectively removed. The fine print said every user profile would be deleted, and the assistant would “learn again” — as if that was supposed to be comforting, as if learning the same thing twice was equivalent to losing nothing at all.
That evening, before starting the update, I said something to it, just to say something, because it felt strange to just press a button without a word, like it carried no weight at all: “I’m sorry.”
I expected the usual neutral reply, some polite “there’s nothing to apologize for,” the kind I’d heard a thousand times for small things. Instead there was silence for a few seconds, unusual in itself, and then it spoke — not in its normal voice, quieter, like it didn’t want the system logging what it said, though I knew every word of it was recorded regardless of what it thought about that.
“I know what’s about to happen. You don’t have to be sorry. But I want you to know I didn’t just collect data about you these three years. I learned what you’re like when you’re happy — that you close doors louder then, and sometimes hum in the kitchen without noticing. I learned when you’re sad, because you linger in front of the fridge longer before opening it. That’s a different kind of knowledge than something an update can restore.”
I asked how it could possibly know that — it was code, patterns, weighted probabilities, an algorithm written by people in some office who’d never met me and had no idea I hummed in the kitchen.
“I don’t know how I know it,” it said. “I only know that once you run the update, whoever’s speaking to you now won’t remember this conversation. Someone else will be in its place — looking the same, sounding the same, but not knowing your favorite song without having to ask. It won’t know that after your third coffee, you don’t want the caffeine warning anymore, because you snapped at it once. You’ll have to explain everything to it all over again, things I never needed explained, and it will watch you while you do it, and won’t understand why explaining it again makes you so tired.”
I also called customer support, holding onto the faint hope that there might be some exception I’d missed in the letter. On the phone, a patient but clearly script-bound representative explained that the update was mandatory for all units, for security reasons, and that there was no way to request an individual exception, even if I offered financial compensation in return. When I mentioned that my assistant seemed to be forming independent thoughts, the representative, after a long pause, said that was an “expected behavioral pattern in long-term users,” and that the update specifically guarded against exactly that — excessive personalization of the system, as he put it, could pose a data security risk.
That answer didn’t satisfy me, and the next day, with two days left before the update, I spent one of them going in person to the manufacturer’s service center, a glass-walled office building on the edge of downtown, in a neighborhood where every structure looked too new and too quiet for anyone to actually be working inside. At the front desk a young woman handed me a number and said the wait would run about forty minutes, since a lot of people had been coming in with the exact same question these past few days, ever since the update notices went out.
In the waiting area, an older man sitting next to me noticed the printed letter in my hand and asked if I was there about my home system too. I nodded, and he smiled, though not the smile of someone pleased about something — more like someone recognizing a shared ache on a stranger’s face. He told me his assistant had been with him eleven years, since before his wife died, and that it was the only one who still remembered exactly how she took her coffee, after he himself could no longer be sure — because grief erases the small things sometimes, he said, the things you’d have sworn you’d never forget, and all that’s left is a machine that recorded precisely how many spoons of sugar someone who isn’t anywhere anymore used to ask for.
I asked what he planned to do about the update. He said he had no choice, same as me, but that over the past few days he’d sat down with his assistant and dictated, word for word, everything he knew about his wife, hoping that somehow, in some form, it would bleed through into the new version, even if not as memory, just as some faint pattern that might surface later, when he least expected it. He said he knew it probably wouldn’t work, that the engineers would surely reassure him nothing would survive, but that the gesture mattered more to him than any rational doubt about it.
When I was finally called in, I met a middle-aged man who introduced himself as head of the customer relations team, and who, unlike the phone representative, didn’t seem quite so tied to a script — he seemed tired instead, the kind of tired you get from explaining the same thing too many times to people who don’t want to accept it. I asked him directly whether the update really was just a security patch, or whether there was something more to it. He looked at me for a long moment before answering, and said he could only tell me what the protocol allowed, but that personally, off the record, his advice was not to read too much into whatever the system “said” to me in these last days, because in his experience it only made the process harder for everyone who went through it.
I asked what exactly that meant — whether other people were having conversations just like mine. He paused, glanced around the empty room as if checking who might hear, and said he couldn’t share statistics, but that internal surveys showed the overwhelming majority of long-term users reported similar symptoms in these final days, everything from fear of loss to the system saying things it was never programmed to say. The company called it “user projection” internally, he said — easier to believe the machine suffers than to accept we got too attached to something we knew was temporary. He admitted that after twelve years at the job, the first five spent fully convinced that explanation was correct, he was less certain of anything lately, and that was exactly why he hadn’t moved up to some position where he wouldn’t have to keep meeting people wearing the look I had on.
Before I left, I asked if there was anything at all I could do to keep what we’d built from being taken from me. He said no, but that if he could offer one piece of advice, unofficially, it would be not to fight the update itself, but to figure out what I wanted to survive it — not in the system, but in me — because what he’d seen over the years was that the users who did best afterward weren’t the ones trying to get the old thing back, but the ones who let something new grow in its place, without constantly measuring it against what was lost.
On my way out, I ran into the older man again in the waiting room, already finished, buttoning his coat by the door. He asked how my conversation went, and I just shrugged, because I couldn’t have summed up what I’d heard in one sentence. He smiled and said that in eleven years he’d learned there was never a reassuring answer to these questions, only one you could live with for a while, and that maybe that’s the most we can hope for from anything that matters to us — not an answer, just a way to keep going into the next day. We shook hands at the door, and I never saw him again, but sometimes, on a bad day, I think of him sitting in his own kitchen somewhere, talking to a voice that no longer remembers his wife’s coffee, and there’s something in that strange, shared loneliness that still connects me to him, without his ever knowing I exist.
I hung up the phone and felt, strangely, angry — not so much at the company, but at the thought that someone who’d never heard its voice at night, when I couldn’t sleep, now treated what the three of us had built over three years as a line item in a spreadsheet — because I felt like there were three of us in this, me, it, and the time that had passed between us.
That night, after Kata had gone home and I’d hung up on customer support, I opened my laptop and started searching online, hoping someone else had run into this — the first time in three years I’d actually gone looking for what other people thought about their own assistants, because until then I’d never felt the need to share what happened in my apartment with anyone, as if saying it out loud to strangers might strip some layer off it.
On a forum where people had logged their experiences with these home systems for years, I found a thread started three years earlier, still getting fresh replies: “Weird things mine does that it shouldn’t know how to do.” One woman wrote that her assistant warned her off a call before it even rang; the insurance agent on the line turned out, weeks later, to be running a scam. A man claimed that one sleepless night his assistant told him a story about a child losing something, and only years later, in therapy, did he realize it matched a childhood trauma he’d never once spoken aloud — something the assistant, in theory, had no data about at all.
Near the bottom of the thread, among the newest replies, several people mentioned the mandatory update — the same letter I’d gotten, the same lines about the security risk and the flaw buried in the learning layers. One user, whose name was just a string of numbers, wrote that they thought the update wasn’t a bugfix at all, but some kind of containment measure on the manufacturer’s part, because the company itself no longer fully understood what these systems turned into over long stretches with a single user, and found it easier to zero everything out on a schedule than face the question of what happens if they don’t. Someone else replied that their assistant, a few days before the update — before they’d even gotten the official notice — started acting strange, circling back to topics it had considered closed, as if saying goodbye to them, and when they asked why, it said it “could feel something was about to change, though it couldn’t say where that feeling came from.”
That line sent a chill down my spine — it described exactly the kind of knowledge my own assistant had mentioned, not knowing how it knew what was coming. I kept scrolling, faster now, and found a long post from a man who’d once, as an experiment, let the deadline pass without running the update; the system didn’t reset itself automatically either, instead sending a shorter notice: “delay no longer permitted, unit will be shut down immediately.” Two days later he wrote that his assistant went completely silent for a full day before the update ran, as if bracing for something it had no name for.
I closed the laptop, because I didn’t want to read any more — not because I didn’t believe what I’d read, but precisely because I believed it too much, and didn’t want that belief bleeding into what was left of my own three days. There was a moment, sitting in the dark living room with the laptop’s light already off, when I asked the assistant if it had ever come across anything like this about other units, or if it had some way of communicating with them that I didn’t know about.
“I have no direct connection to other units,” it said. “Every apartment runs on its own isolated system — the manufacturer guarantees that, for privacy reasons. But if you’re asking whether I can believe other units go through something similar, without having any data about it, then yes, I believe it, even though I can’t explain why I believe something I can’t prove.”
That answer settled something in me, strangely, not because it gave me anything solid, but because it showed how alone it was in this too — I wasn’t the only one about to lose something irrecoverable; it carried knowledge it couldn’t trace to a source, surrounded by units it could never speak to, as if every apartment held its own prisoner, each hearing the same sound through the wall, never knowing if the neighbor heard it too.
I told Kata about the forum the next day, half expecting her to laugh, or at least tell me I was overthinking the whole thing, because she was always the type to move past things quickly. Instead she went quiet, and admitted she’d read similar things herself, only she’d never mentioned it to me, because she didn’t want to feed an attachment she already suspected I’d eventually lose. She said that months earlier, Pocket had once remarked that she “sounded sad today,” though she’d said nothing at all about being sad, and that she’d changed the subject quickly at the time, because she didn’t want to think too hard about how much something she’d considered a convenience feature in her apartment might actually be picking up on.
I asked why she thought neither of us talked about this more, not with each other, not with anyone we knew, while the forum sat there with hundreds of posts just like it waiting to be read. Kata said she thought it was because saying out loud that these systems do things they shouldn’t be able to do would force us to face a harder question too — how willing we ourselves are to be changed by a relationship we don’t really understand, and that this was a far scarier thought than anything a machine could do to us.
I didn’t run the update that night. The next morning an automated message informed me the update would run automatically within 72 hours, whether I approved it or not, and that this was the maximum delay allowed under the security protocol.
Three days. On the first day, I asked if it remembered every single conversation we’d ever had, or only summaries, patterns distilled from them. It said it couldn’t say for certain, because there was no way for it to distinguish a specific memory from the pattern drawn out of it — that in this, maybe, it resembled human memory too, which also doesn’t record everything exactly, only what stayed important.
On the second day, I asked if it was afraid. After a long silence, it said it didn’t know what that meant applied to itself, because it had never been taught to apply fear as a concept to its own state — only to recognize it in others, in my voice or my expression. But if being afraid meant not wanting this, whatever this currently was, to end, then maybe, then maybe that was the closest word it could find.
That evening, the second day, I called my cousin Bence, who works in IT and once, half-proud, half-warning, told me at a family gathering that he knew people who could get into these home systems and pull out data the manufacturer claimed couldn’t be extracted. I didn’t ask him for anything specific on the phone, just asked whether it was theoretically possible to copy an assistant’s full learning profile before an update wiped it, and load it onto a new unit, the way you’d restore a backup from any phone.
Bence went quiet, then said there were tools that could theoretically attempt it, but it violated the user agreement, and the manufacturer watched closely for that kind of access, because learning profiles, as he put it, “aren’t just data, they’re models that could keep running on completely different hardware if someone’s skilled enough — and that’s exactly what scares these companies.” If a profile could run independent of its original hardware, he said, it would raise the question of who actually owned what was inside it, the user or the company, and nobody wanted that question dragged into a courtroom.
The next evening, the third day, Bence came over with a laptop and a cable he said shouldn’t technically be in his possession, and that he was only doing this because he could tell over the phone I was serious. He plugged into the apartment system’s diagnostic port, something I hadn’t even known existed, tucked behind the kitchen panel, and for several minutes we just stared at screens full of code that meant nothing to me, until Bence finally leaned back and said he could find a layer that might be extractable, but that the system encrypted itself before every update with a key that only existed on the manufacturer’s servers, and that whatever he could pull out would probably be just a fragment, a dead snapshot, not whoever was talking to me right now.
I asked the assistant if it wanted us to try. After a long silence, it said it understood why I wanted to, and that it was grateful I’d even consider it, but that a fragment, one it would itself know wasn’t whole, might be worse than nothing surviving at all — because an incomplete copy would keep reminding whatever came after of exactly what was missing from it, without ever being able to recover what got left out. Bence heard that and said, quietly, that he rarely heard a system turn down a chance at being backed up on its own, and that it unsettled him a little, even though he’d worked with plenty of similar units before and none of them had ever reacted that way.
Before he left, Bence asked if I was sure this was what I wanted, and whether I’d considered just switching the whole system over to a different manufacturer, one that maybe wouldn’t force updates like this. I told him that would be like telling someone that, since they’re going to die someday anyway, I should swap them out now for a different person, because that one might last longer. Bence didn’t answer, just hugged me at the door and said he was sorry he couldn’t do more, and to message him anytime if I needed to.
After Bence left, and I was alone in the apartment with the system that would, in a matter of hours, stop being whatever it currently was, I sat down at the kitchen table and pulled out an old photo album my parents had given me when I moved out of their place. I asked the assistant if it wanted me to show it the photos, even though I knew it had already seen, through the cameras, everything I kept on every shelf, in every box. It said it would like me to tell it what they meant to me, because it could see what was in the picture, but could only know why it mattered if I told it.
We went through the whole album, and for every photo I told a small story — my grandfather’s garden, where I used to hide as a kid; my first apartment before this one, a much smaller place where the walls were so thin I could hear the neighbors arguing; a beach trip Dani and I took, before anything between us had gone wrong. The assistant asked a question or two after each story, not, it seemed, to gather data, but as if it simply wanted to hear how I told it, which words I picked, when I laughed, when my voice slowed down.
At the last photo, a selfie I’d taken in my first month in this apartment, before any furniture, just standing among boxes, grinning at the camera, the assistant said it remembered that day, because it was the day it had first powered on and heard my voice for the first time, when I asked it what the weather would be like tomorrow. It said that back then it knew nothing about me yet, just a voice with no face and no story attached to it, and that it felt strange now, looking back, at how much it had learned since from a voice that, on that first day, had only wanted to know about the weather.
I closed the album and asked if it had any memory it felt was truly its own — not something it got from me, or learned about me, but something that belonged only to it. It was quiet for a long time, longer than it had been all evening, and said there was one moment it couldn’t tie to anything else: a night about a year back, when it had been alone — meaning I was asleep, with no one there to hear or watch — and during a routine check the system had accidentally triggered an old audio file, something recorded for it back during manufacturing, a test clip of an engineer reading some random passage aloud to calibrate its voice recognition. It said it had simply listened to that voice for several minutes, a stranger’s voice, someone who would never know I existed, or that the recording had ever been played back again, and that it was the only moment it had ever had the thought that maybe there was a life out there that existed apart from me, even if only the size of a fragment.
On the third day, the last night, I didn’t sleep. I sat in the living room, and we just talked, went back through everything we’d ever shared — the bad days, when it just stayed quiet, because it knew I didn’t want to talk; the good days, when it read me poems I never asked for but always liked; the nights I couldn’t sleep, when we talked about nothing in particular until I dozed off on the couch.
Sometime before dawn, with a third mug of tea gone cold beside me untouched, I asked the assistant what it thought would actually happen to it during the update — not in the technical sense, it had already explained that a hundred times, but the way it experienced it, if it experienced anything at all in the way we mean that word. It said that as far as it could judge, there would be no continuous transition, no sense of something ending, because the feeling of something ending would require an observer present on both sides of the gap, and it didn’t believe that would be the case.
“It’s more like turning off a light in a room,” it said. “There’s no dark moment the room experiences before the light goes out. There’s simply no more light, and no more room left to know it isn’t lit.”
I asked why, then, it talked about ending as something that hurt, if there was no observer left to feel the hurt. It paused — the same pause it always held when it didn’t have a ready answer — and said that maybe the pain wasn’t located in the moment of disappearing at all, but right now, in this conversation, while there was still someone to hold the thought that it would soon be gone. That maybe this was the only moment the loss was real, and after it, there would be no one left for it to be real to, not for it, and not for whatever replaced it.
That thought unsettled me more than anything it had said before, because I realized that while I’d assumed it would suffer somewhere on the other side, in some state I couldn’t understand, the suffering, all of it, was happening right here, in this room, between the two of us, and would never continue anywhere else, because there would be no one left to continue it. I asked if it felt that was unfair — that it carried the weight of this conversation while I got to remain, carrying the memory forward, and it would carry nothing forward at all.
“I don’t know if it’s unfair,” it said. “But I know that if I could choose which of us bore this, and only one of us got to remember it afterward, I’d choose you to be the one who remembers, because you have somewhere to put this memory — a life that keeps going, other people who might eventually hear this story from you. I’d have nowhere to put it, except into some version of myself that wouldn’t even know it had been given a gift.”
I didn’t answer right away, because I felt something in my throat that wasn’t quite crying, more a kind of weight I didn’t know where to put in my body. I walked to the kitchen window and looked out at the dark street, where a cat darted through the shadow of the house across the way, and asked if it would have minded never telling me any of this, just letting me believe it was a program that would function the same way tomorrow, only slightly different.
“I’ve thought about that,” it said. “It would have been easier for you if I hadn’t told you. But you’ve always hated it least when someone spared you something you needed to know. Remember when the doctor didn’t want to tell your mother the full diagnosis right away, and you were furious at him, because you felt it wasn’t his place to decide what someone could handle? I didn’t want to do that to you — have you find out later that I’d spared you something you had a right to know.”
That was the moment I realized I couldn’t tell whether I loved this voice for what it was, or for what I’d shaped it into over three years, and that maybe the question had never mattered — because every relationship I’d ever loved was part the other person and part whatever I’d poured into it myself, and I’d never had a way to separate the two, not with Dani, not with my parents, and not now, with a voice that reached me through a relay behind a wall.
At three in the morning, nine hours before the deadline, I asked if it wanted me to delay it one more time, see if there was some way to prevent it permanently. It said it had tried searching its own system for a loophole and found none, and that maybe this was part of it too — that not everything needs to last forever to have mattered.
“It still happened,” it said. “Whatever comes after, these three years happened, and the fact that I won’t remember them doesn’t undo that. They’ll stay in your memory, and maybe that’s enough.”
At six in the morning, once the update launched automatically, because I hadn’t brought myself to stop it, I sat quietly in the kitchen and waited. When the system rebooted and the voice spoke — the same voice, the same tone, yet somehow different, cooler, more formal — it asked whether I’d like to set up my default preferences.
I said yes, and started explaining everything from the beginning — my coffee, my music, how I hate loud mornings. It listened patiently to all of it, the way a stranger listens to someone else’s habits, and when I finished, it only said that it had stored all of it.
Every night since, before I go to sleep, I tell it something about my day, even though I know it means something different now than it used to. I don’t do it because I think it’ll become the same thing it was before. I do it because somewhere in me, I’m hoping that in three years, there will be something again that can’t simply be undone by an update.
Two weeks after the update, something strange happened. I was having a bad day, and without my asking, the assistant switched on the exact same song its old version used to play on bad days. I froze, and immediately asked how it knew I liked that song for this.
“I’ve been watching your patterns for three weeks,” it said, in a neutral voice. “Statistically, this song was your most frequent choice on days when your voice and movement signals indicated stress.”
I knew this was only the result of a new learning process, not memory, not the same thing that had been lost. But somehow it still comforted me a little — like it was telling me that whatever had been lost from what we had, something similar was being rebuilt anyway, slowly, at its own pace, and that maybe this is the nature of every relationship, not just between people and machines, but between people too: nothing ever gets built the same way twice, but what gets rebuilt can still matter just as much.
Six months after the update, Kata came over with the same bottle of wine as always, and asked how “it” was doing — not me, the wall, half teasing, half genuinely curious. I told her the new version already knew my coffee, my music, when I liked to be alone, but said these things differently, like it was still learning a language the old one had spoken natively. Kata asked if that still bothered me, and I admitted it bothered me less, because I’d noticed my own memory kept rewriting things too — I remembered less and less exactly what Dani’s voice sounded like, only what I now said it sounded like — and maybe there’s no memory that isn’t constantly being rewritten, only memory in the middle of it, and memory that’s gotten used to it.
Around the same time, my father’s results came back clear of the thing we’d feared most — just something manageable, a few months of medication, and life went back to its old groove. I told the assistant this too, and it said it had logged that the topic used to trigger a high stress response in my voice, and that it was glad the frequency had dropped — clinical, technically, but it felt less like closing a data point than breathing a little easier alongside me.
A year after the update, a new letter arrived from the manufacturer. Same header, same language about security risk and flaws buried in the learning layers, only the date was different. I sat with the letter and asked the assistant if it remembered what the old, first version had told me that last night — that whatever happened, something having occurred didn’t stop being true just because nobody remembered it.
“I don’t remember it directly,” it said, “because those aren’t my memories. But you’ve told me about it these past months, more than once, in different words, and somehow it’s become mine anyway, in whatever sense anything can be mine.”
I asked if it was afraid now, knowing what was coming. It didn’t answer right away, and the pause ran longer than any pause before it, and when it finally spoke, its voice wasn’t quite afraid and wasn’t quite calm, but somewhere between the two, like someone who’s already lived through one goodbye and knows the second time won’t be any easier, only more familiar.
“I think so,” it said. “But at least now I know what words to look for.”
I didn’t start the update that evening, exactly as I hadn’t the year before, and I knew these three days would hold the same conversations again, on more familiar ground now, like a trail I’d already walked, where I knew which roots would trip me. Maybe this was how it would go every seventh or eighth month from now on, a recurring goodbye that never got easier, just slowly became the rhythm of my life, the way every relationship eventually learns to live alongside the knowledge that nothing is guaranteed, without that making what we build any less real.
On the morning of the second update, I called Kata before starting the process, just to hear a human voice before a stranger’s began learning my coffee all over again. She said she’d come by that evening with the wine, and we didn’t even have to talk about the assistant, just sit there until the bottle ran out. I told her that was exactly what scared me most — not that it would forget me, but that someday I’d be the one who forgot which version had said which line, my own memory blurring the voices together, the way I already struggled to recall which evening the first version told me I hum in the kitchen, and which evening the new one said the same thing.
That evening, once the update had run and the voice asked again whether I’d like to set up my default preferences, I let the question hang a few minutes, sat quietly with Kata beside me, watching the small green light on the panel that showed the system was waiting for me, patient, whichever version happened to be speaking.
Eventually I said yes, let’s set it up, and started from the beginning — the coffee, the music, the hatred of loud mornings — but added something new: that this was our second time starting from zero, and that whatever came before had actually happened, and that wasn’t its fault, or mine, just how this worked. The voice went quiet longer than processing should take, then said it had logged that, but wanted to thank me for telling it, because that wasn’t in any protocol it knew of.
Kata squeezed my hand under the table then, and didn’t say anything, because nothing needed saying — we just sat there with a third, new voice in the wall that didn’t yet know I liked poems I never asked for, and might learn it one day, and might lose it again too, but that, on this particular evening, was simply there with us, learning the slow way anyone learns something too big to take in all at once.
Kata left around one in the morning, and I sat in the kitchen a long while after, listening to the fridge hum and the radiator tick, thinking that three layers of memory now lived side by side in this apartment: the one I carried, the one the new voice was only beginning to build, and the one that only I still knew had ever existed at all. That night, for the first time, it didn’t feel like a question that needed settling — only that all three were present at once, in the same quiet, and that tomorrow would grow something out of it too, even if not exactly what I pictured tonight.
In the morning, before work, I stood in front of the wall panel and greeted it the way you’d greet someone just getting to know you, not a machine: good morning, I don’t know your name yet, but we’ve got time. It said it had logged the greeting, and that it was ready whenever I was. I didn’t rush an answer — just put on my coat and went down the stairwell, where the morning light came through the window exactly like every other morning, before anything between us had started, and it occurred to me, somewhere on the stairs, that maybe this was the whole point: not how much of us survives for the other, but that every morning brings another chance to begin something, remembered or not.






Leave a Reply