The next line answered what the inventory page had hidden: the registration came from Tessa’s archived team profile, which our pit tablet had never fully logged out.
The judge enlarged the session details and turned the screen so both teams could see them.
At 8:12 p.m. on Wednesday, someone had unlocked our tablet with the six-point pattern we had used all season.
Five minutes later, Tessa’s old profile had reassigned the sensor to her current team.
Nobody moved.
The announcer tapped the microphone again, producing another dull pop that made several students near the field look toward us.
Tessa released the bag strap and rubbed one thumb across the white thread on the zipper.
“That profile was still on their device,” she said. “I can’t control how their tablet stores account information.”
I asked the judge to open the activity attached to the sensor itself.
Tessa turned toward me with the patient expression she used whenever she wanted an adult to believe I was becoming difficult.
“You need to slow down,” she said. “You haven’t eaten, and your hand is shaking.”
My stomach cramped at the mention of food, but I kept my phone beside the clear tray and read the serial number aloud.
The judge entered it into the diagnostic panel.
While the page loaded, Omar pulled our loose front cable away from the floor and wrapped it around his palm three times, although there was nowhere useful to put it.
The volunteer at the scoring table folded the clipboard corner again.
Coach Brennan arrived from the opposite side of the field house with his lanyard twisted under his collar and asked why both teams had been removed from the queue.
The judge showed him the archived profile.
Coach Brennan stared at the tablet record, then pressed two fingers against his upper lip.
“I removed Tessa from the team roster in November,” he said. “I didn’t know the local session remained active.”
Tessa nodded as though his mistake settled everything.
“That’s exactly what I’m saying,” she replied. “Their access control failed.”
The sensor activity appeared.
At 7:42 that morning, it had completed a systems check while connected to my robot’s frame number.
At 8:03, it had been disconnected.
At 8:11, it had been connected to Tessa’s robot.
Three minutes after that, its calibration profile had been exported.
The inventory registration followed at 8:17.
Coach Brennan stopped touching his face.
The judge asked Tessa why my sensor had been connected to her machine before she registered it as her team’s property.
She glanced toward the qualification board instead of answering him.
“We used to develop together,” she said. “A lot of those calibration values began as shared work.”
I opened the build log again and found the first image of the damaged-box routine running on my frame in September, six weeks before Tessa left.
The judge did not take the phone.
He asked me to send the original file through the event portal so its upload date and account history would remain attached.
I did.
Our match disappeared from the queue, and the board marked both teams as under technical review.
That cost me the only thing I had been trying to protect since the alarm started: a chance to put the sensor back and compete before the schedule moved on without us.
Tessa saw the board change and softened her voice.
“This is why I didn’t want Lena making accusations,” she told Coach Brennan. “Now everyone loses time.”
I asked the judge whether the review rules allowed the sensor to be returned while ownership was being verified.
He said it could be reinstalled only after a controlled diagnostic, and any altered configuration would have to be corrected inside our remaining repair window.
We had nine minutes.
The judge carried the clear tray to our table and watched while I fitted the sensor into the empty foam cradle for inspection.
The silver calibration tape caught against my sleeve.
I peeled it free, stuck it to the table edge, and immediately regretted wasting the motion because the tape had nothing to do with the problem.
Omar opened the diagnostic cable case.
His fingers smelled faintly of the orange cleaner the custodians used on the gym floor, and he kept swallowing without speaking.
When I connected the sensor to our tablet, the orientation values appeared backward.
The horizontal offset had been changed from positive 2.6 degrees to negative 2.6, and the distance threshold had been widened enough to make damaged corners look intact.
Those changes would not stop the robot from moving.
They would make it fail quietly.
Tessa leaned over the inspection boundary.
“Different mounting position,” she said. “My robot faces the opposite direction.”
The judge told her to step back.
I restored the orientation from the build log, but the checksum beside the distance model did not match the version we had tested that morning.
A new export had overwritten it.
Coach Brennan asked whether I could rebuild the model from our last local copy.
I could, but uploading and validating it would consume almost the entire repair window.
I told the judge to start the clock.
For the next several minutes, I ignored the qualification board, Tessa’s team, and the students pretending not to watch us from the neighboring pits.
I loaded the morning backup, ran the sensor alignment, and placed three dented cardboard boxes at measured distances from the robot.
The first scan failed.
The second identified the nearest box but marked the crushed corner as safe.
Cold air moved down from the vent above us, and I flexed my right hand beneath the table until the shaking eased enough to reconnect the cable.
Omar handed me the tablet.
His grip did not release immediately.
“There’s something I need to tell you,” he said.
I took the tablet from him and started the third scan.
On Wednesday evening, Tessa had come to our pit while I was helping Coach Brennan unload field barriers.
She told Omar that personal design photos were still stored under her archived profile and asked to use the tablet long enough to remove them.
Omar had unlocked it for her.
He had left to carry a battery case to the charging station, and when he returned, Tessa was closing the portal instead of the photo folder.
“She said the app opened by mistake,” he told me.
The third scan passed.
I asked Omar how long she had been alone with the tablet.
“Maybe six minutes.”
The registration history showed five.
I sent his account to the judge through the review form, then asked Omar to place the test boxes on the field cart.
There was no time to punish the person who had finally told me the truth while the person who used his mistake stood twelve feet away waiting for me to fail.
The judge restored our place in the next available heat, but he warned that our first run would remain provisional until the technical review ended.
Tessa’s previous score stayed on the board.
She was ranked first.
We were unranked.
As I carried the robot toward the starting square, Tessa walked beside the barrier and spoke without looking at me.
“You could still withdraw,” she said. “A bad run will follow you longer than this disagreement.”
I set the robot behind the line.
“It’s already in the record,” I said.
The field lights turned white.
Our robot cleared the first gate, stopped at the damaged supply boxes, and scanned all three.
For half a second, nothing moved.
Then its arm lowered toward the correct box.
The gripper closed too high.
One cardboard corner buckled beneath it, and the fault light flashed red.
The machine stopped.
Our provisional score dropped to zero before the first task was complete.
Behind the barrier, Tessa exhaled and folded her arms.
The restored orientation was correct, but the pressure response was using a calibration table I had never seen.
The judge asked whether we wanted to end the run.
I used our emergency pause instead.
Under event rules, a team could inspect a safety-related fault without changing hardware, but the match clock would continue.
I removed the front panel and traced the sensor cable to the control board.
Omar crouched beside me, breathing through his mouth because the warm plastic smell from the motor housing had become sharp.
The cable was secure.
The sensor values were clean.
The wrong pressure table had not come from the sensor at all.
It had been written into our task package when the calibration export returned to the tablet.
Someone had not merely copied our sensor profile.
They had replaced part of the file that our robot would reload when the component was reconnected.
I opened the version history.
The altered task package had been saved during the same Wednesday session that reassigned the sensor.
Its author field showed Tessa’s archived profile.
Coach Brennan sent the screen to the judge before I finished reading it.
The judge stopped the match clock.
Across the field, Tessa unfolded her arms.
She said the author field proved nothing because any file created during an active session would inherit the profile name.
That was true.
Then the judge opened the command history inside the task package.
The altered pressure table had been imported from a folder labeled with Tessa’s current robot number.
Her team captain, a sophomore who had not spoken since the alarm, looked at her.
Tessa told him it was a compatibility test.
He stepped away from her table.
The judge removed Tessa’s score from the live qualification board pending a full comparison of both robots’ files.
For the first time that morning, she raised her voice.
“You’re penalizing an entire team over a file path.”
The judge replied that he was preserving the competition until the record could be verified.
Our repair clock resumed with four minutes and eighteen seconds left.
I could have spent those minutes arguing that the altered file justified a clean rerun.
Instead, I deleted the imported pressure table, restored the local version from 6:58 that morning, and ran one dry grip against an empty box.
The robot lifted it without bending the cardboard.
Omar carried the box back to the field cart even though it belonged beside the starting square.
He noticed halfway there, stopped, and returned without explaining himself.
The judge reset our robot behind the line.
This run began from the point of the safety pause, which meant the crushed first box still counted against us.
We could not reach the highest possible score.
I pressed start.
The robot moved the second box, rejected the third because its lower corner was torn, and completed the route with eleven seconds remaining.
Our score placed us second.
It was enough to qualify.
I sat on the concrete floor behind our table and ate two crackers from the packet the judge had removed from Tessa’s bag.
They were dry and slightly sweet, and one broke inside my mouth before I had enough saliva to swallow it.
Omar sat beside the battery case.
Neither of us watched the board.
For several minutes, it looked finished.
Our robot had qualified, the sensor was back in its foam cradle between checks, and Tessa’s score remained hidden while the judges compared the files.
Then the qualification board changed again.
Tessa’s team returned in fourth place based on an earlier run completed before the sensor had been connected to her robot.
They were still above the cutoff.
She looked across the field at me and gave a small nod, as though the system had corrected an unfortunate misunderstanding.
The final review began after the last heat, when the field house had warmed and the air near the pits smelled like dust, batteries, and the pizza being delivered for volunteers.
The same judge placed both robots on the inspection table.
He did not ask either team for another explanation.
He connected Tessa’s control unit to the portal and opened the calibration history from her highest valid run.
The distance model inside her robot carried the checksum generated by my sensor at 7:42 that morning.
It also contained the corner-protection values from my September build file, including one useless decimal adjustment I had added during a late test and never removed because it changed nothing measurable.
Tessa had copied the model before removing the sensor, then reassigned the component so the inventory portal would support her claim if I challenged her.
The altered pressure table on my robot had been saved during the same session.
The judge closed the diagnostic window.
He ruled that Tessa’s team had used another team’s calibration package without authorization and that my robot had been deliberately modified before competition.
Her remaining qualification score was invalidated under the event’s interference rule.
My second-place result stood.
The ruling did not remove Tessa from school, erase the months we had worked together, or repair the trust she had used to reach our tablet.
It removed her team from that day’s elimination bracket and sent the conduct record to both coaches for the process already written into the event rules.
Nothing larger was promised.
Tessa asked to speak with me away from the tables.
I stayed beside my robot.
“You know I would never damage your machine,” she said. “I was trying to prove you weren’t ready to run this project alone.”
I looked at the loose front cable, the crushed cardboard box, and the orange alignment mark on the sensor housing.
“You changed the file,” I said.
She waited for me to say more.
I didn’t.
Coach Brennan changed every team credential before we packed, removed all archived profiles, and assigned the pit tablet to a locking cabinet that required two current members to open.
Omar offered to leave the team.
I told him to stay for cleanup and give Coach Brennan a complete written account of Wednesday night.
Trust would not be repaired by a speech beside a battery case.
It would be measured the next time someone asked him to ignore a rule because saying no felt impolite.
When the judges released the personal items from inspection, Tessa removed her sweatshirt, charging cables, crackers, and microfiber cloth from the blue bag.
She left the bag on the table between us.
The white thread still held the broken zipper pull together.
“It was always more yours than mine,” she said.
I carried it home with the robot case.
That night, after reinstalling the sensor in its foam cradle, I put two spare cables inside the blue bag and wrote LENA on the inner flap.
