fpf.tools
Library / Semantic Integration Engineering Principles Framework
Jump to passage
In this reading
Source · lines 1235–1248

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 03:55:20 UTC

SIE.7:5 - Archetypal Grounding - AP242/QIF Mapping Rules

The AP242/QIF package needs a row set for the configuration-bound inspection query. Its specification includes these constructed rules:

RuleSemantic and executable behavior
MAP-SIE-APQ-01Select the released AP242 product-definition revision/configuration supplied by Systems Engineering and filter features by effectivity E. Do not select “latest” as a substitute.
MAP-SIE-APQ-02For each accepted SIE.4 plan-characteristic-concerns-feature row, join exact source identifiers only under the referenced SIE.5 feature disposition. Preserve AP242 and QIF IDs and issuers.
MAP-SIE-APQ-03Compose AP242 definition/effectivity and QIF plan/result claims through the referenced SIE.6 result. Emit compatible qualified claims, explicit contradiction, non-comparability, or unresolved branches; never overwrite.
MAP-SIE-APQ-04Convert units only through the contract-approved code/unit table and retain original value, unit, conversion rule, precision, and loss. An unknown unit stops that result row.
MAP-SIE-APQ-05Return unmatched AP242 feature, unmatched QIF characteristic, stale result, missing provenance, and source-error states distinctly. No state defaults to an accepted match.

Positive examples cover one known configuration/feature/characteristic/result chain. Boundary cases cover one-to-many characteristics and repeated results. Negative cases cover an obsolete revision, incompatible feature, unresolved identity, unknown unit, contradictory result status, and absent QIF plan. A SQL view, R2RML mapping, QVT transformation, or application code may implement the rules; none changes the specification without reopening the affected rule.