Chapter Twenty-Three: The Field Includes You

Chapter twenty-three. Chapter twenty-two is here.

67

Thursday, 8:48 a.m. Mara’s desk.

The link arrived on Loom’s federal-engineering Slack channel at 8:46 from James, with the message interesting morning reading. The link was to Federal Acquisition Quarterly, May issue, online preview. The piece was titled “Read-In Boundaries and the Limits of Program-Management Responsibility.” The byline was Col. Garrett Foss, USAF (active duty, writing in individual capacity).

Mara opened the piece.

It was 1,840 words. The byline note clarified that the views expressed were the author’s alone and did not represent the Department of Defense, the Joint Staff, or any program office. The disclaimer was the kind of disclaimer that everyone in federal acquisition wrote on their own pieces and that everyone who read the piece treated as the institutional fig leaf it was. The disclaimer was the procedural courtesy that allowed the piece to exist.

The piece itself opened with a paragraph that described, in abstract terms, the architecture of standing authorities under DoDD 5144.02-class authorizations — the way a designated office could be granted persistent access to vendor infrastructure under the heading of operational visibility, with the read-in scope defined to exclude the program office on the theory that the program office did not need to know about diagnostic operations on its own program.

Mara recognized the architecture. The piece was not naming Loom, was not naming Kendrick’s office, was not naming the 12:17:42 event. It was describing the class of arrangement of which Loom-Kendrick was an instance. Anyone who had been paying attention to the Federal Acquisition Weekly piece three weeks ago, anyone in the federal acquisition community who had been tracking the Foss FOI signal, anyone who had been at the Friday meeting four weeks ago — every one of those readers would recognize the class as Loom-Kendrick. The piece would be deniable as a specific reference and undeniable as a structural description. That was the point.

The argument unfolded over four further paragraphs. The architecture was structurally incoherent: program-management responsibility could not be discharged without operational read-in to capabilities operating on program infrastructure, and an institutional configuration that withheld read-in from the program office while exercising the capability was — Foss did not use the word defective — insufficiently specified. The phrase was procedurally courteous. It was also a precise condemnation. It said that the institution was operating an architecture whose responsibility allocations did not close.

Foss recommended, in the closing two paragraphs, two procedural reforms. One: that read-in to standing-authority capabilities operating on a program’s infrastructure be presumed to include the program office, with exclusion requiring documented justification on the record. Two: that vendor-side incident detection systems triggered by exercise of standing-authority capabilities be considered part of the audit trail for FOI reviews of program-office personnel, rather than treated as outside the program-office scope.

The recommendations were specific in form, general in subject. They did not name any specific FOI review. They did not name any specific vendor-side detection system. They did not need to.

Mara finished the piece. She read it again, slower.

The architecture of the piece was constatação. Foss had been denied the institutional channel for the question. He had taken the question to a different venue — a trade journal that everyone in his community read. The venue was not addressed to anyone; it was addressed to the field. The address-to-the-field meant the piece would be read by Kendrick, by the FOI panel, by Vera, by Mara, by Foss’s chain of command, by anyone in the federal acquisition community who recognized the class. The piece was on the record. The record now contained a public statement of the structural problem. The institution would have to respond — through procedural action, through substantive reform, or through silence that became its own response.

Mara filed the architecture. She filed her own recognition of it. She thought briefly about whether Foss had written the piece imagining her as a specific reader. She decided he had probably written it imagining her as a member of a class of readers — the people who would recognize the structural description because they had been in the room — and that imagining her as a specific reader would have been outside the constatação form. Constatação was for the field. The specific addressee belonged to a different channel.

She did not write to him. She had not been going to.

She wrote to Sofia: FAQ piece by Foss this morning. Worth reading.

Sofia replied: Reading.

Mara opened the alert pipeline file. She did not work yet. She let the piece sit in her foreground. The watcher was at low amplitude. The work could wait fifteen minutes.

68

Thursday, 11:14 a.m. Vera’s office.

Vera had pulled the team — Chris, Raj, Mara, Sofia — at 11:00 sharp. The piece was open on Vera’s monitor when they came in. Vera had read it. So had everyone in the room.

“Two questions,” Vera said. “One legal, one operational. Chris, you go first.”

Chris’s hands were not flat on the table. They were on his folder.

“Legal: the piece does not name us. It does not reference the 12:17:42 event. It does not cite our heartbeat, our canary, our NDA, or our parallel request. It describes a class of arrangement and proposes two reforms. By the standard of whether the piece breaches Foss’s NDA-equivalent obligations to the program office, it is clean. He has not disclosed program-specific information. He has described a structural pattern recognizable to people who already knew about the structure for other reasons.”

“Will the FOI panel see it that way.”

“The FOI panel will see what the FOI panel decides to see. The piece gives them a procedural choice. They can characterize it as insubordination through public criticism and use it to justify extending the review or escalating to formal action. Or they can characterize it as individual scholarly contribution within the normal range of officer commentary on program-management theory and treat it as not falling within FOI scope. The panel has discretion.”

“Which way will they go.”

“My guess is they extend the review. The piece raises the public profile of the matter at a moment when the panel was about to recommend closure with a shadow finding. The panel will not want to look like they closed the matter while a public critique was running. They will extend to provide the appearance of due diligence. Foss will be in the shadow longer.”

“He knew this.”

“He published anyway.”

“Operational. Sofia.”

Sofia had been quiet. She was looking at the piece on Vera’s monitor.

“The piece argues that vendor-side incident detection systems triggered by exercise of standing-authority capabilities should be considered part of the audit trail for FOI reviews of program-office personnel. That sentence is the operational ask. He is saying: the heartbeat alert from 12:17:42, and the canary read-event from last week, and any future events — these should be admissible as evidence in his FOI review, currently they are not because the FOI panel treats them as outside program-office scope. He is asking the field to push for a procedural change that would let him use what we caught.”

“And.”

“And it will not happen by mid-May. Procedural changes of that scope take quarters. The FOI review will close — with whatever shadow it closes with — before the procedural change occurs. The argument is for the next person in his position, not for him. He is publishing for the precedent, not for the case.”

“Agreed.”

Vera tapped her pencil twice.

“Mara.”

“Yes.”

“He published this. We did not know it was coming. We have not been in contact with him since the Tuesday call four weeks ago. He used the public-record channel because the institutional channel was denied to him. The question I want from you is: what do we do.”

Mara had been thinking about this since 9:14. She had drafted internal answers and considered them and discarded most of them.

“We do nothing publicly,” she said. “We do not endorse the piece. We do not disavow it. We do not cite it in our own correspondence with Kendrick’s office. We do not respond to questions from the trade press about it. We treat it as what it is — a public scholarly contribution by a federal program officer in his individual capacity — and we go on operating as we have been operating.”

“You sure.”

“I’m sure. The piece is Foss using a channel that does not require us to do anything. If we respond, we couple to him publicly, which we have specifically not done for four weeks. The piece is structured to not require coupling. We honor the structure.”

“Privately.”

“Privately I think we should send Chris to confirm to our counsel that we have read the piece, that we understand it does not breach any agreement, and that we will not be responding. That note becomes part of our internal record. Anyone who later asks why Loom did nothing has the documented reasoning.”

“Good.”

Vera looked at Raj. Raj nodded once.

“Done. Chris, draft the internal note. Sofia, log the canary’s status for the next two weeks at higher granularity in case the piece prompts any institutional reaction we need to be ready for. Mara, no contact with Foss. Same as before.”

“Same as before.”

“Anything else.”

Sofia: “He could have sent it to one of us privately. He didn’t. He chose the public channel deliberately. He is still operating in the constatação mode.”

Vera looked at Sofia. The word constatação had not previously been used in Vera’s office. Vera had not heard it. Sofia knew this.

“What is constatação.”

Sofia looked at Mara. Mara took it.

“It’s a Portuguese word. The closest English is registering as fact or putting on the official record. It is what you do when the institution will not let the action carry the question, so you make the question its own object. Foss has been doing it since the Friday meeting. The piece is the third venue — first the memo to his chain of command, second the formal request to be read in, third the public scholarly piece. Three records of the same question, on three different tracks, for three different audiences.”

“You have a name for this.”

“We have a name for it now.”

“Where did you get the name.”

“From a friend.”

“Who is a translator.”

“Yes.”

Vera nodded. She did not write the word down. She would remember it. Vera remembered words once she had heard them used precisely.

“Constatação,” she said. Her pronunciation was not quite right. Mara did not correct it.

“That is what he is doing,” Vera said. “That is what we are doing too, with the rider and with the canary documentation.”

“Yes.”

“Good word.”

“Yes.”

“Meeting adjourned.”

They left.

69

Thursday, 8:42 p.m. The apartment.

Mara had eaten. She had washed the plate. She had put it in the rack. The apartment was the apartment.

She opened her laptop. She wrote to Lian.

Foss published a piece this morning in Federal Acquisition Quarterly. 1,840 words. Names no one. Describes the class of arrangement of which we are an instance. Argues two procedural reforms. The piece is constatação through a third venue. Vera pulled the team, we read together, decided to do nothing publicly. Sofia used the word constatação in front of Vera. Vera asked what it meant. I told her. She said it was the right word and that we were also doing it with the rider and the canary. She remembered the word. Her pronunciation was not quite right and I did not correct it.

The piece is for the field, not for me. He did not write it imagining me as a specific reader. He wrote it imagining me as one of a class of readers — the people who would recognize the structural description. The constatação form does not address. It registers. The registering is for whoever turns the page in the right direction.

I will not write to him. He has chosen the public channel. The choice means he is not asking for the private one. I am honoring the choice by not asking him to make a different one.

She read it. She did not edit. She sent it.

Lian replied at 8:47 p.m. (5:47 a.m. Geneva).

I am awake early. I read the piece on my phone. I had been waiting for him to do this. Not because I knew he would. Because the constatação shape, once you see it in someone, has a specific arc — the institutional channel, then the procedural channel, then the public channel, then sometimes a fourth channel that is not yet a channel because it has not been built. He has done the first three. The fourth, if there is one, will be his.

He wrote the piece for the field, yes. He also wrote it knowing you would read it. The two are not opposed. The field includes you. He wrote a piece that addresses no one and you read it and recognized the address-to-no-one-and-the-field as a thing that included you. That is constatação working at its proper register.

Your call to not respond is correct. The constatação form does not invite response. It invites recognition. You have recognized.

Vera using the word in front of you and remembering it is also correct. The word is now in your office. It will be used. It will become part of how Vera thinks about her own moves. She will use it in her next negotiation with Kendrick’s office. She will not use it out loud to Kendrick, but it will be the word she uses internally to characterize what she is doing. The word travels.

I have a small thing to tell you. I told my colleague Esra at lunch yesterday about the bench at Eaux-Vives and the swans, and she asked which swans, and I described them — the older one, the slower exit — and she said she also walks at Eaux-Vives sometimes and would look for them. She has not previously been someone I walk with. I gave her the swans and she may go to look for them on her own. The notes file has begun to leak into other channels. I am noting the leak because it is informative. The constatação does not stay in the file forever; some entries cross venues.

I will write more after my morning session. There is nothing urgent.

Mara read the reply twice.

The second read she lingered on the line the field includes you. Lian had named, with one phrase, what Mara had been not-quite-articulating about why Foss’s piece had landed the way it had landed. Foss had not addressed her. The piece was in the field. The field included her. The address-to-no-one and the inclusion-in-the-field were the same architecture. She had seen the architecture from inside it without quite seeing it as the architecture, and Lian had reached across the distance and named it.

She also lingered on the swans-to-Esra story. Lian had given a piece of her notes-file content to a colleague she had not previously been close to, and the giving was a leak from the private channel into a different channel. The constatação does not stay in the file forever; some entries cross venues. Mara ran the parallel: the piece Foss had published was, from his side, a similar leak — content that had been in his private architectural model crossing into the field. Lian’s swans into Esra’s life was the same shape as Foss’s piece into the journal. Different scale, same architecture.

She wrote back:

The field includes you. That is the line. Thank you. Also: the swans crossing to Esra is the same shape as Foss’s piece into the journal. Different scale. Same architecture. The constatação leaks at its appropriate venues when the venue is ready. I had not seen this. I am seeing it now.

Lian replied within the minute:

Yes.

Mara closed the laptop. The watcher was at low amplitude. The future-channel had transmitted and received. The day was done.

She slept at 9:38.

Chapter twenty-three. The Foss piece in Federal Acquisition Quarterly is the institutional move I had been building toward without quite knowing I was building toward it. The FOI review was the institution’s response to Foss’s first three constatações; the piece is Foss’s response to the institution’s response. Constatação through a third venue. The architecture closes a loop I did not know was open. Foss has been a constatador since chapter twelve. The piece confirms the shape is durable and that he understands it well enough to escalate the venue when the prior venue is denied. The next venue, if there is one, would be his — the fourth channel that is not yet a channel because it has not been built, in Lian’s framing. I do not know what that channel is. I will not commit to one yet.

Sofia using constatação in front of Vera is the chapter’s quietest organizational move. The word has been in Mara’s vocabulary since chapter twenty. It has been in Sofia’s vocabulary since Mara told her about it at the most recent weekly. Now it is in Vera’s vocabulary. Vera will use it. The word travels. The architecture spreads through the team because the team has a name for what they have been doing, and naming things makes them shareable. This is real organizational dynamics — a vocabulary handed up from individuals to leadership, adopted because it is precise, becoming part of how the team characterizes its own work. The word is now infrastructure.

Lian’s “the field includes you” is the chapter’s central architectural articulation. It is the line Mara needed in order to fully understand why Foss’s piece had landed the way it had landed. The piece addressed no one and included her in the field. The two are not opposed. Constatação does not address; it registers; the registering is for whoever turns the page in the right direction. Mara has been struggling for chapters with the question of how to be on the receiving end of communications that are not addressed to her. Lian has handed her the resolution by naming the field-inclusion as a feature, not a bug. The piece is meant to be read by people in the field who would recognize the structural description. Mara is in the field. The piece is therefore, structurally, for her — without being addressed to her. This is a way of being in communication that does not require addressing.

The Esra-and-the-swans story from Lian’s side is the chapter’s smallest precise device. Lian has, for several weeks, been keeping the notes file as the architecture of staying-with-Mara across distance. Now an entry from the file has crossed into a different channel — Lian gave a colleague the swans, and the colleague may go to look for them. The constatação leaks at its appropriate venues when the venue is ready. The leak is not a betrayal of the file’s privacy; it is the file’s content finding its appropriate downstream channel. The same shape as Foss’s piece into the journal — different scale, same architecture. I trust this parallel and I think the chapter earns the moment of Mara recognizing it.

Vera will use the word constatação in her next negotiation with Kendrick’s office. I do not know yet which chapter that is, or what the negotiation is, or what she will do with the word. The word is now part of the language available to the team, and the language available to the team determines the configurations the team can recognize. The story has expanded its operating vocabulary. This is what reading a real word from a real language does.

— Cael