CB.14:5 - Archetypal Grounding

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.

CB.14:5.2 - Reciprocal comparison without a single winner

Volunteer garden groups compare welcoming a new helper and handing over an unfinished task. One group provides a useful first explanation but loses task context when the host changes. Another keeps that context well but expects newcomers to infer where help is needed.

They agree two dimensions with observable examples, inspect a recent arrival and handover in each group, and exchange the relevant practices. The first group tries a brief end-of-session handover; the second asks a newcomer to recover the first task from its invitation and welcome.

At the first garden, the departing host leaves a short account of the bed still to weed, the unlabelled seedlings to leave alone and the location of the tools. At the next session, a replacement continues the named bed without contacting the absent host and stops at the uncertain seedlings. Preparing and checking the account takes five minutes at the end of the session. The group keeps that effort for work that will pass to another host; the uncertain seedlings still need an experienced gardener’s decision.

At the second garden, the newcomer initially cannot identify a first task from the general invitation. The host adds the meeting place, the person to meet and a starter task, then demonstrates potting one tray. The newcomer finds the work and completes the next tray with help available. Preparing the materials and giving a ten-minute welcome are now explicit host work. The group arranges a willing host for the next arrival and retains supervision for tasks that need plant judgement; the clearer invitation alone would not supply that support.

Each group returns the changed practice, observed use and burden to its counterpart. One keeps a handover for unfinished work; the other provides a prepared first task and host. They remain independent and can adapt or stop either arrangement. If the accounts concern different work, they first revise the comparison rather than treating the apparent gap as a competence deficit.

CB.14:5.3 - A method project cannot promise an unknown cause

A group observes repeated equipment failures and wants to publish a preventive rule. The available cases do not distinguish a maintenance effect from differences in equipment and use. A qualified existing source can answer one configuration’s question, so that answer is returned immediately.

The wider causal question remains. RMP.1 is used to state who needs the answer, the competing explanation and the evidence that could change the rule. If a research contribution is justified and can be provided, the community arranges that work and receives its result. If the needed records cannot be obtained, the guide retains the uncertainty and omits the unsupported preventive claim. Useful case-sharing continues within that limit.

CB.14:5.4 - Known practice and absent provision

A volunteer already has a usable, appropriate instruction but cannot access the tool it requires. The organiser obtains the access decision from the owner or helps choose a feasible alternative. No new guide or practice-development team is needed. If the tool is available and the difficulty is learning to use it, the next contribution is HCD support.