IS.2:5.2 - An independent carrier needs a different input, not a community

A freelance repairer obtains a diagnostic procedure from a publisher. The new instrument exports a different identifier format, and the procedure’s lookup fails. The repairer is not part of a practice community.

The support practitioner asks for an allowed sample and follows it through the lookup. A subject expert can map the new identifier unambiguously; the existing instruction assumed the older format. The immediate response is a qualified input adapter and an explanation of its boundary. No peer group, habit programme or personal learning diagnosis is necessary.

If two new identifiers map to the same older code, the mapping is no longer sufficient. That changed condition returns to the target Method and subject expert. The helper must not choose arbitrarily merely to keep the implementation moving.