Great question. It usually never happens. Our system is based on an adoption of Domino (systematic error/slice discovery), AgentBoard (trajectory/progress evaluation), τ-bench (goal/outcome correctness), MAST (failure taxonomies) and process mining (recurring session paths).

It surfaces issues at trace, session, and systemic levels by tracking user goals/constraints, progress and failure sequences, then grouping recurring high-impact failure modes rather than just clustering similar conversations.

The chances of a wrong fix is very low. However, even if it happens, the devs have the final say at "Merge the PR" stage. If it seems wrong, you can reply in the Github PR and selfship will improve upon it. If it's still going nowhere, the PR can be closed.

A bad fix never lands.