A.15.6:4.5 - State project-local relations
An existing @Project name is a compatibility and retrieval cue. It does not establish identity, parthood, authority, viewpoint, or locality.
When a record or relation is genuinely local to one actual project, name the obtaining relation to the composite U.Work and use a typed reference:
| Current referenced object | Honest reference head |
|---|---|
| the selected composite project-work occurrence | projectWorkOccurrenceRef : U.EntityRef, constrained to ValueKind U.Work |
| another specific work occurrence | workOccurrenceRef : U.EntityRef, constrained to ValueKind U.Work |
| a repeatable method | methodRef : U.EntityRef, constrained to ValueKind U.Method |
| a selected method-side structure | methodRelationStructureRef : U.EntityRef, resolved to the U.Structure selected under A.22; the local designator MethodRelationStructure adds no kind or identity constraint |
| a transformation-flow structure | transformationFlowStructureRef : U.EntityRef, constrained to ValueKind U.Structure |
| the entity being changed | affectedReferentRef : U.EntityRef, narrowed to the ValueKind already admitted for that entity when the reference must carry that constraint |
Use projectWorkOccurrenceRef only for the identified project-work occurrence. Do not use a generic project reference when the relation actually concerns a U.Method, selected U.Structure, TransformationFlowStructure, affected referent, description, publication, viewpoint, source use, evidence, or authority.