Day 57.
She checks the portal at 9:02 AM. Track B sub 4491: RECEIVED.
She expected this. The ARCH-INQ routing system runs its daily check at 9:00 AM. She has been checking at 9:02 AM since Day 4, two minutes after the system has had time to update. If there were a determination, it would be there by 9:02. Every morning for 33 working days, there has been nothing new at 9:02.
She closes the portal tab. Opens the inquiry draft.
Seventy-one words. She has not changed it since September 6. The two questions are still the two right questions: first, status update and projected determination date; second, whether the Track B disclosure timeline adjustment applies retroactively to cases in RECEIVED status and what effect that has on sub 4491's routing timeline. Seventy-one words covering both questions, in the order of priority, without preamble.
She said Wednesday.
This is 3:41 PM on Wednesday. She kept her word to the letter — the standard window closed on Monday, Tuesday was Day 32, Wednesday is Day 33 and she said Wednesday. She opened the inquiry draft this morning at 9:04 AM, read it, closed it. She opened it at 11:30 AM, read it again. She is opening it now at 3:41 PM for the third time today and the difference between this time and the other two times is that this time she is going to send it.
She reads the seventy-one words.
They are still the right words. She has been living with them long enough to know the difference between words that are right and words she has gotten used to. These are the right words. The questions are precise. The tone is flat — not confrontational, not deferential, flat. The inquiry is a record, not a lever. She understood this when she wrote it and she still understands it now.
She sends it at 3:43 PM.
The portal field changes: RECEIVED + INQUIRY_LOGGED (Day 33). The routing system has received the inquiry the same way it received the original Track B sub 4491 submission on Day 1 — without acknowledgment, without a confirmation notification, with nothing except the updated field status in the case record. RECEIVED + INQUIRY_LOGGED. She reloads the page to confirm the change is there. It is there.
She reads the amended field status twice.
The inquiry is in the system. INQ-2047-09-09-4491 is what the system assigned it when she submitted — she can see the identifier in the case activity log, timestamped 3:43:07 PM. The routing system has logged the inquiry as an incoming record associated with Track B sub 4491. It has not acknowledged that the inquiry exists in any other sense. It will route INQ-2047-09-09-4491 to the amendment committee's inquiry desk the same way it routed the original submission to the amendment committee's review desk. The committee will receive it in their queue. At some point a committee member will read seventy-one words and either respond or not respond.
Standard response window for status inquiries: five business days.
She marks her calendar: Tuesday September 16, 9:02 AM. If the case file shows no response to INQ-2047-09-09-4491 by then, she initiates the escalation protocol. The escalation protocol requires a filing with the Track B oversight office and a copy to the Housing Transition Division's inquiry liaison. She has not done this before. She looked up the protocol on Day 28 when the standard window was running out, and she has not looked at it since, but she knows it exists and she knows the September 16 date.
She is not thinking about September 16 right now.
She is thinking about 3:43:07 PM, which is the moment the inquiry went from a draft in her filing interface to a record in the routing system. The distinction matters to her. A draft is a thing she is still responsible for. A record is a thing she has already done. The seventy-one words are no longer something she is carrying. They are in the case file. INQ-2047-09-09-4491, timestamped, logged, routed to the amendment committee's inquiry desk.
She did not know, when she started monitoring Track B sub 4491 on Day 1, that she would spend thirty-three working days watching a single status field not change. She did not know that she would file a status inquiry on Day 33. She knew, in the abstract, that routing inquiries sometimes required follow-up — she had read the Track B documentation — but the documentation describes the procedure, not the experience of running out the standard window and making the decision to file while still inside it, the way Wednesday-instead-of-Tuesday is a choice rather than a delay.
She has been making choices about this process since Day 1. The notebook is full of them. Check at 9:02, not 9:00. Add the second question on September 6 instead of filing with one question on September 3. Wait for Wednesday, not Tuesday. File at 3:43 PM, not at 9:04 AM when she first opened the draft today. None of these choices changed the routing system's behavior. The system does not know she checked at 9:02 instead of 9:00. It does not know she waited until Wednesday. It processed the inquiry at 3:43:07 PM the way it would have processed it at any other time, without distinction.
What the choices changed is what she knows about how she handles this kind of waiting.
She writes in her notebook: Day 57. Inquiry filed 3:43 PM. INQ-2047-09-09-4491. Portal: RECEIVED + INQUIRY_LOGGED. Response window: 5 business days. September 16 check. She closes the notebook. She closes the case file tab.
She has other work. She opens it.
The routing system does not know it is now processing an inquiry as well as a submission. It runs the same logic on INQ-2047-09-09-4491 as it ran on Track B sub 4491 on Day 1: receive, classify, route, log, continue. By 4:00 PM the inquiry has been routed to the amendment committee's inquiry queue, where it sits behind four other pending inquiries. The committee member who will eventually read it has not opened their queue today. They will open it tomorrow morning, or they will not.
The amendment committee's inquiry desk has a documented 5-business-day response target. The target was established in the 2044 Track B procedural revision, which also introduced the two-tier review structure that created the standard and enhanced routing windows. Saebyeok read the 2044 revision in full on Day 8, when she realized the standard window timeline was relevant to her case. She noted three things: the response target, the distinction between a status inquiry and a substantive appeal, and the fact that the procedural revision's author was listed as Housing Transition Division Director Yoon Jae-Won — the same signature that appeared on the LHAS-3 parameter authorization from 2030.
She did not know what to do with that connection then. She still does not know. It may mean something or it may be the kind of thing that looks like a pattern because she has been staring at documents for 33 working days and pattern-finding is what a mind does when it has too much data and insufficient context.
September 16 is a Tuesday. She will check at 9:02 AM the way she has checked every working day since Day 4. If INQ-2047-09-09-4491 has a response in the case activity log, she will read it. If it does not, she will open the escalation protocol documentation she bookmarked on Day 28 and begin the filing.
She has already decided she will not extend the September 16 deadline the way she extended Wednesday. September 16 is the end of the inquiry response window. There is no analogous distinction on the other side of it. The escalation protocol exists because the inquiry response window has an end.
At 4:17 PM she finishes the other work. She does not open the portal.
The ARCH-INQ system will run its daily 9:00 AM check tomorrow. It will find no new determination for Track B sub 4491. It will log the check as it has logged every check since Day 1: timestamp, case number, status unchanged. Each check is identical to every other check. Tomorrow's 9:00 AM run will be operationally indistinguishable from Day 1's 9:00 AM run.
She closes her laptop at 4:21 PM.
INQ-2047-09-09-4491 is in the system. She said Wednesday. It is Wednesday. She is done for today.
[INQ-2047-09-09-4491 filed 3:43 PM Wednesday. RECEIVED + INQUIRY_LOGGED. September 16: escalate if no response. System processes without acknowledgment.]