SIE-INSPECTION - Connect inspection evidence to the configured product

• Situation: Product-definition and inspection sources are accessible, but a quality engineer cannot tell which inspection result concerns the feature in the configuration being reviewed.
• Question: How can the receiving query return applicable evidence and expose the branches it cannot establish?
• First useful result or blocker: The required answer for a named feature, configuration, and effectivity, with the permitted incomplete branches; or the missing configuration or acceptance decision that prevents bounding that answer.
• Start with: SIE.1 when the receiving question is unsettled; SIE.10 when an existing result already fails that question.
• Stop or return: Stop a dependent branch on unresolved feature identity or configuration. Return a source-definition gap to its owner, a transformation defect to SIE.7, and the release or inspection-acceptance decision to the engineering or quality authority.

In APP-SIE-01, the engineer asks for the QIF plan and result concerning feature F in released revision/configuration R at effectivity E. SIE.1 makes those inputs and the acceptable answer branches explicit. SIE.2 then supplies the source editions, local definitions, identifier schemes, and authority needed to interpret them. If the available model cannot distinguish a planned inspection from an observation of that configured feature, SIE.3 develops that missing distinction and tests it against those cases. An adequate existing model can be reused.

Those meanings allow SIE.4 to state a directed relation: inspection characteristic C-17 concerns product feature F-17 under the plan and configuration. SIE.5 qualifies the feature endpoint at the required grain and effectivity. The relation permits navigation between the records; it does not make a characteristic identical to a product feature. A shared label without the supporting plan and effectivity remains an unmatched candidate. SIE.6 uses these premises to combine definition, plan, and observation claims while retaining their sources and any conflict.

SIE.7 turns the accepted relations into selection and transformation rules. The rules select the supplied released configuration, preserve both source identifiers, and expose an unknown unit or unmatched feature. SIE.8 uses those required behaviours when comparing ways to supply the result; SIE.9 makes their meanings, timestamps, provenance, and failure branches available in the engineer’s query.

The constructed application permits a qualified row set with unresolved local-extension and unknown-unit branches shown separately. SIE.10 can support that narrower answer only with matching evidence for all premises on which it relies, including the engineer’s interpretation. A different question can finish much earlier: if a conversion returns 1 millimetre from an input of 1 metre where 1000 millimetres is required, that case establishes the mapping failure and returns it to SIE.7; unrelated layers remain unexamined. When the released configuration changes, SIE.11 follows the changed applicability through the relied-on identity, mapping, and receiving tests. The query supplies evidence; the responsible authorities still decide release and acceptance.