CB.14:5.1 - From repeated case repair to a usable shared guide

In a constructed network of repair workshops, technicians repeatedly ask which information should accompany a request for a second opinion. CB.5 resolves several cases, but the same missing context recurs. The members select a bounded question: help a competent recipient decide what to inspect next without repeatedly requesting basic information.

They recover existing instructions and compare permitted, anonymised examples. One workshop obtains clear accounts of the symptom; another supplies a concise record of what has already been tried. Faster replies at the second workshop also reflect its easier case mix. The group treats that difference as a question, not proof that its approach is superior.

None of the existing instructions explains how to request help when the original configuration is partly unknown. Two practitioners, a method developer and a writer accept a four-week project to supply that procedure and its usable explanation. Their employers provide the agreed time; the community supplies an editor and intended trial recipients. The completion condition is a procedure that lets a recipient identify a useful next inquiry or state the information that prevents advice.

With the practitioners, the developer compares two arrangements: have a specialist reconstruct every configuration before a request, or let a competent recipient first inspect the known account and decide which missing fact is needed. The first is feasible through a paid service but would consume specialist effort even when the unknown detail does not affect the question. They select the second for a bounded trial, accepting that some cases will need an additional exchange. Using ME.7/8, the developer prepares the proposed procedure and explanation: state the question, distinguish known from unknown configuration, report prior actions, and obtain the recipient’s next inquiry or stop.

The first reading exposes wording that could lead the sender to guess an absent configuration; the team corrects it before the trial. In the complete-information case, the recipient chooses a next inquiry directly. In the incomplete case, the recipient identifies the missing detail, the sender obtains it, and the recipient can then continue. A third case lacks retrievable information and receives an explicit stop. The developer and receiving practitioners check these results against the procedure’s stated conditions and return its bounded fit, the additional-exchange burden and the retained limit.

The community accepts the developed procedure and guide for those communication uses, with the trial observations and limitation. It has not established a better diagnostic method or a general reduction in repair time. An editor maintains the guide; receiving workshops decide how to introduce it. A workshop outside the network can use the published instruction without joining its meetings.