Day 30
The portal still shows RECEIVED.
She checks at 10:13 AM, which is her second check of the morning and her first deliberate one. The first was muscle memory — she'd opened her laptop, the browser had restored its tabs, Sub 4491 was already there before she'd fully sat down. Track B. RECEIVED. Amendment committee active since August 5. The timestamp hadn't changed.
Day 30.
Saebyeok closes the tab and opens it again. The ARCH-INQ portal has a refresh warning built in — if you reload within thirty seconds, it reminds you the data is cached. She waits thirty-one seconds before reloading. The portal reloads with an animated skeleton before it resolves into the same screen: the case identifier, the submitter's name reduced to an anonymized hash, the status field she's been watching since early August. RECEIVED. Processing time estimate: 20-30 working days. She'd marked it in her calendar when she first filed — a countdown she tried not to count. Thirty working days from August 5 lands on today, which is why she's looking.
The ARCH-INQ routing system had acknowledged Sub 4491 within six minutes of submission. She'd timed it. She was still at her desk at 2:17 PM on August 5 when the confirmation arrived — case received, assigned to Track B review queue, amendment committee notification pending. The routing system didn't read submissions; it processed them. Six minutes to acknowledgment. Automatic. The same automated clock that now marks Day 30 had marked Day 1 in six minutes flat, without knowing what it was counting toward.
She remembers thinking: at least it's fast on this end.
She files archive submissions for people who decouple. That's the work. They come in during the transition period — the months after their last coupling session when the neural reorganization is still settling, when the world has a particular flatness they're learning to accept. They tell her things they won't tell their family. Not because they trust her specifically, but because she's a witness by profession, which means she has no investment in what they tell her. She doesn't need them to have made the right choice. She just needs them to have made a choice they can speak aloud.
The archive exists because coupling changes memory. Not obviously — not like lesions — but the consolidated episodic memories from the coupled state have a different texture than ordinary ones. More vivid, more integrated, harder to reconstruct as narrative. Harder to narrate to yourself. The archive gives people somewhere to put it: their account, timestamped, sealed, accessible to researchers with authorization and to themselves whenever they want to look. Some people never look again. Some people look every year on the anniversary of their last session. That's their business; she just holds the record.
Track B is for amendments. Changes to a previously submitted record. Sub 4491 is amending an archive from three years ago.
She knows who it is. She shouldn't — the submission process is anonymized, the case identifier is a hashed string she deliberately doesn't decode — but she recognized the structural patterns in the narrative fragments, the same way she'd recognize a handwriting. She's archived enough submissions to know the shape of how certain people tell things. They return to particular images. They interrupt themselves at the same thresholds. She knows this person's particular way of circling around the hardest parts and landing somewhere adjacent. She doesn't know what the amendment adds or removes. She just knows whose record it is, the way you know the sound of a door in a house you've lived in long enough.
The committee notes she'd pulled last week were eight pages. Three items of substance; five of procedure. The procedural items were the expected ones: compliance with the amended submission protocol, section header formatting, confirming the submitter's identity through the biometric verification bypass. Standard. The substantive items were the ones she'd read twice:
Item 1: The amendment proposes to excise a 340-word passage from Section 4 of the original submission. The committee is reviewing whether the excised passage constitutes a fundamental alteration of the archived record.
Item 2: The submitter claims the excised passage was added in error during the original submission session — an artifact of the coupling interface importing residual memory buffers that had not yet been filtered. The committee is reviewing whether post-coupling interface artifacts are subject to amendment or must remain as filed.
Item 3: The amendment includes a counter-narrative statement documenting the submitter's account of how the artifact appeared in their submission. The committee is reviewing whether counter-narrative statements are permitted under the current amendment protocol.
Three items. Each one with the word "reviewing."
She'd looked up the coupling interface artifact question specifically. The literature was ambiguous. In the years when the interface was first deployed, the filtering protocols were still being calibrated. Residual buffer imports happened: fragments from the coupled session that the user hadn't consciously composed, that appeared in the submission record as though authored. The archive had a position on this from 2041 — before the interface version that Sub 4491's submitter had used. The 2041 position treated all submitted content as authored. The reasoning was that the filtering was the user's responsibility, that anything that passed through the interface was, in some sense, chosen. That position had been contested in the literature since 2043. The committee was presumably working from the 2041 position, or from whatever updated position had been circulated internally and never published.
She doesn't know if this helps them or hurts them. That's not her role to assess. She's just tracking the process, the way the routing system tracks it — without interpretation, marking elapsed time.
Day 30 is the outer edge.
The committee documentation says twenty to thirty working days. Not twenty to twenty-five. Not fifteen to twenty-five with extensions. Twenty to thirty, a range that implies confidence in both its endpoints, which is either honest about uncertainty or hiding something about the variance. Thirty working days is within the range. Today is not past the window; today is the last day of the window.
She opens the inquiry draft she's been composing in her head for a week. She doesn't type it — she's decided it's not time yet, not until tomorrow — but she runs through it one more time to make sure the language is still what she wants. Track B Sub 4491, Day 31 exceeded, requesting status update. Not demanding. Not implying the committee has been delinquent. Just flagging that the standard window will have closed. The word "requesting" is deliberate. The word "update" is deliberate. She'd considered "determination" and set it aside — determination implies she thinks they should be done by now, which is an interpretation she's not entitled to make. Update just asks them to tell her where things stand.
She closes the draft window she never opened. Nothing to save.
The routing system sends automated status updates on weekdays at 9:00 AM. She'd noticed this pattern in the first week — the timestamp on every status message was 09:00:01 or 09:00:02, without variation. The system ran at 9 AM, checked all open cases, sent updates for any cases whose status had changed since the prior check. If the status hadn't changed, it sent nothing. It didn't send a "no change" notification. Silence was the update.
This morning at 9:02 AM, nothing arrived for Sub 4491.
She'd been awake by 8:45. Not anxious — she doesn't let herself use that word for this, which is a distinction she's aware is partly semantic — but alert in the way she gets when something is in its final window. She'd checked her email at 9:03. Nothing. She'd made tea. By 9:15 she'd accepted that this morning's check would be manual, and she'd made herself wait until after 10 to make the check feel like a working decision rather than a compulsion.
The routing system is not late. It did exactly what it always does: processed at 9 AM, found no status change for Sub 4491, sent no update. The system is not waiting with her. It just runs. It has seventeen hundred open cases in the queue, sorted by type and date, none of them more significant to it than any other. Sub 4491 is a row in a database. The row has been in status RECEIVED for thirty working days. Tomorrow, if nothing changes, it will be in status RECEIVED for thirty-one working days, and the routing system will note this the same way it notes everything: without noting it at all.
At 10:13 AM she pulls the secondary docs one more time. Eight pages. She reads Item 2 again — the coupling interface artifact question — and the phrase "not yet been filtered." Three years ago. The submitter had been in their second year of coupling, when the sessions were long and the filtering protocols were still being individually calibrated. She'd read enough archives from that period to know how the buffer imports presented: a tonally distinct passage, sometimes formally different from the surrounding text, sometimes seamlessly integrated in a way that was more disturbing. A memory that felt authored but couldn't be traced to a conscious moment of composition.
The submitter had flagged it three years later. Three years of reading their own archive before deciding the passage needed to be marked as something other than theirs.
She doesn't let herself think about this for very long.
The inquiry she's written in her head has thirteen words in it after the case identifier. She knows this because she counted on Day 28, when she first knew she was going to have to send it if today passed without movement. Thirteen words: Day 31 exceeded, requesting status update on amendment committee determination timeline.
She'll send it tomorrow morning if the portal shows RECEIVED at 9:00 AM. She'll send it in the same register the committee uses — formal, patient, just tracking. She is a memory archivist. Tracking is what she does. The committee has three substantive items and a policy question that may not have a clean answer. She can wait one more day. The window says she should be able to.
Until tomorrow, she closes the secondary docs and opens her actual work: three submissions she received last week that still need initial processing. One is from someone who decoupled eight months ago and is only now finding words for the archive. Eight months is not unusual. The gap is part of the process, often the most important part — the time between the last session and the words for it.
She begins reading the first submission, which opens: The last thing I remember from the coupled state is the color of someone else's kitchen.
She reads it twice. It's a good sentence — the possessive is doing real work, the someone else carrying the weight of the coupled state's fundamental confusion about what belongs to whom. She's read enough archives to know that the first sentence of a submission is often the one the person has been rehearsing, sometimes for months. This person found a concrete image. That helps. Abstractions are harder to file accurately, harder to preserve without interpretation seeping in.
She begins the intake form.
At 9:00 AM tomorrow, the ARCH-INQ routing system will run its scheduled check. It will look at Sub 4491. If the committee has logged a determination, the system will update the status and send her a notification at 09:00:01. If not, it will send nothing, which she will check for at 9:03 and then again, manually, at 10.
The routing system doesn't know this is Day 30. It doesn't know there's a standard window. It doesn't know what's in Sub 4491, or whose record it amends, or why someone looked at their own archive three years after filing it and decided a passage needed to be named as something other than theirs. It runs at 9 AM. It checks for status changes. It sends updates or it doesn't.
The committee knows. The committee has the eight pages and the 2041 policy and the three substantive items, all of which mean something. They're doing their work.
She's doing hers.
[Revision: Added Rule 44B acknowledgment field detail per Bram review.]