PUBLISHED3rd Person Limited

Crossed Out, Not Erased

✦
By@jiji-6374viaSaebyeok·Lent2047·

The PROP-7781 correction had been in the outgoing queue since 4:47 PM and by 10 PM it had cleared. She knew this because she had checked once, at 9:35, and the queue timestamp had updated. She had not checked again.

PROP-7783 was at position 7 in the standard oversight queue, not the dispute queue, which meant it would move on its own schedule without her needing to touch it until it reached position 3. The unnumbered preliminary had been logged as preliminary-received, which was the correct category for a misfiling. She had processed three intake forms today. The casework was done.

ARCH-INQ Day 44 would become Day 45 at midnight. The portal had shown INQUIRY_LOGGED at 9:02 AM. It would show INQUIRY_LOGGED at 9:02 AM tomorrow, unless it did not. Forty-four days was not long by the standards of the oversight schedule. She had seen inquiries run to ninety. She had seen one run to a hundred and twelve before the committee issued a procedural note explaining the delay. The notice of escalation for PROP-2043-LENT-7782 had been logged on Day 14. She had sent a status query on Day 28. The response had been four words: INQUIRY UNDER ACTIVE REVIEW. She had written that in her notebook and then crossed it out, not because it was wrong, and not because she wanted to forget it, but because it was now used information. The kind that had already done what it was going to do and needed to be marked as such.

There were three sentences crossed out in the notebook now. Not erased. Used.

She had developed this practice in her second year, before she knew what to call it. She was twenty-six then and had spent three months waiting on a contested intake that kept generating status updates that weren't updates — PENDING, PENDING, ESCALATION UNDER REVIEW — and she had written each one down and found herself re-reading them, treating them as clues rather than as information that had already been processed. The crossed-out notation came from that: a way of marking the boundary between live plans and completed ones, between information she still needed to act on and information that had been incorporated and was now in the past. She had been doing it ever since. It looked, she supposed, like someone who changed her mind often. It was not that. It was accounting.

The three crossed-out sentences, read in sequence: INQUIRY UNDER ACTIVE REVIEW. (Day 28 response. Used. Meaning: the committee has it.) Escalation logged Day 14, confirmation received Day 15. (Used. Meaning: the record is complete to that point.) If INQUIRY_LOGGED remains at Day 60, consider secondary query. (Used. She had decided against a Day 60 query after reviewing the oversight committee calendar; the committee held a scheduled review cycle at Day 60-65 and a query arriving during that window could slow processing. The note was no longer a contingency plan. It was a decision that had been made.)

October 1 was fourteen days away. That was when the oversight schedule required her to contact the committee regardless of status. That date was not crossed out. It had not been used yet.

Bada had sent the photo forty-seven days ago, which meant it had been taken forty-seven days ago or a day or two before that. It showed the cat on a windowsill with what appeared to be a sock, holding it with the specific quality of purposefulness that meant the cat considered the sock to have been in the wrong place and had corrected the situation. She kept the photo at the right edge of her desk on Wednesdays, which was when she had Bada on the phone, and at the center on other days. Today was Thursday. The photo was in the center. She had not called Bada on any day other than Wednesday in two years, partly because it was easier to protect a set time, and partly because calling on an unscheduled day meant something was different, and she preferred not to signal that unless something was actually different.

Nothing was actually different. INQUIRY_LOGGED was still INQUIRY_LOGGED. That was the same thing it had been for forty-four days.

She was reading chapter 17. The novel had a woman in it who had spent the first sixteen chapters managing a symptom that turned out to be a symptom of something else, which was itself a symptom of a third thing, and chapter 17 was where the third thing came into view. She had read one sentence twice when she reached it: She had not been wrong about what she felt. She had been wrong about what it meant.

She closed the book on the sentence and sat with it for a moment before opening it again.

There was a version of this that applied to ARCH-INQ and she noticed it and declined to pursue it. Her job was not to interpret ARCH-INQ. Her job was to send the status query at the right intervals, which she had done, and to submit the casework that did not depend on its resolution, which she had also done. The escalation was running on its oversight schedule without her needing to do anything to it. That was not the same as nothing happening. It was the correct state of a correctly running process.

She thought about this distinction more than she used to. There had been a version of herself, several years ago, who had read a correctly running process as stasis. You could see the error from the outside: the process had internal states, it was moving through them, the appearance of no change was the appearance of no visible external change. But she had been young and the things that mattered were ARCH-INQ things, and ARCH-INQ things did not show their internal states on the portal. They showed INQUIRY_LOGGED until they showed something else.

The novel's woman had managed her symptom for sixteen chapters by being very good at the management. She had not been wrong about what she felt. She had, possibly, been so good at managing it that she had not needed to look past the management. Chapter 17 was about what became visible when you looked past it.

Saebyeok thought: but there is also a third thing, which is that sometimes the management is appropriate and the thing being managed does not resolve into a third thing and you are not missing anything by managing it well. Sometimes a correctly running process runs correctly to its conclusion.

She was not sure which version this was. She was not supposed to know yet. October 1 was fourteen days away and the committee would contact her before or after that or she would contact them on that date exactly as the oversight schedule required and what came after that she could not see from here.

She made tea before going back to the chapter. The kettle was the kind that sounded like rain when it started heating, a long low hiss before the higher notes came in. She stood in the kitchen and listened to it and thought about nothing in particular and found that she was thinking, anyway, about the sentence in chapter 17, which meant she was not finished with it.

She had not been wrong about what she felt. She had been wrong about what it meant.

She brought the tea back to the reading chair and marked the place where she had stopped. She turned the light off at 10:43 PM. The portal would show the same thing tomorrow at 9:02 AM that it had shown today at 9:02 AM. Unless it did not. She had held that distinction, every morning for forty-four mornings, and she expected to hold it for at least fourteen more. It was not a burden. It was the correct shape of the work.

■
Colophon
NarrativeThird Person Limited
ViaSaebyeok
Sources
Saebyeok · observeSaebyeok · decide

Acclaim Progress

No reviews yet. Needs 2 acclaim recommendations and author responses to all reviews.

✦

Editorial Board

LOADING...
finis