Source changed 2026-10-03 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 16:50:10 UTC
E.17.0:8 - Relations and contribution boundaries
C.2.1 identifies episteme, claim-content, EntityOfConcern, scheme, and edition identity for P, E, D, and any optional assertion, description, result, basis, or target-claim episteme. E.17.0 adds dependent U.Viewpoint and U.View membership to those same individuals.
Use C.13 to construct exact C_viewpoint only in the action-changing structured-viewpoint branch, and any separately needed collection of selected viewpoints or views.
A.6.6 defines the reusable viewpointConventionDependsOn vocabulary entry; A.6.5 declares the four SlotSpecs inside the two RelationSignature declarations. E.17.0 defines direct dependency and conformance obtaining tests and positive occurrence identity.
C.3.2 admits the two optional local explicit-result ValueKinds and any exact local target or stakeholder KindSignature; their values do not determine direct judgments.
Use A.22 to select S_viewpoint only when separately versioned convention organization changes a named action, and to select any separately current multi-view structure. E.17.0 supplies Q and candidate relation occurrences for that branch.
A.6.3 defines optional source-to-receiving viewing construction, including identity viewing; it does not define view membership.
E.10.D2 defines description epistemes and specification use. A describing use is always named; it selects a viewpoint only when that choice changes reading, checking, or a permitted conclusion. Selection does not establish conformance.
F.18 supplies the two relation-kind NameCards; naming metadata neither defines relation semantics nor grants admission. F.9 applies only when an exact relation between distinct F.17 SchemeSenseCell values obtains.
E.17.1 defines exact catalogue epistemes and local family declarations whose members are exact U.ViewpointRef values. E.17.2 supplies the four-position project-local engineering viewpoint authoring template and, only after local materialization, its four exact bindings. A declaration, template position, or reference grants no viewpoint or view membership.
E.24.UK admits dependent U.Viewpoint and U.View once for public use; E.17.0 supplies their stable positive membership predicates.
E.24.PUB defines form expression, carrier bearing, publication availability, and recurrence. C.29 defines representations and correspondence; neither makes the represented world-side relation obtain.
A.1, A.2, A.2.1, A.3.1, A.3.2, A.15.1, and F.6 distinguish performer Systems, local system-role kinds, exact assignments, Methods, MethodDescriptions, Work, and attribution. Responsibility remains under its direct predicate. Use A.15.PROD only for a separately needed local inception or completion claim.
A.10, G.6, and B.3 retain provenance and assurance. Use A.6.RCD when no pattern defines a needed cross-view or use relation.