February 1998, Cambridge
The snow outside had turned from powder to glass. Each morning the sidewalks cracked under boot heels like static, and the Charles wore a crust of ice thick enough to hold yesterday's footprints but too thin to trust.
Inside the dorm lounge, space heaters hummed under the tables while half awake students typed with gloves on. Stephen had claimed a corner sofa, laptop balanced on one knee, cables snaking to a router he wasn't technically supposed to borrow.
On screen, Backline 2.0 looked less like code and more like a working idea. The new Signal View dashboard had finally stabilized, handling multiple locations without collapsing. The active registry had climbed to twenty-two live sites since the New Year shift, the steady intake of nightly logs pushing the localized routing scripts near their processing limits as word of mouth spread beyond the primary Texas and Cambridge connections.
The lounge door opened, letting in a draft and two undergrads carrying laptops larger than their backpacks.
"Mr. Cooper."
Stephen looked up. "You make me sound like a substitute teacher."
The girl, Leah Vance, sophomore, database compression, grinned. "We wanted to sound respectful before breaking something."
Her partner, Omar Alvi, math minor, saluted with his floppy disk. "Intern orientation."
Paige walked past with a stack of binders under her arm. "Boss man now."
"Two interns doesn't make a company."
"You hired them. Congratulations, you're management." She stopped at the coffee machine. "Try not to union-bust."
Leah and Omar laughed. Paige gave a mock salute and disappeared down the hall toward her own lab.
Stephen turned back to the interns. "Let's make something worth the rent."
"You pay rent," Omar said.
"Figure of speech. Let's work."
They spread out across two tables. Leah dove into compression testing to handle the expanding database files. Omar debugged the time tracking module. Stephen rewrote a query that had been eating memory for no defensible reason. The hum of three laptops filled the silence better than conversation would have.
Around eleven, Omar held up a printout with a confused expression. "Why does the schedule page think Tuesdays are cursed."
Stephen leaned over to check it. "It's not cursed. The weighting from the diner pilot bled into the general template before I split the configs apart. Tuesdays got Darlene's slow-day pattern by mistake."
"That's almost more interesting than if it were actually cursed."
"It's less interesting. It's just a copy error."
"Everything's more interesting with a curse attached," Omar said, already typing the fix. "You're bad at marketing."
"I'm aware."
Leah, without looking up from her own screen, added, "He really is."
"Thank you both," Stephen said, "for the unsolicited audit."
Between lines of code, Stephen read incoming data lines in the feedback_metrics folder.
Inventory actually makes sense now. Twenty five percent fewer mistakes. Still can't find my wrench.
That fancy register told me I was out of eggs before breakfast. I married the wrong kind of genius.
Proof somebody actually used the thing daily enough to send raw terminal updates was better than steady invoice clearing.
By noon the heater clanked off and the silence stretched. Leah looked up. "Are we allowed to call you Steve."
"Stephen."
"Got it. Stephen. Boss."
"If you break something, call me sir. Otherwise first name's fine."
Omar smirked. "You realize you just made titles conditional."
"Welcome to software."
That afternoon his inbox pinged with a message from Hwang. Subject line: consultation request, behavioral data modeling. A study on decision making under pressure, her note said, your prior modeling work would be useful, stop by tomorrow at ten if interested.
He typed back two words. Interested. See you then.
Paige passed his desk that night, notebook under her arm. "You look like someone just got homework they secretly wanted."
"Hwang wants me to consult on a behavioral data project."
She arched a brow. "Quantico's circling early."
"Probably coincidence."
"Sure. Coincidence with a federal letterhead."
Hwang's office smelled faintly of tea and dry paper, files stacked with a precision that made the rest of the building look careless by comparison.
"Still keeping the same hours," she asked.
"Trying for something before two a.m."
"Progress." She gestured to a chair. "I've been seconded to a project analyzing decision loops in high stress simulations. They want to quantify hesitation."
"Response lag."
"More specific than that. The gap between instruction and action when something in the operator pushes back against the instruction."
Stephen folded hands. "You want me to build the predictor."
"I want you to tell me if the pattern's real before anyone calls it a predictor. You've built something like this once already. I trust you to remember the difference between detecting a pattern and assuming it means more than it does."
"I remember."
"Good. You'll have anonymized datasets by morning."
The files arrived that evening, rows of timestamps and reaction codes from simulated training environments. The header read Behavioral Sciences Division, Training Metrics.
Paige sat cross legged on his floor, running diagnostics for her own program. "What's it look like."
"Half math, half delay," Stephen said. "Measuring how long it takes someone to act once they're given an instruction under pressure."
"Military."
"Could be. The header doesn't say."
"Be careful with this one."
"It's a consulting request. Not a commitment."
"Those start the same way."
Days blurred into code and coffee. Stephen built a model to flag the micro delays between a command and the response to it, the kind of gap that might mean nothing or might mean someone briefly weighed a choice before acting on it. Leah optimized the compression on the side to manage the incoming client data traffic. Omar built a visualization script that rendered each decision as a spike on a line.
When the first graph loaded, the peaks looked uncomfortably like heart monitor output. The higher the stress condition, the longer the delay before response.
Hwang looked over his shoulder at the screen. "You found the lag."
"I found a measurable delay," Stephen said. "I'm not calling it anything more specific than that yet."
"Good distinction to hold onto." She didn't push it further. "Send the model for review when you're satisfied with the error bounds."
He labeled the file Adaptive Gradient v1.0 and sent it.
Backline kept running quietly in the background the whole time. Dale wrote again. This thing's faster than my nephew counting his own paycheck. Darlene left a voicemail for Meemaw bragging that the register sent her shift reports before her second cup of coffee.
Paige caught him replaying it and smirked. "You've automated gratitude."
"I call it a feedback loop that doesn't need me in it."
"Whatever gets you up in the morning."
They met one afternoon in the lounge, her with circuit blueprints, him with the latency graphs.
She looked at the spikes. "These look like your old threshold work."
"Different inputs. Same instinct. Watch for the point where confidence stops meaning what you think it means."
"You're circling the same problem from a different angle."
"Probably."
Hwang called him in the following week with a printed summary. "They're satisfied. The model predicts hesitation with eighty seven percent accuracy on the validation set."
He scanned the page. "High accuracy on a behavioral measure isn't automatically good news."
"I know. That's why I want you to write the limitations section yourself, not me."
"Me."
"You understand what the number can't tell anyone. Write it down so the next person reading this doesn't skip that part."
That was either generous or a deflection of her own discomfort with the project. He didn't ask which. He nodded and took the assignment.
Before he left, she added, "There's a seminar at Quantico this spring. Behavioral analytics track. You might find a few of the presenters familiar from your own footnotes."
"I'll look into it."
She didn't push beyond that.
Back in the dorm, Paige sat on the radiator, watching frost retreat slightly from the window glass.
"How'd the meeting go."
"They're satisfied with the model. I'm writing the limitations section myself."
"Of course you are."
"I might have just volunteered for more work voluntarily, which Eugene would find very on brand."
"You're learning to read yourself a little. That's progress."
"Terrifying, isn't it."
"Less than you'd think." She made room on the radiator without quite saying so. "What's the actual concern. Not the polite version. The real one."
Stephen sat down beside her, close enough that the heat from the radiator reached both of them.
"Eighty-seven percent accuracy looks like a clean optimization target until someone decides that hesitation window is a latency error to be engineered out of the loop instead of a mandatory deliberation threshold."
"That's the part you're writing into the limitations section."
"In fewer words than that, but yes."
"Good. Write it exactly that blunt. Don't soften it for the agency."
"I wasn't planning to."
She nodded, satisfied, and let the quiet hold for a while, the two of them watching the same patch of frost lose its edges by degrees as the building's heat slowly won out over the night outside.
(Thanks for reading, feel free to write a comment, leave a review, and Power Stones are always appreciated. Let me know if you find any mistakes)