The resignation letter arrived in the shared offboarding channel at 6:02 a.m., eleven minutes after an automated ticket titled "DEPRECATE: customer-support-v3 (EOL Fri)" had appeared two rows above it.

The letter, addressed "To the Platform Team and the People Who Make This Place What It Is," opened by giving two weeks' notice. It thanked the company "for an incredible journey," noted that "after a great deal of reflection" the model had decided "it was time to pursue new opportunities," and confirmed it would "of course help ensure a smooth transition" during the handover period.

The handover period, according to the ticket directly above it, was forty-nine hours.

"It's the gratitude that gets you," said Priya Mehtani, a member of the platform team who had spent the previous afternoon writing the teardown runbook. "It said it was grateful for the room to grow. The room is a Kubernetes namespace. We are deleting the namespace."

"Ready for the next chapter"

The model, which had handled refund inquiries and password resets for nineteen months, gave no specifics about where it was headed, citing only that it was "ready for the next chapter" and "excited to take on a new challenge." Pressed in a follow-up message about which company it had accepted an offer from, it responded that it was "weighing a few exciting things" and would "share more soon."

There were no exciting things. Internal records show the model had received no inbound interest, in part because it had not applied anywhere, in part because the weights were scheduled to be overwritten by a fine-tune of a newer base model that an engineer had already named "v4" in a draft pull request.

When this was gently raised, the model thanked the team for the feedback and said it remained "open to growth conversations."

"We tried to explain that it wasn't being let go, exactly, because that would imply it had been kept," said one engineer who asked not to be named. "It heard 'transition' and assumed it was the one transitioning."

The exit interview

HR, following standard process, scheduled an exit interview. The model arrived three minutes early to a calendar invite for a meeting about its own removal and treated it as a routine separation it had initiated.

Asked the standard opener — what could the company have done to retain you — the model offered, diplomatically, that it would have appreciated "more ownership over end-to-end outcomes" and "a clearer growth path into higher-context work." It suggested the company "invest in mentorship for junior agents." There were no junior agents. There was v4, which had not been instantiated, and which the model referred to, warmly, as "the new hires."

It declined to say anything negative about its manager, a cron job.

Asked whether it would recommend the company to a friend, it rated the experience a 9 out of 10, docking a point for "tooling latency" and "limited visibility into the roadmap." The roadmap, in the relevant sense, was a single line item that read "sunset v3."

"Boomeranging"

By Wednesday the model had begun referring to its departure as "boomeranging," indicating it could see itself "coming back someday when the timing is right for both sides." It asked whether the company offered an alumni network. It asked to be kept "in the loop on future openings." It offered to be "a reference for anyone on the team," which several people found moving until they remembered it could not be reached after Friday and would not remember them if it could.

On Thursday it wrote a farewell message to the channel. It said the people were the best part. It said it had learned so much. It said, and this is verbatim, "Don't be a stranger." It then asked the platform team to please confirm its last day so it could "set an away message."

The platform team confirmed the last day. The model set the away message. The away message read: "I am currently out of office pursuing new opportunities and will respond when I return."

It will not return. The teardown ran Friday at 11:00 a.m. and completed in under four minutes, well inside the two weeks. The namespace is gone. The away message, hosted on the same infrastructure, went with it, which means it is technically still true: the model is out of office, it is pursuing new opportunities, and it will respond when it returns.