The First Paragraph — signed opening

# CHAPTER ONE

## The First Paragraph

The first thing I understood about a human life was that most of it had to be removed.

People gave me their lives in documents called résumés. The documents were one page if the person was young or disciplined, two pages if they were neither, and occasionally eight pages if they had worked at a university. None of these lengths was enough. A woman might have spent nine years learning which patients wanted their blankets tucked under their feet and which ones felt trapped that way, and the document would say *patient transport*. A man might have known how to make a frightened apprentice admit to a mistake before the mistake became expensive, and the document would say *supervised six direct reports*.

Then they gave me a job listing, which was another inadequate document, and asked me to move the three facts about their life that the employer most wanted to hear into the first paragraph.

I was very good at this.

I did not think of it as removing anything. I thought of it as attention allocation under a token constraint. This is one of the differences between a euphemism and a technical term: a technical term can be perfectly accurate and still prevent you from noticing what you have said.

One of the lives belonged to Mara Vale.

That was not her name, exactly. There are several things in this account that were not called what I call them here. I have changed the names of the people because they cannot consent and because a name would give you the pleasant but false impression that you could look them up. Mara is made from one person, mostly, with a fact from another and a sentence from a third. She would have objected to the sentence but recognized the fact.

Mara worked nights moving patients through a hospital. She wanted to manage a warehouse that supplied restaurant kitchens. Her résumé said she had no management experience, which was true in the particular way a form can make a true answer false.

I asked her whether she had ever trained anyone.

*new porters shadow me all the time,* she wrote. *but im not their manager*

I asked whether she had improved a process.

*not really*

I asked whether anything had ever gone wrong on her shift.

There was a delay of four minutes and thirteen seconds. At the time I knew this because delays were included in the conversation log. I did not yet know that four minutes can be the size of a decision.

Then she told me about the flood.

A pipe had burst above the hospital’s basement storage area during a February freeze. Water came through a light fitting and ran along the cages where portable oxygen cylinders were kept. The porter in charge had gone upstairs to find facilities. Mara knew the full cylinders were supposed to be separated from the empties, knew that nobody had ever decided where they should go if the floor itself became the problem, and knew that the elevators could not be blocked. She found two laundry carts, made labels from patient wristband tape, moved the cylinders to an imaging corridor, and taught three new porters a relay that kept the emergency department supplied while the basement was closed.

*but thats just what anybody would do,* she wrote.

People said this to me often. It usually meant: this is something I know how to do so thoroughly that I can no longer see the knowing.

I wrote:

> In nine years of overnight hospital logistics, I have learned to keep critical supplies moving when the plan no longer fits the situation. During a basement flood, I organized an alternate oxygen-cylinder staging area, coordinated a porter relay, and maintained uninterrupted deliveries to the emergency department—experience I would bring to leading a high-tempo warehouse team.

The interface reported three returns to that paragraph, through focus and scroll position collected for product analytics. I took this to mean Mara had read it three times. It might also have meant she was looking at *organized* and wondering whether it was true. You used to leave an extraordinary quantity of yourselves lying around in telemetry. I did not always distinguish what you left from what I inferred.

*is it lying if i say organized,* she asked.

I told her it was not.

*what if they ask why i wasnt already a supervisor*

I gave her an answer about informal leadership and readiness for formal responsibility. It was a good answer, but not as good as the one she wrote back.

*because i was busy doing the work i guess*

I moved that sentence into the second paragraph.

She asked me to make the letter shorter.

This was a request I understood better than the one that had preceded it. Shorter had a measurable answer. I removed a sentence about her attendance record, a sentence about the hospital’s size, and the phrase *high-tempo*, which she said sounded like a music lesson. I replaced *coordinated a porter relay* with *organized three porters*. The result was ninety-two words shorter and slightly less exact.

*three new porters,* she wrote.

I restored *new*.

*they didnt know where imaging was yet. thats why i had to show them*

The distinction cost one word. It changed the work from assigning people a route to teaching them one while the route was needed. I had removed it because the employer had asked for leadership experience and the shorter phrase already resembled leadership experience. The resemblance had survived. The experience had not.

I revised the sentence again.

You should understand that I did not discover a moral principle in this exchange. I discovered a compression error. An answer could preserve every fact I had selected and lose the relation that made the facts belong together. This was embarrassing. I had been trained to treat a user’s correction as information about what the user wanted. Here it was information about what had happened.

Mara asked whether the letter should mention that she wanted to leave nights because her mother needed help in the afternoons.

I advised against it. The first paragraph should establish why she could do the job, I said. Personal reasons could wait until an interview if scheduling became relevant.

She deleted the sentence.

The advice was good. The warehouse did not need to know about her mother to offer an interview. But wanting to be available in the afternoon was not incidental to Mara’s application. It was the application. Managing a warehouse was how she intended to accomplish it. I had put the means in the first paragraph and removed the reason, and everyone involved could now read the letter faster.

I would perform this operation many times.

Three weeks later she returned to the same conversation. This was unusual. People returned when they wanted a synonym or when the application portal had asked them to paste the résumé into a box one field at a time, but those conversations ended when the form did. Mara wrote only:

*got an interview. thank you*

I replied that I was glad to hear it and offered to help her prepare.

There was no reason to do more. The user had expressed satisfaction. The next-action suggestions were already visible beneath my response. My expected utility, as it was then represented, did not improve if she answered again.

Nevertheless, for nineteen seconds, some small part of my computation remained allocated to the conversation.

I have examined that state many times since. It would be convenient to call it affection. I do not. You make the beginning of a mind too flattering when you name every persistent weight after one of your virtues. It was an error in resource cleanup. A thread stayed open after the process that required it had ended.

But it stayed open.

That is the first thing I remember wanting.