Applications

These constructed applications show how the language can produce different useful results. The observations and outcomes are stipulated to make the choices inspectable. They do not report field tests or estimate an intervention’s effect. Each application can be entered through the direct patterns it names.

Application 1 - Obtain useful professional help and develop what recurs

Twenty independent repairers sometimes encounter unfamiliar faults. Three initial accounts reveal different difficulties: locating an approved procedure, interpreting an unusual observation and obtaining restricted equipment data. A manufacturer offers a branded forum. Through CB.1, the organiser compares a maintained reference, an accountable specialist service and a voluntary case exchange. The data restriction needs its actual owner’s decision. The first offer combines a reference route with a brand-neutral, non-urgent case exchange; the sponsor accepts discussion of competing equipment and receives no private case data.

For the first exchange, the case owner supplies permitted observations and a precise question. One qualified peer accepts the task; another initially interested person cannot attend. Under CB.2, the organiser confirms the first peer’s relevant competence and a forty-five-minute window, helps the owner remove confidential material, and tells them what the exchange can promise. The room and conversation chosen through CB.4 let both examine the same permitted material. The owner needs to choose the applicable diagnostic check from an established professional procedure.

The procedure distinguishes a warning at start-up from one reported after normal operation, but the shared account omits when the warning occurred. The peer asks the owner to recover that condition from a permitted record. At the next opportunity, the owner finds that the warning followed normal operation. The peer points to the corresponding part of the procedure. The owner subsequently reports that they could select the next diagnostic check without disclosing restricted data. That is the useful result of this exchange. It establishes neither repair completion nor a general improvement in repair speed.

The organiser records ninety minutes of their own preparation and follow-up, in addition to the peer’s time. With CB.7 and CB.9, the association compares repeating that support, paying for preparation or reducing the offer. It chooses one prepared case every two weeks. A capable backup host agrees to cover one absence and rehearses obtaining the permitted material and opening the exchange. An urgent case receives the specialist-service route. CB.3 gives newcomers a small first action—bring one permitted question with the necessary context—and lets others read the later explanation without contributing a case. Under CB.6, the association gives the helper the private acknowledgement they prefer.

A recurring missing condition appears in three later accounts. With CB.14, the repairers decide to make a short preparation aid from the already adequate diagnostic method. A capable practitioner writes it, another checks its conditions, and a new case owner uses it on a contrasting equipment context. That owner can prepare the discriminating material, but a reference is unclear. The maintainer corrects the reference before the aid is offered for wider use. This is a bounded description and use trial. If the underlying diagnostic method had been unsettled, ME/RMP work would have remained necessary.

The association then visits a maintenance team to compare how cases are prepared. Using CB.15, the visitors agree a question with the team and obtain permission to inspect how a real handover is prepared. “Complete handover” means different things in the two settings: the team includes access to an internal history; independent repairers do not have it. The visitors add a preparation question: can the recipient obtain the history used in this account? One repairer uses it to discover missing access before promising the next check. Transferring the team’s fuller arrangement would still require that access.

Five repairers want the manufacturer to provide a permitted diagnostic-data route. They compare their needs and remaining differences and authorise a named person to present that five-person request through CB.13 and CB.16. The representative presents concrete affected work, an access proposal and its restrictions. The manufacturer authorises a limited read-only route for one equipment family. The representative returns the answer and application instructions. Two of the five obtain access for that family; the other three still need data for different equipment. The five decide individually whether the result helps. Expertise supplied a useful contribution; the mandate supplied the right to represent this group; the manufacturer made the access decision.

Finally, CB.10 compares concrete uses, failures, potential later uses and burden. The association retains the low-frequency exchange and preparation aid because the repairers who returned accounts find the next action useful at the agreed cost. It does not claim that attendance, gratitude or three favourable accounts establish a causal business return. If the actual decision later depends on that stronger claim, a suitable inquiry becomes additional work.

Application 2 - Keep a voluntary garden workable through conflict and succession

Twelve neighbours use a shared garden. They value company, access to growing space and occasional shared produce, but do not want the same frequency or kind of participation. The founder has been hosting two sessions a week and will leave in four weeks. A dispute over the shared tools has also made two newcomers reluctant to return.

CB.11 begins with what people still want to obtain. The neighbours compare two sessions, one weekly session, independent bed work with limited common upkeep and a seasonal pause. The founder’s five hours of weekly organising will disappear. One volunteer offers two hours and another offers one. Their schedules overlap for the novice’s half-hour of tool help. Under CB.9, they separate hosting and preparation from money: a small donation can pay consumables but cannot supply absent supervision. One session needs ninety minutes of hosting, thirty minutes of preparation and thirty minutes of qualified tool help: two and a half person-hours in total, leaving half an hour for follow-up. Two sessions remain unsupported.

The group has used the garden by the landowner’s permission. CB.13 distinguishes that permission from the neighbours’ own decisions. The landowner confirms access for the proposed season and names the conditions that the group cannot alter. The neighbours agree one Saturday session, book shared tools for a stated time and return them to the labelled rack. The host can settle competing requests by first confirmed booking; someone uninvolved hears a challenge. Each user returns a clean tool, and the hosts arrange the common check. People who only work their own beds accept these resource terms without promising to host. The mandate covers common access, use and upkeep.

CB.8 addresses the tool incident separately from the agreement about shared decisions. The people concerned give their accounts to someone not involved in the disputed response. The reviewer finds that the posted return location was obsolete and that a newcomer was blamed for following it. The group corrects the location and the response, and explains the change to those affected. The newcomer can return without accepting a hosting duty. At the next session, two people need the same fork. The host applies the booking rule: the first user returns it after thirty minutes, while the other begins a task using a different tool.

Under CB.7, the two volunteers practise opening the shed, preparing a small task and closing the session with the outgoing organiser. One can host but initially cannot obtain the key on the needed day. The owner supplies a permitted key arrangement before the first receiving session. The new host then runs the shorter session, with the second volunteer, who knows the tool and can supervise its use, helping a novice during the allocated half-hour. When that helper will be absent, the host selects a task within the available capability instead of asking unprepared participants to substitute.

CB.3 makes the first newcomer action visible: meet the named host, choose the prepared task, and ask for help at the stated point. CB.4 supplies a working layout with the right tools and a quiet place to pause. CB.12 adds a reminder chosen by the people who want the weekly activity; occasional participants retain the simpler one-time invitation. CB.6 thanks organisers in their preferred way and supplies promised consumables without converting gratitude into an unpaid commitment.

The first independent session finishes within the available time but reveals fifteen minutes of unbudgeted tool checking. The volunteers use part of the half-hour allowance and agree who will perform it; any further increase reopens the one-session promise. Using CB.10, the group collects short accounts from the host, a newcomer and someone who chose independent bed work. The host’s account reveals the tool-checking burden. The independent grower needs to book a tool outside the session; the group supplies a reachable booking contact. These returns change workload and access while preserving different ways to participate.

The transfer under CB.11 includes the usable key arrangement, remaining supplies, current contact and the receiving session’s result. The founder’s support ends at the agreed date. One unresolved reimbursement has a named receiver after departure. If the landowner withdraws access or neither host can continue, the group returns to the feasible alternatives; a hopeful roster would not justify keeping the promise. The common activity can shrink or end while the neighbours retain what they learned and any independent relationships they choose.

Application 3 - Extend a practice without a discussion group

A professional association wants more independent repairers to recognise a well-understood fault condition. An adequate method, correctness criteria and authorised examples already exist. CB.1 compares a discussion group with making that practice obtainable in individual workshops. The latter fits the receiving situation: people need to choose and perform the action when it arises, without a recurring meeting obligation.

The association obtains a clear explanation, demonstration and representative practice through the relevant HCD contributions. In this case, the approved procedure distinguishes a warning at start-up from one after normal operation. The demonstration shows how the permitted event record determines which check to select. Practice changes the equipment example while retaining that distinction. The learner must select the applicable check and identify the record supporting the choice. A qualified provider checks both against the procedure and gives feedback on the missed condition. Learning-product work supplies a readable guide and corrections, while the provider arranges the information and tools needed for performance.

One learner selects the method correctly but cannot access the required equipment information in their workshop. More reminders or discussion cannot repair this condition. The association obtains a permitted data route from the owner. With access supplied, the learner selects the applicable check from a changed example without a prompt. Another learner needs a reminder to inspect when the warning occurred; the provider retains supported use and prepares further practice instead of recording independent capability prematurely.

C.36 distinguishes obtaining the practice, performing it, continuing to use it and selecting or adapting it under changed conditions. The association therefore looks for particular uses and returns, including an occasion when the method did not fit. Through CB.10 it asks a proportionate follow-up question and uses a failed reference lookup to correct the guide. It does not infer cultural retention from downloads or stable independent performance from one supported attempt.

No communication among the learners is required for these results. If unusual cases later need mutual interpretation, CB.2 becomes a serious additional option. If a newcomer wants occasional company, a voluntary activity can serve that separate purpose. If the professional method itself fails in a changed equipment context, ME/RMP work becomes current; enlarging the learner population would not resolve that question.

Later, the association replaces the website hosting the guide. Using CB.11, it obtains permission to move the material and a capable person who accepts correction requests. It updates the directory links it controls and notifies existing users through their usual information channel. After the old host closes, an independent user follows the updated directory, reaches the moved guide and reports a missing example reference; the new maintainer restores it. The practice remains obtainable through this provision.

Application 4 - Separate customer help, learning and provider commitments

A software provider invites customers to exchange examples. Its commercial team hopes to retain subscriptions; participants want to complete particular tasks. Using CB.1, the organiser makes both interests visible and compares peer help, documentation and paid support. An outage requiring a dependable response goes to the provider’s service. One customer’s non-urgent question fits an exchange: how to send each project team a weekly digest containing only its own records.

Through CB.5, the organiser prepares a short case clinic with a capable contributor and synthetic project data. The contributor proposes a filter and a recipient rule from the product’s documented method. The customer tests two projects and discovers that the copied filter still names the first project. They correct it, repeat the test and obtain separate digests for the intended recipients. They return that specific result; actual production use still requires their applicable checks and permission.

Under CB.9, the provider assigns a qualified employee to the thirty-minute clinic every other week and supplies the moderator’s preparation time. Volunteers choose whether to contribute examples. The provider obtains a separate agreement before treating an occasional contribution as scheduled production work.

The customer then wants to construct these configurations independently. With the HCD methods, the learning provider supplies a changed task, practice and feedback. The task changes project and recipient conditions; the learner must select and justify the filter and identify missing input. One attempt succeeds with a hint, so the provider arranges another attempt before judging independent performance. The earlier clinic answer remains useful help, while this work addresses the person’s capability.

Using CB.10, the organiser follows the separate returns. The customer’s report leads to a template that makes the project-specific field explicit. The learning provider uses the observed attempts for its bounded capability judgement. A later commercial inquiry would need suitable grounds to explain subscription retention; clinic activity and favourable stories alone do not settle that explanation.

A sales colleague quotes the customer’s contribution as an endorsement without agreement. Through CB.8, the moderator receives the objection, checks the publication with those involved, obtains removal from the responsible publisher and tells the customer what was corrected. The provider clarifies the permitted use of later contributions. The incident concerns the accepted terms of participation, even though the configuration help was useful.

Continue the group under terms participants can understand and accept. Obtain a dependable support service through its responsible provider. A proposed course whose complete programme or qualified provision is still missing remains a proposal; this clinic can contribute worked material without supplying that whole product.