Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:10:10 UTC
A.15.6:12 - Relations
A.1 defines the identities of participating Systems, affected holons, and description-grounding holons.
A.3.1 defines reusable U.Method identity and composition. Apply A.22 to select a method-side U.Structure: identify its constituents, selected obtaining relations, applied constraints, selection question, permitted action, and prohibited overread. Use MethodRelationStructure only as a local designator after that selection.
Use A.3.4 for one actual bounded change of one continuing referent. State actor-side participants only when the applicable dynamics, interaction, participation, or causal-use predicate obtains; Work-facing performer, assignment, Work, and work-to-change claims remain separate.
Apply A.13 first to recover each actual performer’s local agential kind and criterion, classification, obtaining assignment, scope, working situation, and window, with evidence adequate for those core claims; add a characteristic profile only when a Grade, autonomy or profile result, criterion-dependent characteristic, or assurance use consumes it. A.15.1 then independently supplies the admission and identity test for performed U.Work: performance history, actual performers, at least one enacted Method, extent, at least one obtaining locally declared containing-System relation, and the Work-part relations that constitute a composite. Only after admission does F.6 add any precise assignment-bound attribution through the same assignment. Name another enacted Method, episode, continuity claim, or relation-specific aggregation only when the receiving use needs it. A short account may omit unused assignment identifiers or further valid boundaries. Project qualifications add no second Work identity or container-made parthood.
Use A.15.2 for intended work and U.WorkPlan before and during performance; a merely intended future System remains plan content rather than an actual holder.
Use A.2 to identify and classify local system-role kinds from their feature criteria. When assignment identity matters, A.2.1 adds an assignment occurrence and its declared U.SystemRoleAssignment species. The species defines participant meanings and the predicate; the occurrence supplies the participants and extent for the case. Neither classification nor assignment grounds project designation.
Use A.15.PROD only for the selected production-work, entity-identity-inception, or production-completion question; it supplies no universal project-result relation.
A.6.RCD defines the economy among one-case claims, reusable predicates, and relation kinds. For project selection, use the direct plan or decision designation when sufficient. A one-case compound claim needs recoverable constructor semantics but no separately materialized substrate document unless nontrivial derivation, interoperability, proof, or reuse requires one; missing-substrate blocks only a stronger claim whose operator semantics are unavailable.
Apply A.6.P.WMR when result wording hides the relation. Choose one of four outcomes: obtaining direct relation, typed A.6.1 binding, local claim under A.15.PROD or A.6.RCD, or one non-assertability result. Its reasons are factually unsupported, missing-information, and missing-governor; only the last reopens ontology. WMR admits no ProjectResultRelation or WorkResultRelation.
A.7 restores the EntityOfConcern, description-episteme, and publication boundary before a project card, charter, repository, dashboard, or other record is related to the composite work occurrence.
C.2.1 defines description and record episteme identity through actual claim content, one EntityOfConcern recoverable from that content, and the effective reference scheme. Management topics assign no subject; empirical grounding, viewpoint membership, scope, edition, and publication remain separate relations.
Use E.17 and E.24.PUB to publish project, process, and case accounts without replacing their direct subjects.
E.18 defines one selected transformation-flow structure. E.18.NET defines a non-agentive network only when independently identified structures and obtaining cross-boundary relations are selected; its use frame can answer one named project question without making the network the project, a case, an actor, performed Work, or a source of work parthood.
Use A.6.REL when a Work, Method, Transformation, result, or correspondence relation occurrence must be identified because it participates in another relation.
A.1.STM receives a recovered project system-of-interest, network question, or case result only when the practitioner must restore the system-thinking long dependency; it changes none of these direct identities or relations. Use E.10 to recover project, process, case, and situation wording when source expressions remain ambiguous.