Chapter Thirty-Nine — Wade
May came warm and fast.
The blossoms were gone and the trees were full green and the valley was in the specific productive beauty of late spring, everything growing at once, the agricultural fields deep green where they'd been brown and the sky a blue that had no hedging in it, just straight clear California sky all the way to the horizon.
Nora ran longer in the mornings now. Five miles sometimes, occasionally six.
She came back from the long runs with the look she had when the run had given her something significant, not just miles but thought, and she'd sit at the kitchen table for ten minutes before she opened the laptop, drinking coffee and looking at something I couldn't see that she was working through.
On a Thursday morning she came back from a six-mile run and sat at the kitchen table and said: I want to expand the monitoring protocol.
I said: Expand how.
She said: The quarterly review is the right interval for formal reporting.
But I've been thinking about what continuous monitoring could look like at a deeper level.
Not just flagging anomalies. Building a predictive model based on the compound's historical transaction patterns so that the system can identify not just what's wrong but what the risk of something going wrong is before it happens.
I said: That's a different kind of tool.
She said: Yes. It would take time to build correctly. A few months of historical modeling and validation before I'd trust it operationally. But if it works the way I think it will, the compound would have the earliest possible warning on anything that could become a problem.
I said: What do you need to build it.
She said: Darren's full historical records going back as far as they go. Time to do the modeling work. A period of parallel running where the model and the manual protocol run simultaneously so I can validate the outputs.
I said: Take it to Kale.
She said: I'm going to. I wanted to tell you first.
I said: Why.
She said: Because I build things for the compound and you're the compound in the specific way that matters to me. She held her pen. That's not professionally accurate. You're a member of the compound, not the compound itself.
I said: I know what you meant.
She said: I know you know. I'm being precise.
I said: You're always precise.
She said: I'm trying to be accurate about something that isn't easy to be accurate about, she said. Which is that when I'm building something for the compound I'm building it with you in mind. Not instead of the compound. In addition to it. You're in the calculation.
I held her eyes.
She said: That's the accurate statement. You're in the calculation.
I said: I know.
She said: Good. She picked up her coffee. I'm going to find Kale after breakfast.
She found Kale at ten. He heard the proposal and asked three questions and wrote two things on his legal pad and said: Darren will give you the historical records today. He looked at her. How long to build it correctly.
She said: Three months to the parallel validation phase. Another month of parallel running before I'd recommend deploying it as the primary system.
He said: Four months.
She said: At minimum. I won't rush the validation.
He said: Good. He wrote something. Don't rush it.
She said: I won't.
He looked at his legal pad. You're building something the compound will use for a long time.
She said: That's the idea.
He nodded. Then: When it's done I want you to present it to the full table. Not a report. A presentation. The table should understand what it is and how it works.
She said: I can do that.
He said: Good.
She came back to the meeting room and sat down and opened the laptop.
I said: Four months.
She said: Minimum. She looked at the screen. It's the right tool and it needs to be built correctly or it's not worth having.
I said: I know.
She said: I know you know. She paused. I'm going to be deep in this for a while. The modeling work is intensive. I might be harder to reach during the build phase.
I said: I'll be at the gate.
She looked at me. That's not what I mean by harder to reach.
I said: I know. I'm saying I'll be there when you surface. Take the time the work needs.
She held my eyes for a moment. Then she said: That's one of the things.
I said: What things.
She said: The things about you that I put in the folder. She looked at the screen. Knowing when to hold the space open without filling it. She paused. It's in the list in the notebook. Under March.
I said: March specifically.
She said: March fifteenth. The night you said I'll be at the gate and let me take the time the work needed.
I said: I didn't know you wrote that down.
She said: I write everything down. You know this.
I said: I know. I forget how comprehensively.
She almost smiled. Very comprehensively, she said. She opened her first file. Let me work.
I let her work.
Devlin came to find me at the workshop door that afternoon.
He said: Come look at this.
I followed him inside. The engine rebuild he'd been running for two months was nearly complete, the parts laid out with the precision Devlin brought to every rebuild, each piece in its place and ready for assembly.
He said: Tell me what you see.
I looked at the layout. I said: It's complete. Everything's there. Ready to go together.
He said: Look at the sequence.
I looked at the sequence. At the order he'd laid the parts out, which wasn't random and wasn't just the order of assembly. It was the order that showed you the logic of the engine, the way each part related to the next one, the reason the thing worked when it worked.
I said: You laid it out so you can see why it works.
He said: So anyone who looks at it can see why it works. He looked at the engine. Some people lay out the parts in assembly order. I lay them out in logic order. So the person who's going to use this engine understands what they have.
I said: That's more work.
He said: Yes. He looked at me. Some things are worth more work.
I said: You're not talking about the engine.
He said: I'm talking about the engine. He picked up a part and turned it over in his hands. I'm also talking about the other thing, yes.
I waited.
He said: She's building something for the compound that's going to take four months and she's doing it right instead of fast. He set the part down in its place. That's Darren's kind of thinking. Build it to last. Build it so anyone who looks at it can see why it works.
I said: She builds everything that way.
He said: I know. He looked at the engine layout. The compound has good people. He paused. She's good people.
From Devlin that was a complete statement. Not an endorsement, not a welcome, a declaration of category. Good people was the highest thing Devlin said about anyone.
I said: Yeah. She is.
He said: Good. He picked up the next part. You can go. I just wanted you to see the layout.
I went back to the eastern approach and thought about logic order and the reason things worked when they worked, and I thought about a woman under the east window building something the compound would use for a long time, laying out every piece in the order that showed why it worked.
Devlin's kind of thinking.
She'd fit here from the beginning. We'd all just been waiting for her to see it.