Story code: ST-000618
Part 2: He Walked Into The Wrong Room Still Talking
By the time Darren Pike came into Evan Cho’s workroom, he had arranged his face back into that same patient look he’d used at the fence, like the rest of us were about to be educated. He carried the controller in one hand, his phone in the other, and kept talking before the door finished closing behind him. Leah came in with the drone wrapped in an old dish towel, not because it deserved care, but because she didn’t want his broken propeller scraping her car seat. I was already inside at the side bench sorting small screws into a tray when Evan cleared a space under the task light. Evan’s room is narrow and bright, all bench surface and labeled drawers, with a rubber mat where he sets anything damaged. He doesn’t rush. He puts objects down in an order that tells you what matters. When Leah handed him the drone, he unfolded the towel, laid the machine on the mat, and set the loose battery to the left of it. Darren started in immediately. “Before we waste time, the issue here is that Leah is treating a compliance rebound like intentional hovering. The flight path should show privacy-shielded transit, and probably a perimeter remap after geofence bounce.” Evan looked at the drone first, not Darren. “Power event before impact?” Darren opened his mouth, then lifted the controller. “The app has the log.” Evan held out one hand, palm up, without changing expression. “We’ll get to the app. I asked about the power event.” There was a short pause. Darren shifted the controller from one hand to the other. “It was still responsive when it dropped.” Leah stood near the door with her arms folded, not interrupting him this time. At the fence he had used every interruption as proof of rank. In here the silences worked differently. Evan pressed the battery release tabs, checked the contact points, then looked at the bent arm and split propeller hub. “Did it strike anything before the yard?” “I don’t know,” Leah said. “I saw it above my fence, then I heard it clip something and land.” Darren gave a quick nod as if that helped him. “Exactly. A rebound.” Evan glanced up. “From what?” Darren moved his phone like the answer was inside the glass. “From a virtual perimeter reaction.” Evan’s eyes stayed on him for one beat longer than usual, then he said, “Show me where this model labels that.” Darren stepped to the bench and opened the app wider. He turned the screen so Evan could see. From where I stood I could make out the usual blocks: battery percentage, signal bars, a tiny map, a scrub line for recorded flight. Darren’s thumb moved fast over the display. “Here,” he said. “This section. It logs protected transitions differently.” Evan didn’t take the phone yet. “Read the label out loud.” Darren looked down. “It’s in the event tree.” “Read the label.” He zoomed in with two fingers. “It abbreviates.” Evan waited. Darren cleared his throat. “It’s the corridor event.” Evan finally took the phone. He held it low under the task light and scrolled once, then once more. “I see obstacle warning, signal variance, manual input, and low-voltage compensation. I don’t see corridor event.” Darren reached toward the phone. Evan angled it just out of reach, not dramatic, just enough to keep the screen steady. “It may only show in export,” Darren said. “The consumer view simplifies it.” That sounded smoother than the words deserved, but less smooth than it had sounded outside. Leah didn’t move. I kept my hands on the screw tray and watched Darren’s pace pick up by half a step. Evan set the phone beside the drone. “All right. Then explain your term without the app. What is privacy-shielded transit on this model?” Darren smiled again, though this one took longer to arrive. “It’s when the craft recognizes a private residential envelope and converts observational posture into compliant lateral passage.” The room got very still after that. Evan didn’t react the way most people would. No laugh, no argument. He just pulled a legal pad toward himself and wrote the phrase down exactly as Darren had said it. Then he asked, “Which sensor handles that conversion?” Darren answered quickly. “The optical stack.” Evan nodded once. “Which one.” Darren’s fingers tapped the controller casing. “The integrated one.” Evan turned the drone carefully and pointed with a small plastic probe, not touching the broken arm. “This model has downward vision sensors, front obstacle sensing, GPS, and IMU. Show me the hardware you’re talking about.” Darren leaned over the bench. He pointed first near the front camera, then hesitated and shifted lower. “It’s not a single component. It’s a managed behavior.” “Managed by what?” Evan asked. “The firmware.” “Using what input?” Darren opened his hands, closed them again, and looked at Leah as if her presence had complicated a simple lesson. “You’re making this sound more exotic than it is.” Evan slid the drone a few inches closer to the center of the mat. “No. I’m making you map your words to the machine.” That landed harder than anything loud could have. Darren stopped moving for a second. Then he reached for his phone again. “I can export the deeper log,” he said. “That’ll show the corridor break and the remap.” Evan handed the phone back to him. “Do that.” Darren took it, plugged in a cable from his controller case, tapped through three menus, then two more. He frowned at the screen, backed out, and went in again. The room stayed quiet except for the soft plastic click of the battery as Evan set it into a charger cradle to see if it would handshake at all. After almost a minute, Darren said, “This app version may not expose it directly.” Evan looked at the charger indicator, then at the drone, then at Darren’s phone. “Interesting,” he said. “Because this model also doesn’t support the feature you’ve spent.