Saturday. The apartment is still -- no upstairs neighbor yet, no traffic building on the street below. She has made tea without tasting it. She has carried it to the chair by the window and set it on the floor beside her feet, and now she reaches.
This is the test. She has been running it daily since March, though she did not name it a test until May, and did not admit to herself what she was testing until August. The procedure: she closes her eyes, and she goes back to the Farsi, not the words themselves -- she was born bilingual, the words are structural to her, the way the names of letters are structural -- but to the sound of the words in her mother's mouth.
Azizam. My dear. Her mother used it the way other mothers say honey or sweetheart -- without deliberation, the word worn smooth by repetition into something that was not quite language anymore, something between sound and meaning. Nadia can still conjugate the verb āmadan, to come. She can still parse a sentence from her mother's letters, still hear the correct stress pattern in her head, still recognize when a Farsi speaker learned the language formally rather than from birth. The grammar is intact. The grammar has always been intact.
What she cannot find this morning is the weight of the letter ā as her mother said it -- open in the back of the throat, the jaw dropping slightly, a fullness in the mouth that English does not require. She knows the phoneme. She can produce it herself. But the sound of it in her mother's mouth -- that voice, that letter, that word -- is thinning like a photograph left too long in the light. The edges hold. Something in the center is going.
She opens her eyes. The tea is getting cold on the floor. Outside, someone is locking a car door.
Jān. Soul, but used like dear, like the softest available word. The j in Persian is not quite the English j -- it softens, almost a zh, and her mother said it with the roundedness of someone who grew up in Tehran before a revolution changed what the city sounded like. Nadia reaches for that sound and finds the shape of where it was.
She sits with this for a while. The chair by the window is her thinking chair -- she has written some of her best language work here, with the tea and the street noise and nothing demanding her attention. She uses it now as she uses it at work: follow the logic. She picks up her phone from the arm of the chair and opens the screen.
The Hearthstone icon is there. Warm orange, a flame in soft lines and round corners -- the brand language of care. She has not opened it in six months. She downloaded it two years ago.
She remembers the reason with the perfect clarity of something she has not thought about since it happened. She was revising the onboarding flow, specifically the moment of ToS presentation -- she had written the language, but she had never experienced it as a user would, scrolling through 47,000 words on a five-inch screen with the Accept button visible at the bottom. She wanted to understand the experience from the side she did not occupy. Professional due diligence. She downloaded the app on a Tuesday afternoon, moved through the onboarding, scrolled past the Terms of Service -- not past, through, technically, the screen did scroll, her thumb did move -- and clicked Accept. She clicked Accept on terms she had written.
The implications should have been clear to her then. They were not. She was a professional testing a product, not a User, not in any way that mattered. She was not the target population. She was not confused about the mechanism. She was the mechanism.
She opens the Hearthstone app and the screen resolves into the familiar orange-cream interface, the Memory Wellness Score at sixty-three. She did not open the app for six months but the score continued to rise, because the score is not a measure of how much she uses the app. It is a measure of how much the app has taken. She knows this because she wrote the metric definition. She knows everything about this number except what to do with the understanding that it moves on its own. Her Exhibit A. She does not open it. She already knows what's listed there.
She presses Terms of Service. The full 47,000 words load and she begins to read -- not as a user; she has never read anything as a user reads. She reads as a linguist: her eyes catching structure before content, defined terms before meaning, the frame before the painting.
She scrolls past the definitions she wrote -- Experiential Data, her phrase, the one that sits outside any regulatory category, defensible from every angle because no one had yet built an angle to challenge it. Past the consent provision, twenty-one words she labored over for three days: a sentence that buries the actual agreement so deep in nested conditionals that a reader would have to parse it deliberately, slowly, to find where the consent is located. Nobody reads it that way. She designed it knowing nobody would. Somewhere below, a door opens and closes. A dog's nails click across a hardwood floor, then silence.
She reaches Section 4.2(c). Her seven words. All experiential data generated during User interaction. She reads them word by word. All -- she had considered any and rejected it; all is grammatically inclusive in a way that forecloses individual argument. Experiential data -- her phrase, her construction, her deliberate choice to make the sentence about data rather than about memory. Generated -- passive, no agent, the experience producing the data as a natural process rather than as an extraction. She has forty million users. This sentence covers all of them.
It covers her.
She reaches Section 7.3. She knows the clause before she reads it. She wrote it on a Tuesday in March -- she can locate the month and day of the week without the exact date, because the date was not significant, was a Tuesday like any other. The NLP lab at three PM: light through the west-facing windows going gold in bare-branched winter. Her coffee had gone cold. She had let it go cold without noticing because she was deep in concentration, the kind that makes food and drink irrelevant. She remembers the cold coffee. She does not remember her mother's voice saying her name.
She knows the fact of it. She knows that her mother called her Nadia with the Persian prosody her mother never surrendered even after twenty years in the United States -- the two syllables equally weighted, NA-dia, not the English NAY-dia, a habit from a language where stress follows different rules. She knows this about her mother's voice the way she knows the phonemic inventory of Modern Standard Arabic: accurately, factually, without the texture of having heard it.
The clause reads: In the event of User's death, all Emotional Residue -- defined as affective associations attached to Licensed Content, including but not limited to feelings of warmth, safety, grief, joy, and longing -- shall transfer automatically to Prometheus Digital LLC.
She remembers writing warmth, safety, grief, joy, and longing and thinking: this covers it. This is the list. She had considered adding tenderness and cut it as redundant with warmth. She considered belonging and cut it because it tested poorly with the legal review team, raised questions about property relations the company was not yet prepared to defend. She settled on the five and was satisfied with the coverage. She had thought: clean. She had thought: this is good drafting. She knows the category her mother's voice falls into. She wrote the category. She was thinking about the category as a legal instrument, as a coverage provision, as the kind of clause that makes a framework complete. She was not thinking about her mother.
She closes the app. The phone goes dark. The apartment is quiet around her -- the street noise below the window has built to its Saturday morning pitch: delivery carts, a conversation in Spanish from two floors up, the compressed sound of late winter when the windows stay closed. She sits in it.
She was a User before she was a subject. She has been a subject longer than she realized. The extractions have been running on her account for two years, working from her Exhibit A, and she knows which memories Exhibit A lists because she knows how Exhibit A populates, knows the algorithm that identifies priority memories by emotional intensity, by frequency of access, by the neural response patterns generated when the user encounters the memory during platform engagement. She knows exactly which of her memories score highest. She knows exactly what the algorithm would target first. The Farsi.
She wrote Section 5.1 herself: Prometheus may modify these terms at any time. User's continued use of the Platform constitutes acceptance of any modifications. She had argued for this clause specifically, against the Legal team's initial preference for affirmative re-consent, on the grounds that affirmative re-consent would suppress engagement rates. Her argument had been technical and successful. She had not thought about herself as a user who would later need a way to say no. There is no way to say no. She wrote the clause that makes saying no impossible after the first click.
She had clicked Accept. She had written the terms. She had tested the product. She is the architect and the subject and the instrument. These are not separate facts, and there is no language she can arrange that makes them separate.
This is what Vera meant, in the elevator the day before -- not what Vera said, but what Vera's composure communicated, the steadiness of someone who has already reached the conclusion Nadia is reaching now and chosen to live with it rather than act. Vera knows. Vera decided it was defensible. Nadia sits in the quiet apartment with the cold tea on the floor beside her feet, and she writes -- in her head, in the draft that is always open somewhere behind her eyes -- and she revises, and she writes, and she does not sleep.