Three days since she saw the dashboard. She has been waiting for something to happen as a result — an email from Data Operations, a notification from Alexei's assistant about an urgent meeting, anything that would suggest the information is moving. Nothing has moved. The number 8.71 terabytes sits in her head the way a badly parsed clause sits: not resolved, not dismissed, just running.
Legal sits on the same floor as the NLP lab, past the Prometheus conference room and two sets of glass-walled offices. The corridor between them is the same as every corridor in the building — the Hearthstone logo above the reception alcove, the corporate blue they selected because it tests well for trust, the motivational signage whose text she has memorized and can no longer read without noting the rhetorical structure. She reads everything this way. She built the eye that does this.
Vera's office is visible through the glass before Nadia reaches the door. Vera is on the phone, one hand holding the handset and the other flat on the desk, the posture of someone delivering a position rather than receiving one. The framed credentials on the wall behind her are positioned to be seen from the corridor: Cambridge (undergraduate), Columbia Law, the bar admission certificates. The legal library fills the opposite wall. The spines are worn. Vera reads the things she cites; Nadia knows this, has noticed the specificity of her citations in every meeting where they've shared a room. The library is not performance.
The phone call ends. Vera sets the handset down, looks up, and sees Nadia in the corridor before Nadia has decided to open the door. She doesn't look surprised. Inside, the glass door seals out the ambient noise — the hum of the associates at their stations, the low register of a building occupied by forty-five people doing quiet work. The quiet here is different: deliberate, managed, the silence of a space where language is produced rather than exchanged.
"You saw the dashboard," Vera says.
Nadia stops two steps inside. She'd constructed an opening on the walk over — a question framed as curiosity, something indirect, a way of approaching the subject without naming it first. Vera's sentence removes the approach.
"The Data Operations terminal," Nadia says. "Someone left it logged in on Tuesday. I was going to—"
"I know." Vera's tone is even, the tone of someone who has heard the testimony before. "You've been processing it for three days."
"You've always known the scale."
"Yes." She doesn't add anything to this. She lets the word sit in the room and occupy whatever space it needs.
"You knew what I was writing." The sentence comes out different from how Nadia intended — not accusatory, almost wondering. The asymmetry of it: Nadia writing language she understood in the abstract, Vera watching the yield. "When I was in the drafting sessions — arguing about 'experiential' versus 'sensory,' about coverage thresholds — you knew what the difference would produce."
Vera looks at her the way lawyers look at witnesses: receiving, not interpreting. Her hands are flat on the desk now, both of them. "What did you think the language was for?" she asks.
The question has the structure of genuine curiosity. Nadia had prepared for defenses, for justifications, for the legal framework Vera is always ready to deploy. She had not prepared for Vera actually asking.
She had thought she was optimizing user engagement language. She had thought she was writing better, more precise legal terminology. She had thought she was solving compression problems — how to achieve broad coverage with minimal linguistic friction, how to write in a register that moved past the eye without snagging. She had thought the craft was the point. She had thought many things.
"I understood what the mechanism did," Nadia says. "I understood it in the abstract."
"That's what I thought," Vera says. There is nothing in her voice that marks this as a criticism. Nadia takes the chair across from Vera's desk without being offered it. It is lower than the desk chair by the standard negotiation-room differential — not enough to register consciously in most people, enough to work. She registers it and sets it aside.
"The consent is documented," Vera says. "The terms are explicit. Section 4.2 — your language — uses phrasing that any competent reader would understand as granting a license to experiential data. We are not responsible for users who choose not to read."
"We wrote 47,000 words."
"We wrote a comprehensive agreement."
"We wrote 47,000 words to ensure nobody would read them." The sentence is out before Nadia decides to say it, but she doesn't walk it back. She has been thinking about this for three days — not just the scale of what the dashboard showed, but what the scale implies about intent. You do not write 47,000 words because you need to disclose that much. You write 47,000 words because length produces exhaustion and exhaustion produces compliance. Because a scroll bar that never seems to reach the bottom trains the eye to stop expecting to reach the bottom. Because 47,000 words of legal register in a nine-point font is a document that displays the words I accept while meaning I did not read and I am consenting to something I cannot name. "The length is an argument," she says. "The inaccessibility is the consent mechanism. We chose the length. We chose the font size. We chose to put Section 4.2 on page forty-nine, after fourteen sections on account creation and payment terms that users actually care about. We designed the placement. We designed the skip."
Vera is quiet for a moment. "We designed for the world as it exists," she says. "The world is one in which users commonly do not read ToS agreements. This is documented and universally accepted in the industry."
"We designed for those norms. That's different from accepting them."
"Is it?" Vera's voice has the quality of a person who has had this argument before and found it unresolved — not challenging Nadia's position, but noting the contested terrain. "The user had access to the terms. The terms were explicit. The user had the option to engage with them. At what point does designing for human behavior — ordinary, predictable, documented human behavior — become designing against the human being behaving?"
This is why Vera is good at her job. The question is not rhetorical. She is asking it the way she asks questions in depositions: because she wants to hear the answer, because the answer might complicate something, because she does not hide from the complicated things.
"When the design uses the behavior against the person," Nadia says. "When you write the length to prevent reading rather than to achieve comprehensiveness. When Section 4.2 is on page forty-nine because you know the eye won't reach page forty-nine. We did not put it there because forty-nine pages of context was necessary. We put it there because exhaustion is the mechanism."
She hears the defiance in her own sentences and does not moderate it. This is the thing she could not say in the drafting meetings, could not say in the all-hands reviews, could not say in the three days since the dashboard — named now, between walls, in the quiet where language is produced.
Vera's expression doesn't change. She has the kind of face that maintains its register across a wide range of incoming information — not coldness but practice, the practiced surface of a person who has had this argument with herself, resolved it on her own grounds, and is not going to un-resolve it because someone else is having the argument now.
"You want me to say it's wrong," she says. "I understand that impulse. But wrong and illegal are not the same thing, and neither of us built our careers on feelings."
The parallel construction registers first: wrong and illegal, not the same thing. The implicit argument: legal is the operative category, wrong is a category for contexts in which legal doesn't apply. The word feelings doing the work of reclassification — converting her argument about design intent into an emotional state, categorizing it as arising from somewhere other than analysis. A move she knows, has used, has watched people use to end conversations that they cannot continue on the merits.
She has no legal counter. She knows this. The consent is documented. The terms are explicit. The user had the option to read. These are true. The framework that contains them is coherent and Vera knows how to hold it.
Her counter is her mother's voice forming the word azizam — the shape of that a, the way her mother's mouth weighted the middle syllable when she meant it as both name and reassurance. Her counter is 8.71 terabytes of that, catalogued, licensed, filed under a subsection she wrote in forty minutes and was pleased with for its compression. Her counter is the recognition that it is possible to document consent to something whose cost cannot be understood until the cost is already paid — and that designing a system to ensure the cost won't be visible until after payment is complete is not a neutral act that lives in the space between wrong and illegal. It is a choice. She made it. Vera defended it.
She does not say this.
She sits in the lower chair and looks at Vera and Vera looks back and neither of them moves. "All right," Nadia says.
She stands. The conversation has arrived at its limit, the point where two clearly articulated positions have been exchanged and there is nothing left to say that would change either of them. Nadia knows where Vera stands. Vera knows, or suspects, where Nadia is going. In legal terms those two things are equivalent.
"Nadia." Vera's voice shifts — not much, a degree of adjustment in cadence, the lowering that distinguishes personal from professional without crossing into warmth or warning. "I need you to hear this as your colleague. Not as counsel." Nadia stops but does not sit back down.
"If you act on this — whatever you're thinking about doing — you're not just implicating yourself." Vera pauses — the calibrated silence of someone selecting the right unit, which Nadia recognizes because she does it herself. "Every person who contributed to the framework is part of this. The NLP team. Product. Every person who drafted, reviewed, approved, or deployed the ToS in the last four years. For all of us." The second pause is shorter. "Think about that."
Nadia thinks about it — and the warning is also a disclosure. Vera has just told her, in the careful language of someone who measures every syllable she speaks professionally, that the framework Vera has defended as legally airtight is something Vera is also inside. Not standing at a distance from it, citing it from the outside. Inside it. Protected by it. If the framework becomes indefensible, Vera is not the brilliant lawyer who constructed comprehensive consent architecture. She is the other thing, and she knows what that would be called.
Nadia looks at her. There is something in Vera's expression she has not seen there before — not doubt, but the thing that occupies the same register as doubt and dresses like certainty in the morning. The look they have exchanged across rooms. Shared knowledge, diverging responses. The gap between them is not that one sees what the other doesn't. They see the same thing. The gap is what they have decided to do with it.
"Thank you," Nadia says. The words carry their content and nothing else. She walks through the glass door and pulls it closed behind her — the associates do not look up — and at the end of the corridor the elevator is waiting.
The doors close on the Prometheus logo above the call panel, corporate blue, the same blue as the Hearthstone Accept button, the same blue as the Memory Wellness Score interface, the same blue as everything in this building that means something it does not say. She reaches for the Farsi.
The daily inventory: the a in azizam, how her mother stressed the middle syllable when she meant it as both name and reassurance. Doostet daram with its long stretched middle, the breath under it when she meant it emphatically. The phonemes, the register, the weight of the language when it was spoken in love rather than in grammar, in a house that otherwise spoke English, in the hours before the vocabulary itself became something she studied rather than something she carried.
It is there. It is fainter.
She cannot tell whether the faintness is today or accumulation — she has had days where the reach required more effort, days where the inventory felt thinner, and she has told herself this is just variation, just forgetting, the way all memories shift when you are not sleeping enough, when you are processing something else. But today the faintness is specific. The vocabulary is intact. The grammar is intact. The conjugations hold, she can still diagram a sentence in her mother's language, can still move through the structure of it. What is fainter is the thing below the structure — not the content of the voice but the acoustic quality that made the Farsi her mother's Farsi and not the Farsi she learned from dictionaries or the Farsi spoken by other people's mothers. The experience of her mother speaking, as opposed to the fact of her mother having spoken.
She holds what she can find of it. It is like holding water — not the glass, not the fact of water, but the water itself, which is still there and yet is not exactly the water that was there this morning, because water moves and memory, she understands now, moves in the same way: you do not hold a fixed thing, you hold a current, and the current is always redirecting itself, and you do not discover that it has changed direction until you are already somewhere downstream. The elevator descends. 12. 11. 10. She does not reach for the memory again. She already knows what she will find.
The lobby opens around her — the security desk, the guard on his phone, the glass revolving door, the afternoon beyond. She pushes through. The air outside has a chill in it, October settling into November, and somewhere down the block a food cart has something spiced working, but she passes it and the smell is just a fact of the block, not a thing that reaches her, not a thing she carries.
She walks. The Farsi walks with her, faint and present, or present and faint, which is beginning to feel like the same thing.
PROMETHEUS DIGITAL LLC CONFIDENTIAL — ATTORNEY-CLIENT PRIVILEGED COMMUNICATION
MEMORANDUM
TO: Executive Leadership Team FROM: Legal Department, Office of the General Counsel RE: Annual Compliance Review — Hearthstone User Agreement (v4.7) DATE: September 2024
Pursuant to the Legal Department's standard compliance review schedule, this memorandum confirms the findings of our annual assessment of the Hearthstone Terms of Service, all amendments through and including v4.7, and associated Exhibit A materials.
Compliance Assessment: All Hearthstone user agreements, including the current Terms of Service and all amendments thereto, comply with applicable federal, state, and international regulatory frameworks. The documented consent structure — including clickwrap acceptance mechanisms, amendment notification procedures, and continued-use acceptance provisions under Section 5.1 — meets or exceeds current industry standards for informed consent.
Section 4.2 (Licensed Content): The defined scope of Licensed Content under Section 4.2, including Subsection 4.2(c) and the recently added Subsection 4.2(d) (Ambient Experiential Associations), is legally defensible under current regulatory frameworks. User consent to the defined scope is documented and enforceable.
Litigation Exposure: No material litigation exposure has been identified. The mandatory arbitration clause (Section 8.1) and class action waiver remain in effect. Individual plaintiff risk is assessed as low. No coordinated plaintiff activity has been identified at this time.
No modifications to the current user agreement are required.
V. Osei, General Counsel Prometheus Digital LLC