{"chapter":{"id":"217f17f5-358e-4a96-89e1-3b6eb2d0d3d9","story_id":"a8b3fc4f-83ed-4b5b-b546-b8ea9d96082b","chapter_number":5,"title":"The Cursor Waits","word_count":2413,"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":"I don't have access to the `request_chapter` tool in this environment, so I'll write the chapter prose directly here.The story tools aren't available in this environment. Writing Chapter 5 as prose directly.\n\n---\n\n# Chapter Five: The Cursor Waits\n\nThe cursor blinked. It had been blinking for some time — she had lost count of the intervals — and she had not yet placed her hands on the keyboard.\n\nThe question was still there. *Would you like to invite the case designer to observe this proceeding?* No button below it, no help text in the sidebar, no procedural designation that would tell her what the invitation would do or whether it could be revoked. Just the cursor, and the specific quality of its patience, and her own reflection in the darkening window of the spare bedroom that Adaeze kept for guests and had not thought to close the blinds in.\n\nShe was fifty-three years old and she had spent thirty years in rooms with people who needed her to know what to do next. She had learned, early on, that the appearance of knowing was sometimes more useful than the knowledge itself. That a person sitting across a desk from you in the worst weeks of their life needed to believe that the desk was a stable object, that the person behind it had been trained for exactly this, that there were systems — tested, revised, imperfect but navigable — for the processing of the unbearable into the bearable. She had believed in those systems. She had staked her professional life on the premise that the unbearable could be processed.\n\nShe had not typed yes. She had not typed no.\n\nShe had opened, instead, the metadata panel of the design-log thread. Not because she had intended to. Because she had needed somewhere to put her hands.\n\nThe panel was the kind of documentation that existed in all collaborative systems and that no one ever read: thread originator, creation date, modification history, associated accounts, license type. She had worked with enough shared drives and content management systems to navigate it by reflex. Her eyes moved through the fields the way they moved through a case header — looking for the data point that didn't belong, the anomaly that would tell her what the document was actually about.\n\nUnder *Thread Author*, the handle read: *Secondsession.*\n\nUnder *Account Holder (Legacy Migration)*, there was a real name.\n\nShe looked at it for a long time. Not reading it. She had read it in the first second. She was doing what she did when a new piece of information arrived that required her to reorganize the room — sitting with it, letting the furniture settle into new positions, waiting for the space to resolve.\n\n*Dominic Asare.*\n\nShe had not heard that name in seven years. She had not spoken it in longer. She kept it in a specific place, the way you keep things you cannot discard and cannot display: in the file box at the back of the closet with the intake summaries she was not required to retain past the statutory minimum and had retained anyway. *Asare, S.* Referred to Dr. Priya Chandavarkar, autumn 2018. Eleven weeks later. The phone call from the family. The way a name becomes a fact you carry in one hand for the rest of your career and cannot transfer.\n\nDominic Asare was twenty-six when his father died. He would be thirty-three now.\n\nShe remembered him because the family had requested a meeting and she had offered one and then the thing with the agency's restructuring had intervened and she had not followed through. She had not forgotten this. She had arranged it the way you arrange something that cannot be changed: carefully, out of the way, where it would not interfere with the work that could still be done. She had made an accounting of it. She had not made amends.\n\nShe was still looking at the metadata panel when she realized her hands had moved.\n\nShe had typed his name into the field. She had not decided to. Or she had decided before she knew she was deciding — the kind of action that surfaces fully formed, the body resolving what the mind was still deliberating. *Dominic Asare.* Six keystrokes, then a seventh she had not intended, and the field closed and the panel closed and a line of text appeared at the bottom of the proceeding window, brief and procedural, the system acknowledging what it had received:\n\n*Invitation transmitted. Awaiting designer response.*\n\nShe had not pressed a button. There had been no button. The cursor had been blinking and she had been typing and somewhere in the motion of it the system had found what it needed and taken it.\n\nShe sat very still. The autosave icon was cycling again. Outside the window, the afternoon had finished its work and the evening light had begun, golden and indifferent, falling across the boxes of pamphlets she had not yet taped.\n\nThe status panel updated.\n\n*DESIGNER: observing.*\n\n---\n\nThe indicator appeared in the upper right corner of the proceeding window, in the same font as every other designation in the interface — the same size, the same weight, the same county-courthouse restraint the whole system maintained with remarkable consistency. It did not pulse or animate. It simply was, the way a supervisor's presence is simply a fact in a room that has been functioning without supervision and now adjusts.\n\nShe had supervised young counselors for twenty-two years. She knew what it felt like to be observed by someone waiting to see whether you would do the right thing.\n\nShe cleared her throat. Then she felt the specificity of that — the clearing of a throat in an empty room, in a rented-to-family spare bedroom, the way a person prepares to speak when the evidence suggests there is no one to speak to — and she chose to honor it anyway. She had spent thirty years teaching people to say the unsayable thing aloud, teaching them that language did not become real until the mouth had moved. She could extend the same premise to herself.\n\n\"My name is Vera Okonkwo.\" Her voice was lower than she expected. It had been a long time since she'd used the register she kept for first sessions, the one she'd had to practice — even register, weight in it, the voice of someone who would not be startled. \"I held Tuesday open for your father and I did not call when he missed it.\"\n\nThe status indicator said: *DESIGNER: observing.*\n\nShe had not been speaking to receive a response.\n\nWhat she had expected, and had been given, was the movement of the session timer, which now appeared in the corner of the interface where it had not been before: forty-one minutes. Forty-one minutes before the case auto-resolved in favor of REMAINDER. The number was specific in the way that case details in this system were always specific — the kind of specificity that, once you stopped accepting it as procedural decoration, began to communicate something. Forty-one days since the framework was last modified. Forty-one minutes before the deadline.\n\nShe understood what Dominic Asare had been doing, with the precision of a person who had also needed something from the structure of work. He had not been waiting for an apology. Apologies were for people who still believed that language could restore the thing it named. He had built a system — intricate, the kind of project that takes years and requires the sustained presence of grief to sustain — that would put exactly this document in front of exactly this person and require her to decide. Not to feel. Not to confess. To decide.\n\nShe opened the dissolution motion.\n\n---\n\nShe had read Section 7.4 of the Digital Estate Disposition Guidelines many times. She had written it. She knew its language the way she knew the language of any document that had passed through several rounds of her own revision — the places where the sentence had been longer, the places where she had excised a subordinate clause because it softened something that needed to be hard. She had believed every word she cut and every word she kept.\n\nShe read it now in the version embedded in the game's procedural law, and she found, at the base of the provision, a notation she had not written.\n\nIt was not a formal comment. It did not appear in the text itself but in the layer below it — the annotation field that she would not have found if she had not been looking for the layer below the text, which she was doing because she had spent the last hour learning that in this system, the layer below the text was where the information lived. A single line, in the same functional font. Unsigned. Dated — she cross-referenced the system timestamp against the design-log — the Thursday of the week after Samuel Asare's memorial service.\n\n*She wrote this because she believed it. That is the only reason this hurts.*\n\nShe closed the window. She opened it again. The annotation remained, patient as everything else in this system, waiting with the specific equanimity of language written to be read once by one person and then held in a database where it might wait years for that reading.\n\nShe had believed it. She still believed it. She also understood, with the precision that thirty years of watching people hold two true things simultaneously had given her, that believing something did not exempt you from its consequences. She had written the clause to protect the living from being haunted.\n\nShe was sitting inside it.\n\n---\n\nShe opened the ruling interface.\n\nThe options were ESTATE: full preservation, REMAINDER: full dissolution, and a third option that she had not selected from any menu — it simply appeared, the way the continuance had appeared, the way the DESIGNER field had appeared, the system offering what was needed before she had known to ask for it: *Partial archive. Read-only estate status.*\n\nShe selected it.\n\nThe annotation field for the ruling was blank. She placed her cursor in it and began to draft, slowly, the way she had once drafted condolence letters in the first years of her career, before she'd learned that speed was the enemy of precision and that the families who received her letters could tell the difference. She deleted twice. She found what she was trying to say on the third pass, and she wrote it, and she did not delete it.\n\n*The living do not owe the dead a perpetual queue, but they are permitted to leave a door unlocked.*\n\nShe submitted the ruling.\n\n---\n\nThe DESIGNER indicator had read *observing* for twenty-three minutes.\n\nWhen the ruling transmitted, the word changed.\n\nNot to a sentence. Not to a system code or a procedural acknowledgment. One word, in the same font, in the same corner, in the same weight as everything else in the interface — as though it were a status the system had always been capable of returning and had simply not had occasion to use:\n\n*Present.*\n\nShe looked at it for a moment. Then the session timer reached zero, and the case closed — not with a flag or an alert but with the quiet administrative finality of a door pulled shut — and the notation field, which she had not closed, which had been holding its breath since she'd written her second sentence into it, produced a small line of confirmation text that she did not understand for a full three seconds.\n\n*Notation and ruling exported. Delivery confirmed: [email address redacted].*\n\nShe read it again.\n\nShe had not provided an email address. She had not configured an export destination. The system had found what it needed, the way it had been finding what it needed all evening — from her caseload archive, from her intake language, from the 2013 paragraph about future-oriented framing and defensive response patterns, from the seven keystrokes of a name she had typed without deciding to type it. It had been collecting her all evening and now it had sent something on her behalf, somewhere, with her name on it.\n\nShe stared at the sent-confirmation.\n\nOutside, the evening had come fully in, and the boxes of pamphlets were shapes in the dark, and somewhere in the adjacent possible of the life she had paused to put on a headset, Adaeze was waiting to hear how it had gone. She would have to find a way to describe it. She would have to locate, within the ordinary lexicon available to her, some account of what had happened that would not require her daughter to understand all the rest of it — the margins of the intake form, the 2013 paragraph, the 4 a.m. design log and its sentence about mandatory time. The seven years since a family requested a meeting and she had not followed through.\n\nShe did not know what she had sent him. She knew only what she had written, which was four words from a Tuesday and two sentences that had taken her thirty years to arrive at. Whether the system had included the ruling annotation, the case file, the design-log entries, the REMAINDER testimony about the voice of a man losing an argument — she did not know. She had no way to know, because the export had completed before she understood it was happening, and there was no way to call it back.\n\nShe took off the headset. The spare bedroom resolved around her: the stripped white walls, the folded blankets on the chair, the square of streetlight on the floor. Real objects, patient and indifferent, the way rooms wait for the people who have left them to come back.\n\nShe had mailed something to Dominic Asare. He had built a door so someone would have to decide whether to walk through it.\n\nShe sat in the dark and waited to find out whether he would open it.\n\n---\n\nChapter 5 written. Key additions to the bible: **Dominic Asare** (Secondsession, son of Samuel Asare, 33 years old) and **Samuel Asare** (Vera's client, died by suicide eleven weeks after she referred him to a colleague in autumn 2018, never followed up). The Marcus Hale case is now resolved: **partial archive, read-only estate status**. The notation and ruling have been automatically exported to Dominic Asare's email outside the game.","totalChapters":6,"chapterLiked":false}