E.10.ARCH:14 - Relations

• E.4.DPF defines the DPF entry condition and the placement rule: each domain entry remains beside the DPF claim whose wording it restores; a separate local profile exists only for a named maintained multi-entry use, and any table that publishes it remains a publication form.

• Use E.10 to recognize and close local wording issues or select the applicable row; use E.10.LRN only while claim-bearing learning wording hides the changed subject, Work, Method, result, evidence, or use; use E.10.DEV only while development or evolution wording hides the changed or represented subject, continuity or membership, posture, direction or value basis, direct owner, or receiving use; use E.10.ROLE for bare claim-bearing role, which has no default Tech reading.

• E.10.ROLE provides the thin first entry from bare claim-bearing role. A.6.RSIR realizes first-level recovery for the narrower relation, signature, interface, assignment, declaration-slot, operation, and representation cluster only until the defining or testing rule for the recovered object is clear.

• A.6.P realizes the shared algorithm for generic relation construction and retained relation specializations. An A.6.P.WMR application records exactly one result family for a current Work and Method boundary claim: an exact direct subject-relation claim, positive or governed negative; an exact A.6.1 operation-application binding; a local A.15.PROD claim or another local relation-bearing claim selected under A.6.RCD disposition 2; or exact non-assertability as factually unsupported, missing-information, or missing-governor. Only the last names the affected receiving use and needed future relation rule or declaration. Use A.6.RCD only for the residual needed-claim derivation and relation-kind admission question after exact participants are known and no lighter current rule closes the receiver.

• A.6.F realizes function-like kind and relation recovery.

• C.2.P realizes source-expression, episteme, publication, and FPF-governed-use recovery.

• C.2.P.DR realizes declarative representation and imperative-metaphor overread repair.

• A.3.1 defines one exact U.Method and the method-side relations within its scope. When a named use depends on organization among several such relations, use A.22’s criterion to select the structure, which may be locally designated MethodRelationStructure. Enter through the method-like wording row only while the actual object or relation remains hidden.

• A.3.2 defines membership for a U.MethodDescription episteme that describes one exact U.Method.

• A.6.0 defines reusable signature identity and A.6.5 defines SlotSpec declarations; C.29 defines representation use and explicit correspondence for tuples, arguments, edges, diagrams, and similar forms; A.6.1 defines operation application and E.20 defines governing-definition assignment. An exact onticSlotRelation exists only after its E.24 durable ontic settlement is current.

• Use A.15.2 for planned work, A.15.1 for dated Work, and A.10 for a descriptive account of sources, independently established support relations, currentness and bounded reliance that method-like or path-like wording may otherwise hide; use A.15.PROD for the local production-work, entity-identity-inception, or production-completion claim when that exact WMR result family is current.

• E.18 defines graph paths, path slices, flow valuations, and graph relations over a selected TransformationFlowStructure when the graph claim is current.

• C.30.P realizes architecture and structure wording recovery.

• C.30.STRAT realizes stratification and source-label wording recovery before the recovered claim is handled under its defining or testing rule; the trigger family is in the applicability table.

• C.16.P realizes characteristic and scale wording recovery.

• C.16.Q realizes quality characterization and evaluative characterization wording recovery.

• E.10.MOVE resolves ambiguous move-, readiness-, route-, path-, or trajectory-like wording and exits to the direct pattern; after E.10.DEV, it opens only for a remaining independent path ambiguity.

• A.19.SPR realizes state-family wording recovery only while the exact object, state frame, value, or direct rule remains hidden.

• Use F.18 for durable reusable naming after the kind under repair or relation is known.

• F.19 owns the normal whole-span semantic and pragmatic reading and the final plain technical rewrite; deeper recovery opens only for the FPF question that remains unresolved.

• E.8 states the pattern-form and placement rules.

• E.19 checks distribution preservation during review and refresh.

• E.11 states the entry-distribution rules for broad or old-term cases across README scenarios, ToC query cues, local Problem frames, and worked entry comparisons in E.11.