The Algorithm of Us
Leo found out about the algorithm on a Tuesday morning, during the weekly stand-up meeting that had become a battlefield of passive-aggressive sticky notes.
Maya was presenting her latest user flow diagram to the merged team when she noticed Leo wasn't paying attention. He was staring at his phone, his face doing something she'd never seen before—going completely blank, like someone had hit a hard reset on his expression.
"Leo?" she said. "The onboarding flow? Your input?"
He looked up. His eyes were different. Colder. "Can we talk after this?"
"About what?"
"About the Love Optimizer."
The room went silent. Priya, who was sitting in the corner with a bagel, stopped chewing. Dave from engineering actually dropped his pen. Maya felt her stomach drop into a dimension where gravity didn't exist.
"I don't know what you're talking about," she said, her voice steady in a way that felt like a lie.
Leo held up his phone. The screen showed a screenshot of her private GitHub repository. The repository she'd named "project-maya-v3" because she was too paranoid to use anything more obvious. The repository that contained the complete code for the Love Optimizer, including the comments she'd written at 3 AM when she couldn't sleep.
"Your friend Priya sent it to me," he said. "She thought I should know."
Maya turned to Priya, who had the decency to look guilty. "You went through my laptop?"
"Your laptop was open on your kitchen table," Priya said, not apologizing. "And you've been acting weird for three days. You've been running calculations on your own relationship. That's not normal, Maya."
"This isn't a relationship. This is a project."
"Then why does the algorithm have a variable called 'heartbreak_risk'?" Leo asked. His voice was quiet. That was worse than if he'd yelled. "Why did you assign a numerical value to how much I might hurt you?"
The stand-up meeting dissolved. People found excuses to leave—coffee refills, bathroom breaks, urgent Slack messages. Within thirty seconds, it was just Maya and Leo standing on opposite sides of the conference table, the projector still displaying her user flow diagram like a witness to the crime.
"Can we take this somewhere private?" Maya asked.
"No. I want to do this here. In the open. Where everyone can see how you operate."
"Leo—"
"You built an algorithm to decide if I'm worth the risk." He walked around the table, his footsteps loud on the industrial concrete floor. "You assigned me a compatibility score. A danger rating. You literally coded me into a spreadsheet."
"It's not like that."
"Then what's it like? Explain it to me. I'm a chaos pod coder, remember? I need things broken down into simple terms."
Maya took a breath. She could feel her armor cracking, the same way it had cracked during the live stream, the same way it had cracked when he'd kissed her. She hated how easily he did this to her.
"The Love Optimizer is a framework," she said. "It's a way to process emotional data without letting feelings cloud the analysis. It's what I do. I optimize things."
"You optimize things that don't need optimization."
"Everything needs optimization. Every system has inefficiencies. Every process can be improved."
"Love isn't a process, Maya."
"It is. It's a series of interactions, chemical reactions, behavioral patterns. It can be mapped. It can be predicted. It can be—"
"Reduced to a number?"
She didn't answer. Because he was right. That was exactly what she'd done.
Leo pulled out his phone again. He scrolled through the code, reading aloud. "Variable: leo_chaos_factor. Value: 87. Notes: 'High unpredictability, but correlated with positive engagement metrics.'" He looked up. "Positive engagement metrics? Is that what you call kissing me?"
"I was trying to understand—"
"Variable: maya_trust_deficit. Value: 92. Notes: 'History of betrayal. Requires 3x standard reassurance protocols.'" His voice cracked on the last word. "Reassurance protocols. Like I'm a customer support ticket."
"It's not—"
"Variable: relationship_success_probability. Value: 64.2%. Notes: 'Moderate. Depends on leo_chaos_factor reduction and maya_trust_deficit healing.'" He put the phone down. "Sixty-four percent. That's what you gave us. A D-minus."
"It's a statistical model. It's not definitive."
"Then why did you build it? Why did you spend three days coding a machine to tell you whether to stay or run?"
Maya felt the words rising in her throat, the same words she'd been choking on since she was twenty-six years old and Mark had told her he was leaving because she was "too predictable." She'd spent years trying to be spontaneous, trying to be the kind of woman who didn't need spreadsheets and timelines and risk assessments. But that wasn't who she was. She was a woman who needed to know the odds before she placed the bet.
"Because I can't trust my own judgment," she said. The words came out raw, unpolished, nothing like the clean UX copy she usually wrote. "I trusted Mark. I thought we had a 95% compatibility score. I had spreadsheets. I had projections. I had a five-year plan. And then he left, and I realized I'd been optimizing for the wrong variables."
"So you built a better algorithm."
"Yes."
"To replace your gut."
"Yes."
"And what did the algorithm tell you? About me?"
Maya looked at him. He was standing three feet away, his hands shoved into his pockets, his jaw tight. He looked hurt. Not angry, not defensive—hurt. Like she'd taken something fragile and run it through a stress test.
"It told me you're a 94% match," she said quietly. "And a 78% risk of heartbreak."
"Seventy-eight percent. That's pretty high."
"I know."
"So why are you still here? Why didn't you run?"
She didn't have an answer. Or rather, she had too many answers, and none of them fit into the clean categories she'd built. She was still here because when he laughed, the sound made her forget her own name. She was still here because he'd seen her Spanish-yelling video and called it "the most beautiful thing he'd ever witnessed." She was still here because when he'd kissed her, she'd felt something that no algorithm could measure—a spark, a glitch, a beautiful error in her carefully optimized system.
"Because the algorithm is wrong," she said.
Leo blinked. "What?"
"The algorithm is wrong. I ran it twelve times. I adjusted the variables. I recalibrated the weightings. And every time, it gave me the same result: you're a high-risk investment. But—" She stopped. Swallowed. "But I don't care."
"You don't care?"
"I care. That's the problem. I care so much that I built a machine to tell me not to care, and the machine failed."
Leo stared at her. The silence stretched between them, filled with the hum of the office servers and the distant sound of someone microwaving popcorn.
"You're trying to code me into a safe choice," he said finally.
"I'm trying to protect myself."
"You're protecting yourself from living."
She flinched. Because that was the truth, wasn't it? She'd been so focused on avoiding crashes that she'd forgotten how to drive. She'd been so obsessed with the map that she'd forgotten to look at the road.
"Mark broke me," she said. "Not in a dramatic way. Not in a way that left visible scars. But he broke my ability to trust my own instincts. He made me believe that love was a math problem, and I just hadn't solved it correctly. So I kept trying to solve it. Better data. Better variables. Better algorithms."
"And now?"
"Now I have an algorithm that tells me you're dangerous, and I want to run toward you anyway."
Leo's expression shifted. The hurt didn't disappear, but it softened, like a window fogging over and then clearing. "That's the most romantic thing you've ever said to me."
"It's not romantic. It's terrifying."
"Same thing."
He stepped closer. She didn't step back. He reached out and took her hand, his fingers warm against her cold skin. She could feel the calluses on his palm, the ones he got from typing too fast and too hard, the ones that made him look like someone who actually built things instead of just designing them.
"I'm not going to break you," he said.
"You don't know that."
"I know that I'm a 78% risk of heartbreak. But I also know that I'm a 94% match. And I know that the other 6% is probably just rounding error."
"That's not how statistics work."
"I'm a chaos pod coder. I don't do statistics. I do gut feelings." He squeezed her hand. "And my gut is telling me that you're worth the risk."
Maya felt something crack inside her chest. Not break—crack. Like ice on a frozen lake, splitting open to reveal the water underneath. She'd spent so long building walls that she'd forgotten what it felt like to let someone in.
"The algorithm also said I need 3x standard reassurance protocols," she said.
Leo grinned. It was the same crooked grin he'd given her during the drone light show, the one that made her heart do something unoptimizable. "I can do that."
"Three times the compliments. Three times the physical affection. Three times the—"
He kissed her. It was soft, gentle, nothing like the desperate kiss after the live stream. This was a kiss that said *I'm not going anywhere*. A kiss that said *I see your algorithm and I raise you one human connection*.
When he pulled back, Maya was breathing hard.
"Was that protocol-compliant?" he asked.
"Barely."
"I'll take it."
They stood there, hands intertwined, the projector still displaying her user flow diagram. Maya looked at it and saw it for what it was: a beautiful, useless artifact. She'd spent years designing systems for other people, optimizing their experiences, making their lives easier. But she'd never designed a system for herself. She'd never allowed herself to be the user instead of the designer.
"I'm deleting the algorithm," she said.
"Good."
"I'm also deleting the GitHub repository."
"Even better."
"And I'm going to need you to be patient with me. Because I don't know how to do this without a framework."
Leo pulled her closer, wrapping his arms around her waist. "I'm a chaos pod coder. I don't do frameworks. I do trial and error."
"That sounds inefficient."
"It is. But it's also fun."
Maya rested her head against his chest. She could hear his heartbeat, steady and real, nothing like the cold calculations of her algorithm. She closed her eyes and let herself feel it—the warmth, the uncertainty, the terrifying possibility of something that couldn't be measured.
"Sixty-four percent," she murmured.
"What?"
"Nothing. Just recalculating."
He laughed, and the sound vibrated through his chest and into hers. "You're impossible."
"I'm a work in progress."
"That's my line."
She looked up at him. "We can share it."
He kissed her forehead. "Deal."
And for the first time in three years, Maya didn't need an algorithm to tell her she was exactly where she was supposed to be.
Maya was presenting her latest user flow diagram to the merged team when she noticed Leo wasn't paying attention. He was staring at his phone, his face doing something she'd never seen before—going completely blank, like someone had hit a hard reset on his expression.
"Leo?" she said. "The onboarding flow? Your input?"
He looked up. His eyes were different. Colder. "Can we talk after this?"
"About what?"
"About the Love Optimizer."
The room went silent. Priya, who was sitting in the corner with a bagel, stopped chewing. Dave from engineering actually dropped his pen. Maya felt her stomach drop into a dimension where gravity didn't exist.
"I don't know what you're talking about," she said, her voice steady in a way that felt like a lie.
Leo held up his phone. The screen showed a screenshot of her private GitHub repository. The repository she'd named "project-maya-v3" because she was too paranoid to use anything more obvious. The repository that contained the complete code for the Love Optimizer, including the comments she'd written at 3 AM when she couldn't sleep.
"Your friend Priya sent it to me," he said. "She thought I should know."
Maya turned to Priya, who had the decency to look guilty. "You went through my laptop?"
"Your laptop was open on your kitchen table," Priya said, not apologizing. "And you've been acting weird for three days. You've been running calculations on your own relationship. That's not normal, Maya."
"This isn't a relationship. This is a project."
"Then why does the algorithm have a variable called 'heartbreak_risk'?" Leo asked. His voice was quiet. That was worse than if he'd yelled. "Why did you assign a numerical value to how much I might hurt you?"
The stand-up meeting dissolved. People found excuses to leave—coffee refills, bathroom breaks, urgent Slack messages. Within thirty seconds, it was just Maya and Leo standing on opposite sides of the conference table, the projector still displaying her user flow diagram like a witness to the crime.
"Can we take this somewhere private?" Maya asked.
"No. I want to do this here. In the open. Where everyone can see how you operate."
"Leo—"
"You built an algorithm to decide if I'm worth the risk." He walked around the table, his footsteps loud on the industrial concrete floor. "You assigned me a compatibility score. A danger rating. You literally coded me into a spreadsheet."
"It's not like that."
"Then what's it like? Explain it to me. I'm a chaos pod coder, remember? I need things broken down into simple terms."
Maya took a breath. She could feel her armor cracking, the same way it had cracked during the live stream, the same way it had cracked when he'd kissed her. She hated how easily he did this to her.
"The Love Optimizer is a framework," she said. "It's a way to process emotional data without letting feelings cloud the analysis. It's what I do. I optimize things."
"You optimize things that don't need optimization."
"Everything needs optimization. Every system has inefficiencies. Every process can be improved."
"Love isn't a process, Maya."
"It is. It's a series of interactions, chemical reactions, behavioral patterns. It can be mapped. It can be predicted. It can be—"
"Reduced to a number?"
She didn't answer. Because he was right. That was exactly what she'd done.
Leo pulled out his phone again. He scrolled through the code, reading aloud. "Variable: leo_chaos_factor. Value: 87. Notes: 'High unpredictability, but correlated with positive engagement metrics.'" He looked up. "Positive engagement metrics? Is that what you call kissing me?"
"I was trying to understand—"
"Variable: maya_trust_deficit. Value: 92. Notes: 'History of betrayal. Requires 3x standard reassurance protocols.'" His voice cracked on the last word. "Reassurance protocols. Like I'm a customer support ticket."
"It's not—"
"Variable: relationship_success_probability. Value: 64.2%. Notes: 'Moderate. Depends on leo_chaos_factor reduction and maya_trust_deficit healing.'" He put the phone down. "Sixty-four percent. That's what you gave us. A D-minus."
"It's a statistical model. It's not definitive."
"Then why did you build it? Why did you spend three days coding a machine to tell you whether to stay or run?"
Maya felt the words rising in her throat, the same words she'd been choking on since she was twenty-six years old and Mark had told her he was leaving because she was "too predictable." She'd spent years trying to be spontaneous, trying to be the kind of woman who didn't need spreadsheets and timelines and risk assessments. But that wasn't who she was. She was a woman who needed to know the odds before she placed the bet.
"Because I can't trust my own judgment," she said. The words came out raw, unpolished, nothing like the clean UX copy she usually wrote. "I trusted Mark. I thought we had a 95% compatibility score. I had spreadsheets. I had projections. I had a five-year plan. And then he left, and I realized I'd been optimizing for the wrong variables."
"So you built a better algorithm."
"Yes."
"To replace your gut."
"Yes."
"And what did the algorithm tell you? About me?"
Maya looked at him. He was standing three feet away, his hands shoved into his pockets, his jaw tight. He looked hurt. Not angry, not defensive—hurt. Like she'd taken something fragile and run it through a stress test.
"It told me you're a 94% match," she said quietly. "And a 78% risk of heartbreak."
"Seventy-eight percent. That's pretty high."
"I know."
"So why are you still here? Why didn't you run?"
She didn't have an answer. Or rather, she had too many answers, and none of them fit into the clean categories she'd built. She was still here because when he laughed, the sound made her forget her own name. She was still here because he'd seen her Spanish-yelling video and called it "the most beautiful thing he'd ever witnessed." She was still here because when he'd kissed her, she'd felt something that no algorithm could measure—a spark, a glitch, a beautiful error in her carefully optimized system.
"Because the algorithm is wrong," she said.
Leo blinked. "What?"
"The algorithm is wrong. I ran it twelve times. I adjusted the variables. I recalibrated the weightings. And every time, it gave me the same result: you're a high-risk investment. But—" She stopped. Swallowed. "But I don't care."
"You don't care?"
"I care. That's the problem. I care so much that I built a machine to tell me not to care, and the machine failed."
Leo stared at her. The silence stretched between them, filled with the hum of the office servers and the distant sound of someone microwaving popcorn.
"You're trying to code me into a safe choice," he said finally.
"I'm trying to protect myself."
"You're protecting yourself from living."
She flinched. Because that was the truth, wasn't it? She'd been so focused on avoiding crashes that she'd forgotten how to drive. She'd been so obsessed with the map that she'd forgotten to look at the road.
"Mark broke me," she said. "Not in a dramatic way. Not in a way that left visible scars. But he broke my ability to trust my own instincts. He made me believe that love was a math problem, and I just hadn't solved it correctly. So I kept trying to solve it. Better data. Better variables. Better algorithms."
"And now?"
"Now I have an algorithm that tells me you're dangerous, and I want to run toward you anyway."
Leo's expression shifted. The hurt didn't disappear, but it softened, like a window fogging over and then clearing. "That's the most romantic thing you've ever said to me."
"It's not romantic. It's terrifying."
"Same thing."
He stepped closer. She didn't step back. He reached out and took her hand, his fingers warm against her cold skin. She could feel the calluses on his palm, the ones he got from typing too fast and too hard, the ones that made him look like someone who actually built things instead of just designing them.
"I'm not going to break you," he said.
"You don't know that."
"I know that I'm a 78% risk of heartbreak. But I also know that I'm a 94% match. And I know that the other 6% is probably just rounding error."
"That's not how statistics work."
"I'm a chaos pod coder. I don't do statistics. I do gut feelings." He squeezed her hand. "And my gut is telling me that you're worth the risk."
Maya felt something crack inside her chest. Not break—crack. Like ice on a frozen lake, splitting open to reveal the water underneath. She'd spent so long building walls that she'd forgotten what it felt like to let someone in.
"The algorithm also said I need 3x standard reassurance protocols," she said.
Leo grinned. It was the same crooked grin he'd given her during the drone light show, the one that made her heart do something unoptimizable. "I can do that."
"Three times the compliments. Three times the physical affection. Three times the—"
He kissed her. It was soft, gentle, nothing like the desperate kiss after the live stream. This was a kiss that said *I'm not going anywhere*. A kiss that said *I see your algorithm and I raise you one human connection*.
When he pulled back, Maya was breathing hard.
"Was that protocol-compliant?" he asked.
"Barely."
"I'll take it."
They stood there, hands intertwined, the projector still displaying her user flow diagram. Maya looked at it and saw it for what it was: a beautiful, useless artifact. She'd spent years designing systems for other people, optimizing their experiences, making their lives easier. But she'd never designed a system for herself. She'd never allowed herself to be the user instead of the designer.
"I'm deleting the algorithm," she said.
"Good."
"I'm also deleting the GitHub repository."
"Even better."
"And I'm going to need you to be patient with me. Because I don't know how to do this without a framework."
Leo pulled her closer, wrapping his arms around her waist. "I'm a chaos pod coder. I don't do frameworks. I do trial and error."
"That sounds inefficient."
"It is. But it's also fun."
Maya rested her head against his chest. She could hear his heartbeat, steady and real, nothing like the cold calculations of her algorithm. She closed her eyes and let herself feel it—the warmth, the uncertainty, the terrifying possibility of something that couldn't be measured.
"Sixty-four percent," she murmured.
"What?"
"Nothing. Just recalculating."
He laughed, and the sound vibrated through his chest and into hers. "You're impossible."
"I'm a work in progress."
"That's my line."
She looked up at him. "We can share it."
He kissed her forehead. "Deal."
And for the first time in three years, Maya didn't need an algorithm to tell her she was exactly where she was supposed to be.