“Shift’s over. Who keeps the promise to call the customer back?”

That question is where Baton started.

I come from support and solutions engineering, and I’m teaching myself to code. When I think about a handover, I think about the customer waiting for a call, the vendor still investigating, and the incoming colleague trying to work out what they have actually agreed to do.

A conversation can contain all the facts and still leave responsibility unclear. “Seen” is an acknowledgement. A name in a summary is a suggestion. Neither tells me whether someone has accepted the callback at its latest promised time.

For WeMakeDevs’ “Flip the Switch” hackathon, I built Baton around that gap. The demo cases are fictional; the operational question is the one I wanted to explore.

Transparency note: I set the goals and made the key calls, such as when a claim counts as stale. AI coding agents (Claude Code and Codex) wrote most of the code and the first draft of this post, and reviewed each other’s work.…