C.2.P.DR repairs declarative-representation overread; C.29 applies only when a mathematical-lens use and
its explicit correspondence, preserved structure, loss, and stop condition are current.
E.17.0 supplies the dependent U.View membership and viewpoint-conformance relation; E.17 and
E.24.PUB keep selected episteme, publication occurrence, form, carrier, reader, and use distinct.
A.6.3.RT governs a representation-scheme transition when the same EntityOfConcern is deliberately
redescribed; it does not establish world-side identity or the correctness of the receiving claims.
A.10, B.3, and G.11 govern evidence reliance, assurance, and source-edition currentness. SYSE.10
specializes the return from research, models, and trials to engineering decisions.
E.15, C.27, SYSE.13, SYSE.14, and SYSE.19 govern configuration continuity, temporal claims, change,
release, and revalidation when those are the current problems.
A compatible SYSE.1 result can supply the scope and intended-result frame for the same subject and decision.
It does not prescribe Work order. If it does not fit, use a qualified direct source or record the missing
result. Descriptions such as concept, candidate, provider, affected-System, or specialist descriptions remain
governed by their own subject patterns.
SYSE.7 supplies evidence to SYSE.6 only when the account can change the same architecture decision at the
same configuration and horizon. The account neither authorizes nor entails that decision. If the account
cannot serve the use—for example, because it is unavailable, stale, outside scope, or incompatible—SYSE.6
uses a qualified direct source or records that missing result.
SYSE.7 supplies a MethodDescription or representation input to SYSE.19 only for the named receiving use.
Description order or conformance does not establish Method order or effectiveness. If the account
cannot serve the use—for example, because it is unavailable, stale, outside scope, or incompatible—SYSE.19
uses a qualified direct source or records that missing result.
When the current problem is requesting and accepting a professional contribution, apply SYSE.9 to that
result and receiving decision. When neighboring Work—for example, realization, integration, supporting-System engineering, description
federation, or assurance Work—needs a description, its governing pattern uses the source episteme through its
own subject, configuration, evidence, and use relations. The Agent performing each neighboring Work applies its governing Method, and that Work produces its own result for the named receiving use.
Engineering profiles—for example, engineering-data, physical, software, electrical, control, manufacturing,
medical-device, ship, or building profiles—may specialize description Methods where their subjects,
formalisms, evidence, and realization relations change the working move. A profile name alone adds no pattern.