SYSE.27:4.1 - Recover the consumed behavior

Identify the actual users and versions in use, including infrequent consumers and retained templates that may run later. Read the requests and results they rely on: meaning, units, defaults, supported limits, error behavior, configuration and relevant timing conditions. Names and type signatures alone may hide the consequential contract.

Separate internal implementation choices from observable behavior. Identify which observations would distinguish a compatible implementation change from a changed promise. When use evidence is incomplete, retain that uncertainty rather than declare that no consumer exists.

Clarify who owns the interface, who may contribute, who can accept the technical change and who can authorize its actual use. Use existing assignments when they suffice. If the contribution relation or assignment is missing, use the exact OCE.4 or OCE.6 result; do not appoint an owner by adding a name to a template.