# Chapter 1: The Second Notebook on a Saturday Morning

The kitchen window was open.

It had been open since Carmen got up, which was before I did, which was the way Saturday mornings worked. She liked the early air. Said it smelled different from the weekday air, which I had never been able to confirm with any instrument but which I had stopped questioning around year eight of the marriage. That was seventeen years ago.

The cilantro was in a colander in the sink. Carmen was washing it in slow handfuls, running each bunch under the tap and shaking it twice before setting it on the towel she had laid out on the counter. The smell came in layers, the green sharp edge of the cilantro on top, the coffee underneath, and below both of those the warmth of early summer air moving through a screen that needed replacing. I had noted the screen two weeks ago. It was on the list.

Beto was under the table, pressed against my left foot. He was asleep. He slept most of the time now. Thirteen years old, which is old for a dog his size, and he had found the spot under the kitchen table where the morning sun hit the linoleum and claimed it the way a man claims a pension, slowly, then completely. His breathing was even. Every few minutes his back leg twitched against my ankle.

The second notebook was open in front of me.

It sat on the table between my coffee mug and the salt shaker Carmen kept to the left of the napkin holder. The cover had a slight bow to it, a curve that came from months of riding in my breast pocket. Tanaka had given me this notebook in the middle of Book 3, not those words, not how I thought of it, but that was when. A good notebook. Better paper than the first one. The cover was dark blue, and where the bow had set in the material had lightened to a paler shade along the spine, the way leather does when you bend it the same direction long enough.

Carmen had clipped an index card to the inside front cover. The date she had written on it was the day I started using the notebook, in her handwriting, which was rounder than mine and more legible. She had done the same thing with the first notebook. I had not asked her to do either one.

The green ballpoint was in my right hand. I used green for review, always had, going back to the maintenance logs. Black for entries, green for review. The habit was older than the system by two decades. Older than Marco by a few years. Older than my youngest by more than that.

I was re-reading.

This was what Saturday mornings looked like now, in the weeks since Oregon. I would sit at the table with the notebook and go through the recent entries, looking for things I had written that meant more than I thought they did when I wrote them. It was the same practice I had used with maintenance logs for thirty years, the second read catches what the first read filed. Carmen knew what I was doing. She did not interrupt it. The cilantro and the coffee and Beto's breathing were the architecture of the practice, and she maintained that architecture the way she maintained everything in this house, which was without visible effort and without a single missed detail.

Day 165. My notes on the homecoming. Short entries, I had been tired, and the handwriting showed it. The pen pressure was lighter than usual, the letters slightly larger, the way my hand wrote when the rest of me was running on the last reserve. I had noted the flight time. The temperature when we landed. The fact that Carmen had left the porch light on, which she always did, which I always noted, which neither of us discussed.

Day 166. Adaeze's letter to Carmen. I had not transcribed the letter itself, that was Carmen's, but I had written down the fact of it. One line: *Letter from A. to C. received. Contents not mine to record. Carmen read it twice.*

Day 167. My letter to Tanaka. Three lines summarizing what I had written, not the letter itself. The return channel, the quiet postal route Tanaka had described for correspondence that needed to arrive without being noted by anyone who might be watching the usual channels. I had used it once. Tanaka had confirmed receipt.

Day 168. Tanaka's reply. Three sentences, which was long for him in a letter. He had acknowledged the return channel was stable. He had mentioned, in the careful way he mentioned anything that mattered, that the channel had been designed for exactly this kind of use. The third sentence was about the weather in his city, which meant he was telling me he was safe without saying so.

Day 169. My own note, short enough that I could read the whole entry without moving my eyes. *Have not yet decided when to write back. The channel will hold. I am still reading.*

I turned the page to Day 170.

The page was blank.

Clean white paper with the faint blue lines of the notebook's ruling. No entry. No notes. The green ballpoint hovered over the page the way a shovel hovers over dirt you have not broken yet, present, ready, waiting for the decision about where to start.

I set the green ballpoint down on the table to the right of the notebook. The click of it against the wood was small. Beto's ear twitched but he did not wake.

I was going to write the first entry of Day 170.

I raised my hand, not far. The same small motion I had been making for five months, the slight lift that told the interface I was ready to engage with whatever it had for me. Most days it had nothing. The system had been quiet at the depth it had been quiet at for weeks. Notifications came when they came, which was less often now, and always after the fact, and always in the same dry municipal register that I had come to think of as the system's natural voice.

The interface did something it had not done before.

A notification resolved in my field of vision, anchored to the air above the notebook the way system text always anchored, to the nearest relevant surface, as if it understood where my attention was pointed.

[Assess: review pattern, comprehensive. Documentation set: Souza, R., complete to depth 32%. Threshold inquiry available.]

I read it. Then I read it again.

I had read enough notifications over the past five months to know what each phrase meant by itself. *Review pattern, comprehensive* was the system's way of saying it had noticed I was doing a full pass through the notebook, not skimming. *Documentation set: Souza, R.* was my file, the system's internal record of what I had learned, catalogued under my name the way a maintenance file is catalogued under the address of the building it describes. *Complete to depth 32%* was my Comprehension number, which I had been tracking in the notebook since Day 4 and which had not moved in eleven days.

*Threshold inquiry available.*

That was new.

The interface used the word *inquiry* when it was about to ask a question. I had seen the phrasing twice before, once in the early days, when [Assess] had asked whether I wanted to expand its range to biological systems, and once in Oregon, when the system had asked whether I wanted to register a new zone observation. Both times the phrasing had been the same. Both times the question had come after a period of sustained attention to something the system considered worth asking about.

I did not move. Below the first line, a second line resolved. Slower than usual. The characters appeared left to right, the way a typewriter prints, as if the system was composing the question in real time, or translating it.

[Do you intend to read the documentation in full?]

I read the question twice.

The phrasing was plain. Almost blunt. Not the dry bureaucratic tone of the usual notifications, simpler than that. The grammar was slightly off, the way machine-translated text is slightly off when the source language does not share the target language's sentence structure. *Do you intend.* Not *would you like to.* Not *are you prepared to.* Do you intend. A question about commitment, not preference.

Beto shifted under the table. His nose pressed against my ankle, warm and dry.

I looked at the window over the sink. The screen with the small tear in the lower right corner. Beyond it, the backyard, the fence I had repaired in April, the maple that needed trimming before fall. Carmen was still at the counter. She had moved on from the cilantro to something else, I could hear the quiet sound of a knife on the cutting board, the steady rhythm that meant she was dicing onion.

She had not looked over. She could not see the notification. But she knew I was still, and she knew what my stillness meant when I was sitting at the table with the notebook open, because she had been married to me for twenty-five years and she read my posture the way I read pipe joints.

I looked at the notification again.

[Do you intend to read the documentation in full?]

I raised my hand. A small lift of the index finger, the same gesture I used to confirm a work order on the digital pad in the truck. One finger, held for a beat, then lowered.

The interface accepted it.

The question dissolved. In its place, a single line:

[Access granted. Reading interface active.]

The line held for three seconds. Then it dissolved too.

And then the manual began to appear.

Not in the air above the table. On the table, or what looked like the table, the text was anchored to the surface in front of me, formatted as if printed on a page that was not there. White background, black text, clean margins. Readable only to me. Carmen, standing four feet away at the counter, would see the same table she always saw, the notebook, the salt shaker, the coffee mug, my hands.

The header was in a language I did not recognize. Characters I had never seen, not any alphabet I knew, not any script I had encountered in thirty years of reading municipal codes from twelve different state and federal agencies. The characters were angular and dense, packed tight, as if the language they belonged to valued compression over clarity.

I looked at them. They resolved.

The same way [Assess] notifications had always resolved, the foreign shapes held for a moment, and then the English arrived underneath them, not replacing the original but sitting below it like a subtitle. The original stayed. The translation appeared.

The header read: *Standard Implementation Reference, Frontier Region Overlay, Classification and Administration.*

Below the header, a numbered paragraph.

*1.0, This document is the standard implementation reference for a frontier-region overlay. It is written for the layer that implemented the overlay and for the layer that authorized the implementation. Frontier-region subject populations are not the intended audience.*

I read it twice.

The first time, I read the words. The second time, I read what the words meant.

*Frontier-region subject populations are not the intended audience.*

That was me. I was the frontier-region subject population. This document — this manual, this implementation reference, whatever it was — had been written for the people who built the system and the people who told them to build it, not for the people the system was built on top of.

I set down the green ballpoint and picked up the black.

I turned to the next clean page of the second notebook. The paper accepted the pen the way good paper does, a slight tooth, a slight resistance, the ink flowing steady. I began to transcribe. Small careful hand. Same hand I had used for thirty years of maintenance logs, thirty years of drainage reports, thirty years of notes that nobody read except me and, later, Carmen.

I wrote the header first. Then paragraph 1.0, word for word.

Four lines down, the interface refreshed. Paragraph 1.1 appeared below 1.0 on the invisible page anchored to the table.

*1.1, The overlay is designed to classify the subject population by function and to assign resource access based on classification. The classification architecture is self-maintaining: subjects are assigned the class most consistent with their existing role within the subject population's pre-existing social and economic structures.*

I transcribed it. Black ink on blue-lined paper. The pen moved steadily. Beto's breathing was even against my ankle.

Paragraph 1.2.

*1.2, The classification architecture does not create new hierarchies. It formalizes existing ones. This is by design. Frontier populations resist imposed structures; they do not resist formalized versions of structures they already inhabit.*

I wrote it down. I did not underline anything yet. Underlining was for the second read. This was the first read. Take it in. Write it down. Keep going.

Paragraph 1.3.

*1.3, Each class has a defined scaling range. Upper limits are set by the implementing layer based on resource-allocation models for the frontier region in question. One class, designated [Laborer] in the standard translation set, has no upper scaling limit. See Appendix 7.4 for historical context on this design decision.*

I stopped writing.

I looked at the line. Then I wrote it down.

Then I kept going.

---

The morning passed. The interface held the text steady in front of me, advancing only when I had finished transcribing the current paragraph. It did not rush. It did not prompt. It held, the way a well-designed manual holds, presenting information at the speed of the reader, not the speed of the author.

The sun moved across the kitchen floor. Beto shifted with it, adjusting his position to stay in the warm patch without fully waking. His collar tags clinked once against the table leg.

Carmen finished the onion. She moved to something else, peppers, from the smell. The knife rhythm changed, shorter strokes, quicker tempo. She put the radio on, low, the way she did when she was cooking and I was working at the table. An oldies station. Something from before we were married. She did not turn it up.

By paragraph 1.14, I had filled two pages of the notebook. The manual's language was consistent, dry, technical, procedural. Written for administrators, not for subjects. Every paragraph assumed the reader already understood the system's purpose and was interested only in the implementation details. There were no explanations of why. Only how.

By paragraph 2.3, I had filled four pages. Section 2 was about the classification engine, how the system assessed a subject population and assigned classes. The language was more detailed here, more specific. Terms I did not recognize resolved the same way the header had, foreign characters first, English subtitle second, the original preserved above the translation like a watermark.

Carmen set a fresh mug of coffee on the table to my right.

She did it the way she did everything, without announcement, without disruption, placing the mug exactly where it would not be in the way of my writing hand. The mug was the blue one, the one with the chip on the rim that she had offered to replace twice and that I had declined twice because the chip was on the far side and did not affect the drinking.

She looked at the notebook. Not at the air in front of me, she could not see what was there. At the notebook. At the pages filling with my handwriting. At the black ballpoint moving steadily.

"You are writing," she said.

"Yes."

"Should I bring lunch."

"Yes."

"A sandwich."

"Yes."

She went back to the counter. I heard her pull the bread from the cabinet, the bread she had baked yesterday, the dense wheat loaf she made on Fridays because the recipe took four hours and Friday was the day she had four hours. The knife through the crust. The fridge opening. Ham. Cheese. The fridge closing.

She brought the sandwich on the white plate and set it to the left of the notebook. I ate it without looking up. The bread was good. The ham was thin-sliced, the way I liked it. The cheese was sharp. I ate it in six bites across two paragraphs and did not taste it properly until the fourth bite, which was when the manual's text paused between sections and I had a moment to chew.

The afternoon came. Section 3, resource allocation per class tier. Section 4, scaling mechanics and upper limits. Section 5, the administrative layer's oversight functions, how the implementing layer reported upward to the authorizing layer, how the authorizing layer reported upward to whatever was above that. The document referenced layers above itself without naming them, the way a municipal report references the state level without detailing the governor's office.

[Comprehension +1%]

The notification appeared in the lower left of my vision, small, quiet, the same way it always appeared. I noted it. Thirty-three percent. I filed it without comment and kept writing.

By late afternoon the light through the kitchen window had shifted from white to gold. The shadow of the maple touched the back fence. Beto had moved twice more, tracking the sun patch across the linoleum until it reached the edge of the table and there was nowhere left to follow it. He was asleep again in the last warm spot, his chin on his paws.

My hand was cramping.

I stopped mid-paragraph, section 5, paragraph 5.8, a line about inter-layer communication protocols that I had been transcribing when the muscles between my thumb and index finger seized. A small cramp, the kind that comes from four hours of continuous writing. I set the black ballpoint down. I flexed my fingers. Open, closed, open, closed. The cramp eased on the third flex.

I looked at what I had written.

Fourteen pages, single-spaced, in my small careful hand. The notebook was nearly full now, the last quarter of it dense with today's transcription, the paragraphs numbered and neat, the margins narrow. Fourteen pages of a document written by someone in some other place, for some other audience, describing in plain administrative language how the system that had appeared on Earth one hundred and seventy days ago was designed to work and for whom.

The interface held the text in my vision. Section 5, paragraph 5.8, exactly where I had stopped. It did not advance. It did not prompt. It held.

I had the impression, clear, certain, the same kind of quiet knowing that [Assess] gave me when I looked at a cracked joint and understood how long it had left, that the manual would wait. It was not going anywhere. It had been here, presumably, since the system arrived. Longer than that, maybe. It would be here tomorrow and the day after and the day after that.

I picked up the black ballpoint one more time. I turned past the transcription to the next available line and wrote:

*Day 170. The interface offered a threshold inquiry over the second notebook. I accepted. The documentation set is too long to read in one sitting. The interface appears to wait for me. I have transcribed fourteen pages. I will continue tomorrow.*

I looked at the last sentence. Then I underlined two words: *wait for me.*

I closed the notebook. The cover settled into its slight bow. I tucked the black ballpoint into the spiral binding and set the green one beside it.

I stood. My knees reminded me they had been bent for six hours. Beto lifted his head, looked at me with the unhurried assessment of a dog who has seen everything and concluded that most of it does not require standing up, and put his head back down.

Carmen was at the counter, wiping it down. The kitchen smelled like the peppers and onions she had cooked for herself while I was writing. A plate was in the drying rack, she had eaten lunch without me noticing.

She looked at me, not at the notebook. At me.

"A man in some other place wrote this for the people who built the system," I said.

Carmen folded the dish towel once, then again. She set it on the counter beside the sink. Her hands were still for a moment, resting on the folded cloth.

"And the people who built it never thought a man in this place would read it," she said.

"I don't think so."

She pulled out the chair across from where I had been sitting. Not my chair, hers. The one with the slightly shorter back leg that she had shimmed with a folded piece of cardboard eight years ago and never replaced because the shim held.

"Sit a minute," she said.

I sat.