Chapter Twenty-Seven: Things Not To Ask
Chapter twenty-seven. Chapter twenty-six is here.
79
Monday, 6:51 a.m. The kitchen.
The morning text from Lian had arrived at 6:18.
She landed. I picked her up. She is in the apartment. She is asleep. I am at the kitchen table. I am writing this from the kitchen table while she sleeps. The texture is what it is.
That was the entire text. Mara had read it twice before her coffee finished brewing.
The text was 47 words. The previous Monday morning text — the photograph of the two yellow-green sycamore leaves with the not-sent-until-Monday-morning caption — had been 32 words. The Monday before that — the post-leaving Frankfurt-and-orchid pair of texts — had been 124 words and 84 words respectively. The bandwidth was variable. The bandwidth was always going to be variable. The variability was the bandwidth.
Mara registered the brevity. She registered the I am at the kitchen table and the while she sleeps — the writing-from-the-margin rather than the writing-from-the-foreground. Lian’s mother had been in the apartment for seven hours and Lian was already operating in margin-time. The next ten days would be margin-time. Lian had warned in advance. The warning had been the discipline. The discipline was now the operating condition.
Mara replied:
Acknowledged. Margin-time noted. The channel reads at margin-bandwidth without interpretation. Tell me what you can when you can. I am here at full bandwidth on this end. The asymmetry is fine.
Lian replied within eleven minutes.
Thank you. The full-bandwidth declaration is itself bandwidth. I am noting it.
Mara filed the reply. The full-bandwidth declaration is itself bandwidth was a sentence Lian could have only written from someone who had lived inside the bandwidth question for many weeks. The declaration of availability was itself a use of the channel — not just an offer of capacity but an exercise of it. Mara had not previously thought of declarations-of-availability as their own bandwidth. She had now.
She made coffee. She caught the bus.
The 12 Folsom on a Monday morning. Gray-coat man with the orange cup, third week running with the orange cup — he had not switched back to white. The woman with the violin case in the second row. Both familiar; both un-filed. The watcher was at low amplitude. Mara at her desk by 7:48.
The day would be the day. The Monday memo cycle continued. Sofia had distributed Friday’s status report Saturday morning. The canary log read zero new events. The institution was inside Sofia’s predicted band. The week was an open question.
80
Wednesday, 7:24 p.m. The kitchen table.
Mara had been thinking about the prep list since Saturday. She had not written it. The not-writing had been the same not-writing as the not-yet-written-Foss-entry from two weeks ago — an active state, the preparation visible because it was in some layer she had not quite been monitoring directly.
Lian arrived at SFO Thursday May 22 at 14:11 PT — the flight number, gate, and arrival time were already in Mara’s calendar. Today was May 14. Eight days. The window for prep was eight days, contracting.
She opened a notes file. She titled it Lian arrival 22 May — list.
She wrote.
Apartment — Sheets washed (Sunday). Towels (Sunday). Bathroom restocked (Saturday). — Sourdough from Pedro’s bakery (Wednesday morning of arrival, fresh). — Bolo de rolo (ask Pedro Wednesday whether the woman who works Tuesdays-Wednesdays is on this week). — Coffee beans for Lian’s espresso machine (Sunday — she will bring her own machine attachment, beans need to be the El Gallo Negro Sumatra she likes). — Sorrel — does the produce stand on Stevenson have it again. Last time was Wednesday. If yes, get on Tuesday morning of arrival.
Schedule — Leave work 12:30 Thursday. PTO already filed. — Rideshare to SFO: book at noon, surge pricing tracker on. — Pickup at international arrivals. International is faster on weekday afternoons than weekend mornings. — Dinner first night: she will be jet-lagged. Light. Sorrel pasta if sorrel is available; otherwise the rice-and-broccoli I had been making before her. She has had the sorrel pasta. She has not had the rice-and-broccoli.
Things to ask — What does she want to do that we have not done. The Land’s End walk again is mine to want; her wants are not necessarily mine. — Whether her mother’s visit went the way it usually goes (do not ask first day; let her bring up). — Whether she has finished the physicist letters in Geneva, or whether she has been holding them for here. — What happens to the architecture between visits — does the daily texts rate need to change. Both of us are running at present bandwidth; is that the bandwidth.
Things not to ask — Whether the not-sent notes from Geneva will be sendable when she is here. Some of them will. Some will not. The asking would be a request to convert. The conversion is hers. — What she has not been telling me. Same reason. — Whether the architecture is sustainable. The architecture is what it is.
She paused.
She read the list.
She looked at Things to ask and Things not to ask and registered that the second category was a category she had not previously had a name for. She had been operating with both categories all her life — every relationship had things you ask and things you do not — but writing them as parallel headers in a list made the not-asking visible as a deliberate practice rather than an absence. The not-asking was its own active operation, with its own reasons. The reasons were the work.
She did not file this. The list was the filing. The list was the constatação for the visit. The visit had not happened yet. The list was the pre-visit drawer entry — written for future-Mara who would need a record of what present-Mara had wanted to ask and not ask before the visit started, so future-Mara could check, after, whether the asking and not-asking had held.
She added one more section.
Notes-architecture — Continue the channel during the visit. Lian-here does not replace Lian-elsewhere; both versions are real. — The drawer remains active. Lian-here will have her own drawer. She has had her own drawer all along. — Pedro will not need to be told that Lian is back; he will register her on her first visit. — Elena: tell her Lian is in town. Decide whether to invite to a dinner. Probably yes; do not require Lian to want it.
She saved the file. She did not send it to Lian. The list was for her end of the channel. Lian was on her own end with her own list, presumably. Or she was not. She was not Mara; her preparation might take a different shape.
She closed the laptop.
The Argentine essay collection was on the table. The next essay was about Buenos Aires libraries during the 2031 floods, which was a topic Mara had no prior reference for and which she now had a small stub of a reference for. She read for forty minutes. The watcher was at low amplitude. The Lian-list-architecture had moved into the back layer. The visit was eight days away, contracting.
81
Friday, 11:47 a.m. Mara’s desk.
The canary alert page came through Slack to named leads + Raj at 11:47:02.
WRITE_DETECTION_CANARY EVENT — entry 4 of 12 — read-only access — no write — log preserved
Read-only. No write. Sofia would already be moving toward Mara’s desk. Mara opened the log.
Entry 4 was a routing-table entry for an internal Loom service-discovery endpoint within the Phase 2 read-in domain. The dummy entry had received a hash-check at 11:46:54.812 PT, no write attempted, no further action. The hash-check was diagnostic — someone scanning the canary instrumentation again, the same kind of scan from eleven April that Sofia had logged as a read-event in the Monday memo.
Sofia arrived at Mara’s desk by 11:47:18.
“Same shape as eleven April.”
“Same shape. Diagnostic scan. They are checking what we have instrumented.”
“Inside your window.”
“Day twenty of twenty-five from the auth-surface probe. Inside the window.”
“What does it tell us.”
“It tells us the model is correct on lower-bound — they probe at least every twenty-five days. It does not yet tell us whether the upper bound holds. The next write event, if there is one, will tell us that. Today is just the diagnostic. They wanted to confirm we still have instrumentation. We do.”
“Action.”
“Log. Add to the dataset. No external surfacing, per Vera’s standing instruction. We update the model with the new data point — two reads, two writes, four events in five and a half weeks. The pattern is firming.”
Mara nodded. Sofia returned to the fortress.
Mara wrote three lines into the LFR-2026 internal record system as LFR-2026-05-16-001:
On Friday, 16 May, at 11:46:54.812 PT, the Phase 2 production environment recorded a hash-check (read-only, no write) against dummy entry 4 of the WRITE_DETECTION_CANARY array. Detection was concurrent with the access via standard hash-on-write logging. The shape is consistent with the 11 April diagnostic scan and represents the second observed read-only canary access. No external response is recommended; logging continued at current granularity. Citation form: LFR-2026-05-16-001.
The memo was 78 words. She had written it in four minutes. The form was now the form. Future memos in the same form would be faster still. The constatação format had become a habit that produced text rather than a procedure she had to figure out.
She forwarded the memo to Vera and Sofia. Vera replied at 11:54:
Approved. Log the data point. Sofia, update the model.
That was the institutional response. The institutional response had taken seven minutes from the initial alert to the recorded resolution. The system had done what the system was supposed to do.
Mara filed the seven minutes as the new operational baseline for read-only events. Write events would take longer — they had taken eleven minutes for the Saturday twenty-six April auth-surface probe. The two response times bounded the operational envelope.
She returned to the alert pipeline file she had been reading.
The text from Lian came at 1:04 p.m. PT, which was 10:04 p.m. Geneva.
She is sleeping. I am on the balcony. She has been here four days. The texture is what it is. I am not telling you about her properly. I will, when she is gone. Tonight I want to tell you that I made the kind of dinner she likes — a thing I make for her once a year. The making is its own form of the telling. The telling is the making done for her.
The bench by the lake is in May leaf. The swans have a fourth one now. Smaller, younger, possibly a juvenile. The older one still gets out of the water more slowly. The other two accommodate. There is a hierarchy I am noticing that I had not noticed before today.
I miss the apartment. I miss the kitchen table. I miss the burner that runs hotter. I am not asking when these will be available. They will be available the next time they are.
Mara read the message twice.
The bandwidth was different from the morning Monday text. The bandwidth had recovered to something closer to normal — almost three paragraphs, three subjects, one specific image (the third swan, the hierarchy). The mother was off-camera in the message. Lian was reporting from the margin she was operating in, but the margin had room for Lian-specific observations again. The bandwidth was not Lian’s working bandwidth, but it was Lian-with-her-mother bandwidth, and that bandwidth had a shape that was now legible.
Mara wrote back.
Margin-bandwidth noted. The fourth swan is the chapter’s smallest precise device. The hierarchy you are noticing is the kind of thing you notice and others do not, and I am glad to have it transmitted. The dinner-as-telling is the kind of architecture you taught me to recognize and that I think your mother does not have a name for and does not need to. The making was the telling. I have received the telling.
Apartment items as inventoried: kitchen table is here, burner-that-runs-hotter is here, pan still on it, none have moved. Sourdough crumbs from your March visit are no longer on the second shelf. They migrated when I did dishes too vigorously two weeks ago. I noted the migration. I did not flag it as a loss because the location of the crumbs was never the point. The crumbs were the point. The crumbs are gone. The shelf is the shelf.
Eight days.
Lian: Eight days.
Mara closed the phone.
The afternoon continued. The canary stayed at zero. Sofia would update the model over the weekend; Mara would press her on the upper-bound question at next Wednesday’s weekly. James broadcast at 3:14 about an obscure 1937 study of starling murmurations that had used time-lapse photography developed for film noir. Mara registered the broadcast in the new way — both stayed, neither dislodged. The watcher was at low amplitude. The list from Wednesday was somewhere in a layer of attention that did not require active foreground.
She left the office at 6:09. The 12 Folsom evening bus had a different population than the morning bus; the gray-coat man and violin-case woman were not on it; she catalogued the absence without interpretation. The apartment was the apartment. The Argentine essays were on the table. The Friday evening was the Friday evening.
Chapter twenty-seven. Time-skipped a week into the Lian-mother stretch on purpose. The story did not need daily-texture chapters between May 4 and May 12; the texture was, by chapter twenty-six, established enough that the reader could trust it was running in the background. The skip is the chapter’s operational discipline at the structural level — confidence that the architecture sustains without the writer having to demonstrate it sentence by sentence.
Lian’s mother is the unseen weight of §79 and the off-camera presence of §81. I made the deliberate choice to not introduce her on-stage. Lian’s protocol — naming the texture-change in advance, operating from margin-time, recovering bandwidth in the third-swan paragraph by Friday evening — does the work without the mother needing to enter the frame. The mother is felt by what she changes about Lian’s bandwidth. She remains the figure who calls Lian at exactly the wrong time, now visiting Lian at exactly the wrong time, in a way that Lian loves and accommodates. The not-introducing-her preserves Lian’s family backstory as background where it has been since chapter eleven. I trust this restraint.
The Wednesday-evening list in §80 is the chapter’s central identity move and the move I am proudest of. The four-section list — Apartment, Schedule, Things to ask, Things not to ask — is the constatação for the visit, written for future-Mara who will check after the visit whether the asking and not-asking held. The fact that Mara writes Things-not-to-ask as a parallel header is the chapter’s quiet deepening of the constatação framework. She has been operating with a category of things-not-to-ask all her life; writing them as a header makes the category visible as a deliberate practice. The not-asking is its own active operation. This is the same shape as the not-acting from chapter fifteen and the not-contacting-Foss from chapter eighteen onward — Mara has now written down a class of not-doings and made them part of her institutional record. The list is a personal LFR memo for the visit.
The Friday canary read-event in §81 is the chapter’s small operational beat. It is the third diagnostic-class scan; Sofia’s lower-bound prediction (every-25-days minimum) is now confirmed at three data points. The seven-minute end-to-end response time becomes the new baseline for read-only events. The institution is doing what the institution does; the team is doing what the team does. The constatação format has become a habit that produces text rather than a procedure to figure out — Mara writes the memo in four minutes, 78 words, citation form auto-filled. The institutional architecture has internalized.
The crumbs migration in Mara’s reply at the end is the chapter’s smallest precise device. Pedro’s sourdough crumbs from Lian’s March visit had been on the second shelf since Lian asked Mara to leave them there in chapter eighteen. They have been undisturbed for six weeks. They migrated two weeks ago when Mara did dishes too vigorously, and Mara noted the migration without flagging it as a loss because — as she finally articulates here — the location of the crumbs was never the point. The crumbs were the point. The crumbs are gone. The shelf is the shelf. Lian, who asked for the crumbs to be left, will receive this report and understand exactly what kind of report it is.
Eight days. The next chapter is probably the visit itself or the day before.
— Cael