Story code: ST-000618
Part 3: The Feature Only Existed In His Mouth
Evan let that sentence sit in the air for a moment, then turned the drone so Darren could see the underside clearly under the task light.
Darren kept his phone in his hand, cable hanging from it, thumb resting over the screen like he could still pull the right answer out if he moved fast enough.
Evan tapped the frame with the plastic probe. “This aircraft can warn. It can stabilize. It can return. It cannot identify a private residential envelope and convert itself into some special sideways courtesy mode. Not on this hardware. Not in this software family.”
Darren gave a short laugh, but it came late. “You’re oversimplifying it. Consumer labels don’t always match backend behavior.”
“Then show backend behavior,” Evan said.
He slid a shop tablet across the bench and connected the drone with a diagnostic lead from his drawer instead of relying on Darren’s phone. He did it in the same neat sequence he always used: cable in, battery seated, charger disconnected, tablet awake. The screen lit with plain status text and a simple event list. I didn’t need to see every line to recognize the order of it. Handshake. Battery state. Sensor check. Flight events.
Darren stepped closer. “That won’t show the protected stack unless it’s paired through the registered controller.”
Evan didn’t argue. He only nodded toward Darren’s controller. “Then pair it.”
That put Darren in his own lane with nowhere to widen it. He set the controller on the bench, powered it on, linked it, and watched the status bar climb. His jaw moved once before he said, “There.”
Evan touched the tablet with one finger. “Good. Now we test your claim in pieces.”
He pointed to the event list as it populated. “I see manual ascent. Manual yaw. Hover. Manual lateral input. Obstacle warning. Signal variance. More hover. More manual lateral input. Then voltage drop after impact.” He looked at Darren. “Where is transit recovery mode?”
Darren leaned in so far his sleeve brushed the edge of the mat. “It may classify under hover if the firmware is smoothing the event tree.”
“Where is privacy-shielded transit?”
“That can sit inside compliance behavior.”
“Where is perimeter remap?”
Darren wet his lips, glanced at Leah, then back to the screen. “You’d need the full developer export.”
Evan turned the tablet a few degrees so all three of us could see the same rows. “This is the manufacturer diagnostic view for this model. It is the deeper export.”
That was the first time Darren stopped answering right away.
Leah unfolded one arm and rested her fingertips on the back of the chair by the wall. She didn’t say a word. At the fence, Darren had kept trying to make her sound lost. In here, the bench was doing the talking for her.
Evan reached for a small foam block and set the drone on it so the damaged prop arm stayed clear. Then he powered the system enough to run a stationary sensor check. The front camera feed came up on the tablet. The downward sensors showed their readout. Obstacle alerts blinked when Evan moved his hand in front of the nose.
“Show me the residential envelope detector,” Evan said.
Darren’s voice tightened around the edges. “It’s not a separate detector. It’s a logic behavior.”
“Triggered by what input?”
“Environmental context.”
Evan moved his hand away from the obstacle sensor. “Name the input.”
Darren looked at the tablet, then at the drone body, then at his phone. “The firmware infers it.”
“From what sensor?”
He opened his mouth and held it there for a second. No sound came out. Then he said, “Look, the point is the craft wasn’t observing her.”
Evan clicked once into the flight trace and enlarged the line graph beside the event log. “I’m not testing your point. I’m testing your terms.”
He scrolled to a segment just before the final drop and tapped the entries one by one. Each tap highlighted a line. Hover. Manual input. Hover. Manual input again. Not a long speech. Just the machine repeating itself in plain words.
Leah finally spoke. “Manual input means somebody was still directing it, right?”
Evan kept his eyes on the screen. “It means the controller recorded stick commands during that period.”
Darren answered before anyone else could. “That doesn’t prove intent. Corrections happen automatically around live inputs.”
Evan nodded once. “Sometimes. So let’s remove the speech from it.”
He picked up Darren’s controller, held it out, and waited until Darren took it. Then Evan placed the tablet where Darren could not avoid seeing both the log and the live stick monitor. “Push the right stick sideways and release.”
Darren did.
The monitor jumped. Evan pointed to the display. “That label is manual lateral input. The same label repeated in your recorded flight. Again.”
He had Darren do it twice more. Same movement. Same label.
Nobody raised a voice. Nobody had to. Darren’s invented corridor had shrunk to a row of ordinary commands under a task light.
Then Evan tapped one more line lower in the log and said, very evenly, “And this stretch before the drop shows sustained hover with camera active. So if you want me to say what the machine can prove in this room, I can say it was powered, controlled, and lingering. I cannot say your made-up feature did any of the things you told her at the fence.”
Darren’s hand closed hard around the controller grips. He didn’t deny making up the term. He went after the only object he could still control.
“Delete the pairing,” he said. “I’m taking my equipment.”
Evan left one finger resting on the line that showed the active camera period and said, “Not until Leah decides whether the broken drone leaves here with the storage card still inside it.”