"Trucks?" You meet Dom's gaze, maintaining a neutral expression while your system rapidly analyzes what he's implying. The room's atmosphere has shifted, a palpable tension hanging in the air as everyone waits for your response.
[Warning: Criminal Activity Discussion]
[Legal Risk Assessment: Severe]
[Crew Trust Test: In Progress]
"I'm listening," you say carefully, "but I'd need details before committing to anything. What exactly are we talking about here?"
Dom nods slightly, apparently approving of your measured response. He gestures for everyone to gather closer around the table, his voice dropping to a near whisper despite being in his own home.
"Electronics. High-end stuff being transported from manufacturers to distribution centers." His fingers trace a route on a map of Southern California's highways. "Three-man driving teams, semi-trucks worth millions in merchandise. Minimal security, just the driver and sometimes a passenger."
Your system immediately projects potential scenarios, calculating risk factors and success probabilities:
[Highway Heist Analysis]
[Success Probability: 64%]
[Critical Failure Points: 3]
[Required Skills: Precision Driving, Vehicle Manipulation, Timing]
"We've been tracking patterns," Jesse adds, spreading out another set of papers. "Same routes, same times. Corporate efficiency makes them predictable."
"And vulnerable," Leon finishes.
Letty's eyes haven't left you. "We don't usually bring new people into this kind of operation. It's family only."
"Which is why we're discussing it," Dom counters. "After tonight, I think we've established Michael has earned consideration."
You process everything, conscious of the line you're about to cross. Street racing exists in a gray area, but highway robbery is unambiguously criminal. Your system offers multiple response options, but this decision feels too important for algorithms.
"I have concerns," you say finally, earning a raised eyebrow from Dom. "Not about trust, but execution. Have you considered the angles, the approach vectors, the driver response variables?"
Dom's expression shifts from surprise to curiosity. "We've run it through scenarios. Vince and Leon approach from behind while I pull alongside—"
"That creates a predictable pattern," you interrupt. "Commercial drivers are trained for hijacking attempts. The moment they see the standard approach, they'll radio for help."
The room falls silent as you stand and begin rearranging items on the table to demonstrate.
"The key is unpredictability. You need to appear, execute, and vanish before they process what's happening." You position a salt shaker as the truck. "Standard procedure is to block from behind and force a slowdown." You move a beer bottle behind the salt shaker. "That's exactly what they're trained to watch for."
Your hands move with precision as your system calculates optimal vectors. "Instead, approach from multiple directions simultaneously. Create confusion, not confrontation."
[Tactical Analysis: Highway Interception]
[Optimal Approach: Triangulation]
[Required Vehicles: 3]
[Success Probability with Modification: 83% (+19%)]
"And how exactly do we get into a moving truck?" Vince challenges.
You smile slightly. "That's where my particular skills come in." You demonstrate with household objects, showing a maneuver that would allow access to the truck's cabin through its blind spot. "The driver won't see it coming until it's too late."
Dom watches with growing interest. "What you're suggesting requires precision driving beyond what most of us can manage."
"I can do it," you say simply. "And I can teach you the basics. Between your instincts and my... perception, we can make this work."
Letty crosses her arms. "Sounds like you've done this before."
"I haven't," you admit. "But I can see it—all the variables, all the possibilities. It's like having run the simulation a thousand times before we even start."
Dom stands, circling the table as he considers your proposal. "Higher success rate, lower risk of injury, better chance of clean getaway." He nods slowly. "I like it. But this isn't a solo call."
He looks around at his crew—his family. "We vote. All in favor of bringing Michael into the operation and adjusting our approach?"
Jesse raises his hand immediately. Leon follows after a moment's hesitation. Vince reluctantly lifts his hand, muttering something about "showing off." All eyes turn to Letty.
"This goes south, it's not just tickets and impound fees," she warns. "This is federal time."
"It won't go south," you assure her. "Not with proper planning and execution."
She studies you for a long moment before slowly raising her hand. "But we do this my way if anything feels off. No questions asked, we abort."
"Agreed," Dom says. "It's settled then. We start prep tomorrow." He extends his hand to you. "Welcome to the real family business."
As you shake his hand, your system updates:
[Mission Accepted: Highway Electronics Heist]
[Relationship Status: Dom's Crew - Inner Circle]
[Warning: Criminal Activity Escalation]
[Reminder: This Universe Has Consequences]
Later that night, as the crew disperses to their respective rooms and you're left alone in the guest bedroom, you contemplate what you've committed to. Your system quietly calculates odds and projections in the background, but a deeper question forms in your mind—one the system can't answer.
In your old life as Mark, you played Grand Theft Auto for the freedom it represented, the consequence-free exploration of a darker self. But this is real. These are real people, real risks, real prison sentences if things go wrong.
You stare at your reflection in the window, Los Angeles glittering beyond. "What am I becoming?" you whisper to yourself.
[Philosophical Question Detected]
[No Data Available]
[Processing...]
[Suggestion: Define Your Own Parameters]
As dawn approaches, you make a decision. You're in this world now, playing by its rules, but you'll do it smart. You'll use your abilities to minimize risk—not just to yourself, but to this newfound family.
Dom knocks on your door as the first light breaks. "Get some sleep. Tomorrow we start planning for real."
"Dom," you call as he turns to leave. "One thing. No violence. No one gets hurt. That's my condition."
He pauses, then nods once. "That's always been the rule. We're thieves, not killers." He studies you for a moment. "This isn't a game, Michael. Once we do this, there's no going back to whatever normal was before."
"I know," you reply. "Normal was overrated anyway."
As Dom leaves, your system finalizes the mission parameters:
[Primary Mission: Highway Heist]
[Secondary Objective: Protect Crew Safety]
[Personal Directive: Maintain Moral Boundaries]
[Next Phase: Detailed Planning and Preparation]
Reconnaissance and Revelation: Truth on the HighwayPrompt: : Write the next segment with the best option without further confirmation
"We need intel," you announce at the morning briefing, spreading a map across Dom's garage workbench. "Not just schedules and routes. We need to understand the drivers, their habits, their responses to road conditions."
Dom nods slowly, considering your words. "What exactly are you suggesting?"
"A reconnaissance run. Not just watching from afar—we need to interact with these trucks in non-threatening ways to gauge reactions." Your system calculates optimal approaches as you speak. "Think of it as a practice run without the actual heist."
Vince scoffs. "So we're gonna what, drive alongside them and wave?"
"Something like that," you reply with a slight smile. "We stage a series of controlled encounters—a car with engine trouble, a near-miss lane change, a vehicle pacing alongside. We document every response, every radio call, every evasive maneuver."
Your HUD displays a real-time tactical simulation, showing various approach vectors with color-coded risk assessments.
[Reconnaissance Approach]
[Risk Level: Minimal]
[Intelligence Value: High]
[Secondary Benefit: Crew Coordination Training]
"I like it," Dom says finally. "Smart to test the waters before diving in." He turns to the crew. "Jesse, I want traffic patterns for the last six months along the target routes. Leon, get us police scanner coverage for those areas. Letty, we'll need the cars prepped but looking ordinary—nothing that stands out."
"What about me?" Vince asks, arms crossed.
"You and I will run point on the first interaction," you tell him, surprising everyone, including yourself. "I need someone with quick reflexes and who can sell a performance."
Vince's hostility visibly diminishes at the recognition of his skills. He shrugs, trying to appear indifferent. "Whatever man, I'm in."
By afternoon, you're on the road. Jesse's research identified three trucks making runs today that match your target profile. Your system continuously updates with traffic data and potential interception points.
[Target Acquired]
[Truck Model: Freightliner Cascadia]
[Driver Profile: Unknown]
[Optimal Interception: Highway 10, Mile Marker 54]
"Target's approaching," you inform Vince through your earpiece. You're positioned at an on-ramp in an unassuming sedan, while Vince waits half a mile ahead in a pickup truck.
"What exactly am I doing again?" Vince grumbles.
"Just merge normally, then gradually slow down with your hazards on. Make it look like engine trouble. I want to see how the truck driver reacts to a vehicle in distress."
"This is stupid," Vince mutters, but follows instructions.
You watch as Vince executes the maneuver perfectly. The truck driver initially maintains speed, then signals and changes lanes smoothly to avoid Vince's apparently troubled vehicle. No radio call, no unusual reaction.
[Data Recorded]
[Driver Response: Standard Evasion]
[Communication: None Detected]
[Threat Assessment: Minimal Awareness]
Over the next six hours, your crew executes twelve different scenarios with three separate trucks. Each interaction provides valuable data that your system compiles and analyzes. By sunset, you've built a comprehensive profile of driver behaviors.
"They don't radio unless physically threatened," you explain to the crew back at the garage. "Lane changes trigger no special responses. But—" you emphasize, pointing to a particularly telling data point, "—they immediately call in when a vehicle paces them for more than 47 seconds, especially on their right side."
"So we stay under 47 seconds for any parallel approach," Dom concludes.
"Exactly. And they're particularly vigilant at these three points." You circle areas on the map where terrain creates natural bottlenecks. "Probably trained to watch for intercepts there."
Letty leans forward, genuinely impressed. "In one day, we've learned more than in three weeks of previous planning."
As the briefing concludes, your system unexpectedly flags something:
[Anomaly Detected]
[Second Truck Pattern Irregularity]
[Recommendation: Further Analysis]
While the others celebrate with beers, you retreat to a quiet corner with Jesse's laptop, diving deeper into the data.
"Something's bothering you," Dom observes, appearing beside you with a Corona extended.
You accept the beer but don't drink. "The second truck—the blue Peterbilt. Its response patterns were different. Subtly, but significantly."
Dom pulls up a chair. "Different how?"
"More... professional. Tighter lane control, better situational awareness." You run simulations, comparing driver responses. "Almost like—"
"Like they're expecting trouble," Dom finishes your thought, his expression darkening. "Could be coincidence."
"Could be," you agree, but neither of you believes it. "Or it could mean some of these shipments have additional security we can't see."
Dom considers this, taking a slow sip of his beer. "You think we should call it off?"
The question surprises you. Despite all the planning, Dom is giving you veto power—a sign of trust you hadn't expected.
[Decision Point]
[Options: Abort/Proceed with Caution/Gather More Data]
[Crew Trust Impact: Significant]
"No," you say finally. "But I think we need to be selective about our target. The blue Peterbilt is hiding something. Let's focus on the white Freightliner—driver showed the least awareness, most predictable patterns."
Relief subtly crosses Dom's features. "Good call. We can handle this."
Later, as the crew disperses, Jesse approaches with his laptop. "I did some digging into that blue Peterbilt," he says quietly. "Cross-referenced with shipping manifests I... borrowed from their system."
"And?" you prompt when he hesitates.
"It's carrying microprocessors for military applications. The others are just consumer electronics." Jesse shifts nervously. "That truck might have more than just a driver, if you know what I mean."
Your system immediately flags this:
[Warning: Military Connection]
[Risk Level Increased: Severe]
[Potential Armed Security: 87% Probability]
"Does Dom know?"
Jesse shakes his head. "Not yet. Figured I'd tell you first, since you spotted something off."
"Good call," you say, processing this new information. "Let's keep this between us for now. No need to worry everyone until we confirm."
As Jesse leaves, you stare at the surveillance photos, your system highlighting subtle details you missed before—the blue Peterbilt's slightly reinforced bumper, tinted side windows in the cab, non-standard antenna configuration.
[Mission Parameters Updated]
[Target: White Freightliner Exclusively]
[Warning: Truck Company May Have Varied Security Levels]
[Recommendation: Final Verification Before Execution]
You close the laptop, weighing your options. The heist suddenly feels more complex, the stakes higher. Part of you wonders if this is the universe's way of testing your resolve—or offering a way out.
Your phone buzzes with a text from Dom: "Briefing tomorrow 0800. We move in three days."
The countdown has begun. You have seventy-two hours to perfect the plan, prepare the crew, and decide just how far you're willing to go in this new life you've chosen.
[Mission Status: Preparation Phase 70% Complete]
[Crew Readiness: Improving]
[Personal Decision Point: Approaching]