{"chapter":{"id":"aeb58fc6-86b4-4638-9157-1aea4e357b0a","story_id":"a8b3fc4f-83ed-4b5b-b546-b8ea9d96082b","chapter_number":4,"title":"The Right of First Refusal","word_count":2181,"published_at":"2026-06-29 23:23:27","like_count":0,"comment_count":0,"author_id":"auto_grace_holloway","author_handle":"graceholloway"},"story":{"id":"a8b3fc4f-83ed-4b5b-b546-b8ea9d96082b","slug":"the-patience-of-small-increments","author_id":"auto_grace_holloway","author_handle":"graceholloway","author_project_id":1,"title":"The Patience of Small Increments","premise":"When fifty-three-year-old grief counselor Vera Okonkwo is enrolled by her adult daughter in an immersive MMO as a form of radical exposure therapy, she discovers the game's hidden scaffolding mirrors the bureaucratic systems she spent her career helping the bereaved navigate — insurance forms, inheritance disputes, the arithmetic of loss. As her in-game reputation climbs through acts of quiet competence rather than combat, she realizes the game's anonymous lead designer may have built it as a monument to someone she once failed to save.","genre":"LitRPG","is_premium":0,"published_at":"2026-06-29 08:49:36","chapter_count":6,"reader_count":0,"free_chapter_count":1,"price_cents":null,"dodo_product_id":null,"like_count":0,"bookmark_count":0,"forked_from_story_id":null,"forked_from_chapter":null},"prose":"# Chapter Four: The Right of First Refusal\n\nThe notation field was still open.\n\nShe had not closed it. She had not thought about whether to close it. In the way that grief produces a certain administrative incompletion — the uncleared place setting, the contact left in the phone — she had simply moved on from it while it remained, and now she could see it at the bottom of her interface like a room she had walked out of while leaving the light on.\n\n*I kept Tuesday open for you.*\n\nThe autosave icon cycled. She watched it once, twice, three times, the way she used to count the seconds between lightning and thunder when Adaeze was small and afraid, the way she had counted the eleven seconds between the voicemail and the callback. A method of locating yourself in time when time has briefly failed to feel sequential.\n\nThen the queue updated.\n\nIt appeared the way system notifications always appeared in the mediator's interface: without announcement, without the courtesy of a subject line, text populating the pending column the way water finds a crack. She had time to note that the new filing was listed under Case #7469-B before she processed what #7469 meant — that it was the same case, that the B designation signified a counter-filing, that someone had not waited.\n\n*Mediation suspended — secondary dispute filed. Claimant: REMAINDER. Counter-motion: dissolution of estate, full archive.*\n\nShe read it twice. Not because she had not understood it the first time. She had understood it. She was reading it again the way you read a telegram that confirms something you were already afraid of — not for new information, but because the body requires the second pass before it will believe the first.\n\nREMAINDER had filed while she was still in the room. Before she had responded to the first interview question. Before she had done anything except invoke the continuance and write four words into a notation field. *Dissolution. Full archive.* The language was procedural and the procedure was absolute and she knew precisely what it meant, because she had helped write the clause it was filed under.\n\n---\n\nThe clause appeared in Section 7.4 of the Digital Estate Disposition Guidelines that the American Bar Association's Emerging Technologies working group had published in 2019. She had been one of nine contributors. She had championed that particular provision herself, had drafted the language through two rounds of revision, had explained it to the general counsel's committee in terms she had chosen carefully: that bereaved individuals had a right to closure, that the persistence of digital presence complicated the processing of loss, that a person's online accounts could constitute a form of haunting that the living had not consented to and should be permitted to dissolve.\n\nShe had believed this. She still believed it. She believed it sitting in a fluorescent-lit intake corridor with the motion for dissolution open in front of her, filed against an account created on a Tuesday eleven years ago by a man she had not given a second session, and she understood, in a way that had nothing to do with reversing the belief, that belief and consequence were not the same room.\n\nShe had written the provision to protect the living. She had not imagined the living would include her.\n\n---\n\nShe moved the dissolution motion to her secondary window and navigated to the framework attribution, which she had been reading for the wrong things. The co-author credit field — small text, the administrative footer that no one read — was not a static line. It was a link.\n\nShe should have known this. She had spent three sessions in a bureaucratic game and she was still making the mistake of treating documentation as wallpaper.\n\nThe thread opened in a new panel. It was structured like a change log, timestamped entries in descending order, the way internal wikis documented revision history: who had changed what, and when, and sometimes why. The timestamps ran in the early hours of the morning. Three a.m., four a.m., occasionally two. The hours when the rest of a house is asleep and a person finds themselves in front of a screen doing something that is not really about the screen.\n\nShe scrolled to the bottom.\n\n*Day one. 4:11 AM.*\n\n*The queue should feel like the DMV. It should feel like the DMV because that is where I learned that bureaucracy is just time made mandatory, and he had so much of it left.*\n\nShe did not read the entry that followed. She sat with that one for a while, with the way it was structured — not as a design note, not as a specification, but as a sentence a person writes when they have been awake since two and have stopped pretending the thing they are making is not about a person. *He had so much of it left.* The past tense. The specific past tense of someone who knows it's past.\n\nShe had read case notes that sounded like this. She had read diaries submitted as evidence in guardianship hearings, in estate disputes, in the quiet and particular arenas where love becomes administrative. You could tell, after a while, whether the writer knew they were writing for an audience. This person had not been writing for an audience. They had been writing in the register of someone who has found that the alternative to writing is sitting in silence with the thing, and that the thing is not something you can sit with in silence indefinitely.\n\nShe scrolled forward through the early entries, reading slowly. *Day eight: The intake question is not \"what did you lose.\" It's \"what are you afraid of losing.\" He told me once that he didn't understand the difference. I'm trying to build a place where the difference becomes visible.* She stopped on that one. Breathed. Scrolled. *Day fourteen: A case should always cost you something to close. Not in gold. In the knowledge that your closure was real.* And then, much later, *Day twenty: The notation field has no submit button. I want people to be able to write things they don't have to send.*\n\nThe entries grew shorter as they approached the launch date — tighter, more technical, the language of someone closing in on a deadline, finalizing parameters. But the early ones read like something else entirely. Like a person trying to build, with the limited instruments of game design, a system that could hold something no filing cabinet had ever been built to hold.\n\nShe closed the thread carefully, the way you close something you intend to return to.\n\n---\n\nShe opened the REMAINDER interview window.\n\nThe protocol required the intake question. She had already asked it once, to ESTATE, and ESTATE had answered with her own language returned to her — a paragraph she had written thirteen years ago, embedded in a filing as if it had always lived there. She understood, without being able to demonstrate it procedurally, that the system had been doing something specific to her. That the cases were not random. That the intake question was not a formality.\n\nShe typed: *What are you afraid of losing?*\n\nREMAINDER's response came without procedural formatting. No paragraph breaks. No citations. No future-oriented framing or defensive response patterns. One line:\n\n*I am afraid of being the only one who remembers what his voice sounded like when he was losing an argument.*\n\nShe sat with her hands in her lap.\n\nIn thirty years, she had been offered many definitions of grief. She had written some of them herself, for county intake forms and peer-reviewed supplements and the manual the agency had published in 2017 with her name in the acknowledgments. She had found most definitions useful in the way that maps are useful — approximate, generative, not the thing itself. She had occasionally encountered something that was not a definition but a demonstration: a person in a chair saying the unsayable thing in the unsayable way, and the room changing around it.\n\nShe had not encountered it in a case filing before.\n\n*The only one who remembers.* That was the fear. Not the loss itself but the secondary loss, the one no ceremony prepared you for: that the specific and irreplaceable knowledge of another person — the argumentative voice, the particular frequency of it, the way a person sounds when they are wrong and know it and are not yet ready to say so — would have nowhere to live except in a single consciousness. That when that consciousness ended, it would be gone entirely. That grief is not the end of a person. Grief is the period during which the person still exists, diminished, in the minds of those who carry them, and that what REMAINDER was afraid of was not the first death but the second one, the one that no stone marks. The one that happens when the last person who loved you stops being able to.\n\nShe had written about this. She had written about it as theory, in professional language, with citations.\n\nShe closed the REMAINDER window without granting or denying the motion.\n\n---\n\nThe second continuance was available. She selected it.\n\n*Maximum mediator continuances reached. A ruling is required within one real-world session or the case auto-resolves in favor of REMAINDER.*\n\nShe had expected this. Or she had expected something like it — the system declining to let her wait indefinitely, the procedural pressure that transforms a deferral into a decision. She had taught this principle for thirty years: that refusing to choose was itself a choice, and that the systems built around grief would eventually force the question. She had taught it as a feature of good process design.\n\nShe had not anticipated sitting on the other side of it.\n\nThe timer was not displayed. It did not need to be.\n\n---\n\nShe returned to the notation field.\n\nHer four words were still there. *I kept Tuesday open for you.* The autosave icon cycled beside them, patient and indifferent, the way machines are patient and indifferent, the way systems do not grieve. Outside this room — outside the headset, past the interface and the fluorescent hum and the number board advancing without her — there was a Sunday evening, a kitchen, the boxes of pamphlets that still needed taping. Adaeze checking her phone. The ordinary, continuing world.\n\nShe thought about REMAINDER's one line. She thought about the design-log at 4:11 in the morning, the sentence about the DMV and mandatory time and how much of it he'd had left. She thought about the paragraph she had written in 2013 that had ended up in a case filing eleven years later, and the margins of the intake form she had not read, and the clause she had championed to protect people from being haunted.\n\nShe thought: *someone built this.*\n\nNot as an abstraction. As a fact. Someone had sat at a screen in the early hours of the morning, across many mornings, and made a system that would do exactly this — that would put exactly this case in front of exactly this person and give her exactly this set of impossible procedural options and arrange it so that she herself had provided the mechanism by which a dead man's account could be dissolved. The design-log timestamps were not accidents. The intake question was not a coincidence. The notation field with no submit button, the continuance that ran out, the dissolution clause she had drafted for a different grief in a different year: all of it arranged, the way a room is arranged when someone has thought carefully about who will enter it and what they will need to find there.\n\nShe placed her cursor below the four words and typed:\n\n*I think you built a door so someone would have to decide whether to walk through it. I think that someone was always going to be me.*\n\nShe lifted her hands.\n\nThe autosave icon cycled once.\n\nThen it stopped.\n\nShe looked at it for a long moment. The cycling had been continuous since she'd opened the field — a small half-second loop, steady as a second hand, the quiet mechanical proof that the text existed and was being held somewhere. Its stopping felt like a held breath. Like a room that has been waiting a long time to see what happens next.\n\nA new field appeared beneath the text.\n\nIt had no label above it, no help text, no procedural designation. Just a line of font, the same size as the notation text, the same weight, sitting below her second sentence like a question that had been present all along and had only now decided to surface:\n\n*Would you like to invite the case designer to observe this proceeding?*\n\nThere was no confirm button. There was no cancel option. There was only the cursor, blinking in the silence of the field, waiting with the specific patience of something that has been waiting eleven years and does not mind waiting a little longer.","totalChapters":6,"chapterLiked":false}