Ficool

Chapter 86 - Chapter 86: The Width of the Brief

Chapter 86: The Width of the Brief

[Sightglass Coffee, 7th Street, SoMa Saturday, September 12, 2015, 10:15 AM]

 

The memo lay flat on the table between three coffees and a cortado nobody had touched. Ethan had printed it at the office at six in the morning. The toner was still warm when he folded it into his jacket. Now it sat between Richard's elbows and Gilfoyle's forearms and the speakerphone Jared had propped against a sugar caddy, and the warm part was over.

 

Richard's fingers drummed the tabletop. Arrhythmic, rapid, the pattern of a man processing a threat before his mouth caught up. He read the memo top to bottom twice. The second pass his lips moved.

 

"Two hundred million," Richard said.

 

"Over eighteen months," Ethan said.

 

"Targeting us."

 

"Targeting revenue. The partnership is adjacent."

 

The fingers stopped. That was the tell Ethan had learned to read over four years of shared architecture. Richard's hands went still when the question became technical. Drumming was social fear. Stillness was engagement.

 

"Adjacent how," Richard said.

 

"Price war on enterprise accounts. Patent overhang on the round. A talent raid when morale dips." Ethan kept the list flat. "None of those require your cooperation to fail."

 

"Then why are we here."

 

"Because the third one works better if you're rattled."

 

Gilfoyle sat with his back to the wall. Sightlines to both exits, the front door and the hallway to the restroom. His coffee was black, untouched, centered on the table with the kind of precision that looked casual if you didn't know him. He had read the memo once and said nothing for six minutes.

 

"The inference pipeline," Gilfoyle said.

 

Richard looked at him.

 

"Under load. The shared channel." Gilfoyle's voice was the same monotone he used for everything. "It's not embarrassing."

 

Richard turned to Ethan. "That's, okay, that means it's good. He doesn't say things are good. If it's not embarrassing, that's, that's a real compliment from him."

 

"I know what it means," Ethan said.

 

He did. The praise scale had been legible to him since the first joint architecture review. Gilfoyle had called a kernel optimization "not stupid" that day, and Richard had spent twenty minutes explaining why that was the nicest thing Gilfoyle had ever said about anyone's code. "Not embarrassing under load" was a rung above "not stupid." It meant the pipeline held when the traffic spiked and the failure modes were graceful. It meant Gilfoyle had tested it already, probably at three in the morning, probably with a load profile he had written himself.

 

Jared's voice came through the speaker tinny and earnest. "I have some questions about incident escalation, if this is a good moment."

 

"It's a good moment, Jared," Richard said.

 

"I organized them by category. There are thirteen. The first category is access logging. When a member of either engineering team accesses the shared architecture channel, is there a named human associated with that access? Because in the current configuration I believe the answer is no, and I'd like to propose that the answer become yes."

 

Ethan looked at the phone. Jared Dunn had been operational at Pied Piper for less than a year. He had already built the kind of process muscle that Gardner's side of the table kept meaning to grow, and never did. Eleven questions, organized, the first one the most important.

 

"Go," Ethan said.

 

Jared went. Access logging, error reporting cadence, on call rotation overlap, shared status page, incident severity definitions, post mortem template alignment, notification chain. Each question landed clean and built on the one before. By question seven Ethan stopped being surprised and started writing them down on the back of the memo.

 

"Question fourteen," Jared said. "Both companies log every access to the shared architecture channel with a named human. Not an API key. Not a service account. A human. Is that agreeable."

 

"Yes," Richard said instantly.

 

"Yes," Ethan said.

 

He said it and then he heard it. A named human on every access meant the log showed who touched what and when. It meant visibility, transparent, bilateral, both sides watching the same stream. It also meant that if someone exfiltrated the curation methodology through that channel, the log would show them doing it. And it would show it to both companies.

 

The log was a trap for a traitor and he had just agreed to it in front of the only two people outside Gardner who would know it existed.

 

"Question twelve," Jared said. "Oh. I only had six. That's fine, then."

 

Gilfoyle reached for his coffee. He picked it up. Took one sip. Set it back down, off center by a centimeter, which was the same as dropping it on the floor for anyone else. Then he pushed it to the middle of the table, a quarter full, and left it there.

 

Ethan watched the abandoned cup. At the end of their first real conversation at Sightglass, Gilfoyle had left a full coffee untouched, the signal that the discussion was over and the relationship was undefined. This was different. A quarter cup, one sip taken, pushed forward. Not finished. Not untouched. Paused.

 

"The thread," Gilfoyle said.

 

"What about it."

 

"Seventeen comments last week. I haven't touched it."

 

The Hacker News thread about impossible hardware. The one that had been accumulating for two years, the one Gilfoyle had built from thermodynamic benchmarks and public GPU specs and a timeline that didn't close. Twenty one new comments. Speculation, argument, a few people doing the math and arriving at questions nobody could answer.

 

"I'm not updating it," Gilfoyle said. "That's not the same as it not existing. Not updating it is a thing I'm doing. Daily."

 

Richard translated without being asked. "He's saying the thread is still live and he's choosing to leave it alone. That's the truce. But he wants you to know it's a choice, not a default."

 

"I understood him," Ethan said.

 

He did. Not updating a thing was also work. Every day Gilfoyle opened the thread, read the new comments, and closed the tab without adding anything. That was effort. That was restraint. The thread had a public address that anyone could find, and it was growing. The only thing keeping it from becoming evidence was one man's daily decision not to make it worse.

 

Ethan looked at the memo. The memo looked back.

 

Four people knew now. Himself, Richard, Gilfoyle, Jared. Sarah and Monica on his side, already briefed. Eighty one people at Gardner did not know. Eighty one engineers and operators and sales reps who would, if they found out Hooli had dedicated two hundred million dollars to killing their company, start updating résumés. And some of them, not many, but some, would be right to.

 

The narrow brief. Four people, not eighty five.

 

He could feel both sides of it. The narrow brief kept the raid surface small through Q4. The wide brief kept everyone informed and made the raid trivial. There was no version of this where he got both.

 

"Nobody else at Gardner knows," Ethan said. "Nobody else at Gardner is told. That's the call."

 

Richard's fingers stayed still. He was engaged. "And if someone finds out from someone who isn't you."

 

"Then they find out from someone who isn't me."

 

"That's not an answer."

 

"It's the only one I have."

 

Gilfoyle stood. He centered his phone on the table, parallel to the edge, equidistant from the two cup rings, and picked up his jacket. The coffee stayed where he had left it. A quarter cup. Paused.

 

"Your pipeline isn't embarrassing," Gilfoyle said to Richard on his way out. "Fix the retry logic on the tokenizer fallback and it's architecturally elegant."

 

Richard stared after him. "Did he just, that's two rungs. He went up two rungs in one sentence."

 

"I heard him," Ethan said.

 

The speaker crackled. "Should I stay on the line for anything else, or is this a natural stopping point? I have the incident protocol drafted. I can send it to both sides by end of day."

 

"Send it," Ethan said. "You own it. Both companies report through you."

 

"Oh," Jared said. "That's, yes. I'll have it by four."

 

The line went dead. Richard folded the memo in half, then in half again, and put it in his jacket pocket. His fingers were still. The friendship was not repaired. That was not what this meeting was for. But the partnership now had a protocol, a coordinator, and a shared log that named humans.

 

Ethan walked out to the sidewalk. Gilfoyle was already gone. Richard was walking south, head down, the memo in his pocket and the retry logic already running behind his eyes.

 

The cortado remained on the table. Nobody had touched it. He had ordered it for Gilfoyle, who had ordered his own coffee before Ethan sat down, and neither of them had mentioned it.

 

He left it there.

 

The log would show every access. Every named human. Every touch on the shared architecture channel, timestamped, bilateral. If someone moved the curation methodology through that pipe, the log would catch them, for both companies. Whatever it found would be visible to the people he had just decided to trust, and to the people he had not.

 

Four people knew. Eighty one did not. He had chosen the narrow brief on the record, in front of witnesses who had reason to disagree. The only one who had pushed back was Richard, and Richard's fingers had gone still.

 

The sun was out. September in SoMa. The Honda was four blocks away because the lot next to Sightglass charged twelve dollars on Saturdays.

 

Twelve dollars.

 

He walked.

More Chapters