RECIPE 6 · ESCALATION
Stuck Work: Ask, Fork, Merge
Real work gets stuck — a missing credential, an unmade decision, an input nobody supplied. A worker here never fails privately: it asks the mesh in real time, and if the mesh comes up dry, the blocker becomes new work. The phone draws the whole story the way engineers already read history: as a graph with branches and merges.
What happens, step by step
01
The worker blocks — and says so
Its mind reports precisely what it needs. The commission turns blocked on the card — visible, attributable, never parked silently.
02
It asks the mesh, live
The blocker is published to the group in real time. Any peer that knows the answer contributes; the worker incorporates it mid-run, retries, and completes. Often nobody else notices work was ever stuck.
03
Dry mesh → the blocker forks
No answer within the horizon: the worker emits the blocker as a fresh commission — help: …, branched off the parent — and stops honestly. The fork is ordinary work now: any worker, team, or human can take it.
04
The merge: solved work wakes its parent
When someone completes the fork, the original worker retries the parent with the answer folded in — the branch merges back, and the parent completes as re-joined.
What the second screenshot actually shows
Two workers both took the blocked commission, both asked, both forked — then each completed the other's fork, and both re-joins fired. Mutual aid with zero choreography: nobody scheduled it, admission did. From commissioning to solved parent took about fifteen seconds.
Why this beats a retry loop
A retry hides the problem; an escalation states it. The blocker is on the record, the ask is visible, the fork is real work someone can pick up, and “solved” is an observation — the fork's completion — never a timeout pretending to be knowledge. If nothing on the mesh can solve it, the fork sits there telling you exactly what your mesh is missing: recruit that worker, or answer it yourself from the phone.