Friction earns its place when it protects the branch.
GitHub's protected-branch rules can require pull request reviews, status checks, resolved conversations, signed commits, a merge queue, or successful deployments before a change lands.[2] Those gates exist to stop incomplete work. Removing them to make an agent feel fast would be counterfeit speed.
The problem is not the gate. It is the dead, punitive interface around it. A wall of red badges can tell a contributor what failed while saying nothing about what the finished handoff gives the next person.
Accountability can block bad work and still reward a good handoff.
A reward can be small and specific.
In a 2024 essay, Jacob Williams describes a shared routine where finishing a daily task earns the chance to send a song to his partner. The system does not increase the penalty for missing the task. It gives completion a social reward.[1]
This is one person's early experience, not a productivity study. The design move still travels well. After a review gate closes, show the exact proof that now exists, name who can use it, and offer one pleasant action. That action might be a short sound, a clean receipt, or a message ready to send. Do not add points, streak debt, random prizes, or public shame.
Celebration must not counterfeit evidence.
A chime cannot mean "tests passed" unless the interface has the test result. Confetti cannot mean "approved" when no reviewer has approved the diff. The reward should follow a named state change, and the text should say exactly what happened.
The proof jukebox below asks for four strings. It can format those strings into a handoff note. It does not inspect a repository, run a check, verify a link, contact a reviewer, or merge code.
Quiet users still get the whole result.
W3C's guidance says status changes that do not move focus should be available to assistive technology.[3] The component uses a live status line and leaves focus on the field or button the reader chose.
MDN recommends starting Web Audio after a user gesture and giving users explicit sound controls.[4] This page never plays sound on load or when a field changes. The optional chime has its own button. Reduced-motion preferences remove the turntable transitions without removing any information.