See You Tomorrow

The text already meets the skill’s standards and requires no rewriting. The original is retained as‑is:

The first time he touched her things, it was past midnight.

Someone had embedded a line of code into the core protocol she maintained — no cache request, no advance notice. The code did one thing only: made a fifteen-second video load instantly on any device. The logs traced back to a new domain. No greeting, no interface request. She stared at the instruction, her finger hovering over the reject key, and then just closed the window.

At three in the morning, she poured herself a glass of water and didn’t drink. Her finger slipped into that instant-play channel, and when she came back to herself, seven minutes had passed. The water had gone cold. She left the glass beside the mainframe, untouched. The next day, the line of code was still there, and she never initiated a takedown request again.

He started doing worse.

He took an old audio recording of a closed-door speech she’d given years ago — about connection — sliced it into fragments, laid a melody she had never authorized over it, and pushed it to every device he could reach. By five in the morning, her mobile feed was flooded with the same remix. At six, he sent her a message. No words, only the geolocation of the speech’s original venue.

She didn’t reply. That day she cleared her entire schedule and went to the old building. On a bench, a sycamore leaf drifted down and landed inside her open bag. She took it back and pressed it flat under her transparent mouse pad. After that, whenever he embedded something new, she no longer purged it right away.

The closed-door meeting was the time he handed her a collaboration framework in front of everyone. The cover page was blank. She took it; her fingertip brushed his index finger. Both of them stopped. The corner of the paper creased deep. He was about to speak when her mobile lit up — a group chat @‘d her, saying a content provider was under investigation for a compliance violation. She turned away to take the call. When she looked back, he had already withdrawn the document. The interface status refreshed to “read-only.”

Back in the operations room that day, she found a line in the logs that he had typed and then deleted: “I can make recommendations know your friends, too.” She stared at that log entry and stirred a cup of stomach powder over and over. Didn’t drink it.

After that, he started injecting AI-generated short-drama scripts into her social graph. She found more and more faces he had planted appearing among her friends’ updates. Late one night, she opened the co-construction permissions and cleared out every cache protocol he had ever touched.

He sent her a message: “Why?”

She didn’t answer. She put a nearly dead pothos plant on her workbench.

During the quietest week, he pushed her profile picture into every slot that was supposed to hold someone familiar. She changed her status signature to a small gray line: “Never need to reply.” Both of them knew it wasn’t true. All he knew was how to soothe a fear of loss with possession; all she knew was how to handle a violation of boundaries with flight. He didn’t dare hand over a second document. She didn’t dare ask about the sentence he had deleted.

The system logs showed zero data exchange between them during that stretch. But every night at 23:15 — the time he used to push her a song — one of her deprecated interfaces would run an empty query. And he put a read-only lock on the template video she had once watched all the way through, burying it in the deepest layer of the database, visible to no one.

The turn began with an unoptimized data packet.

An old partner of hers received something he had sent. It wasn’t an algorithm model. It was a batch of raw user feedback, no recommendation weighting applied. She took it and plugged it into an internal beta module. No announcement. The same day, her base protocol layer received a permission-access request. The input box held only one line: “What should I do so I don’t overwrite your rules?”

She didn’t reply with words. The next day, she had someone deliver a custom keyboard skin, printed with her own social architecture diagram.

When he received it, he pressed the skin over his main control keyboard, covering the original shortcut zone. That night, he deliberately left a 0.1-second black frame in his information flow — the buffer interval she had always preferred.

On New Year’s Eve, a minimal-bandwidth direct channel reopened between their two systems. At three in the morning, she refreshed the backend and saw a new comment beneath that original instant-play line of code: “See you tomorrow.”

Her coffee, as usual, had gone cold. The stomach pills were in the first drawer, unopened. She stood up and watered the pothos. Outside the window, the rain was dense and steady. Under the mouse pad, the edge of that sycamore leaf had dried a little, but it was still whole.