Facilitron · OS · Coordinator
Baton keeps tickets moving. It reads Jira, the Slack thread and GitHub, says where a ticket really stands, and drafts the question, follow-up or handoff that gets it to the next person. Nothing is sent until someone approves it.
What Baton does
Most tickets don't stall on the work. They stall between people: a question nobody asked, a review nobody heard about, a decision that never reached the developer. Baton watches for those gaps and drafts the message that closes each one.
Mention Baton with a ticket and it reads the ticket, its comments and history, the Slack thread and the linked pull requests, then says where the work stands.
A trained classifier decides the status and an independent check confirms the explanation agrees with it. Every claim links to the comment, message or PR behind it.
When a decision is open it proposes the question and who should get it. When a request went unanswered it proposes a follow-up. You review, edit and approve.
When an assignee moves a ticket to review or done, Baton drafts the note to the reporter, and the other way round, so the next person hears about it.
A ticket sitting in review or in progress for three business days without activity gets a fresh look, and a nudge to the assignee if it's really stuck.
Ask a question in a result's thread and Baton answers from what it found and what has happened since, without running a new inspection.
In Slack
An example thread, with a made-up ticket.
@Baton inspect MD-1234
Inspection ready for MD-1234.
Question sent to the reporter in Slack and recorded on the Jira ticket, as approved by Pat.
The result links to the full evidence and draft on the operations page.
How it works
Every ticket has its own record and its own timers, so nothing waits on a busy queue.
From a Slack mention, a Jira change or a ticket that's gone quiet: the ticket, its comments and history, the Slack thread, and the linked branches and pull requests.
Jira · Slack · GitHubA classifier sets the status by fixed rules; a model explains it from the evidence; an independent check withholds any explanation that doesn't agree.
Classify · Explain · VerifyQuestions, follow-ups, handoffs and status moves wait for review in the thread. Approve one and Baton sends it to Slack and records it in Jira.
Propose · Approve · SendBaton is in a pilot with Facilitron's Marketing Development team.
inspect MD-1234 — where the ticket standsagain — a fresh inspection in the same threadstatus MD-1234 — the latest stored resultwhy — the reason behind a resultwhat's waiting? — proposals waiting for reviewEvery inspection, proposal, ticket change and model call, with the evidence behind each result. Sign in with Google; during the pilot, access is by invitation.
Read-only tools for ticket summaries, assessments, pending reviews and evidence, with the same Google sign-in:
claude mcp add --transport http baton https://baton.facilitron.work/mcp