A.3.4:4.4 - Add neighboring objects only for the claim being made
For each neighboring claim, identify the object it needs and state that object’s relation to the transformation, changed subject, work, or later use.
| Claim being made | Pattern and boundary |
|---|---|
| reusable semantic way of doing | A.3.1 governs U.Method |
| claim-bearing account of that way | A.3.2 and C.2.1 govern U.MethodDescription |
| typed operation arguments or results | A.6.1 governs the exact operation declaration and application binding; these are not generic transformation inputs or outputs |
| intended work | A.15.2 governs U.WorkPlan |
| performed work | A.15.1 governs dated U.Work occurrences; for the named work/transformation pair, apply the routes and stops in 4.2.4 |
| transformation-flow location or composition | E.18 governs selected TransformationFlowStructure |
| mathematical expression | E.18.2 and C.29 govern representation |
| dynamics model | A.3.3 governs the episteme |
| evidence, measurement, evaluation, or assurance | apply the measurement, evaluation, evidence, provenance, or assurance pattern that states the support or judgment relation |
| description, view, publication, form, or carrier | C.2.1, E.17, and E.24.PUB keep the episteme, view membership, publication occurrence, publication form, and carrier distinct |
input, output, result, outcome, deliverable, or handoff | name the participant and the relation actually claimed: method declaration, planned work, actual work, transformation, evaluation, commitment, delivery, acceptance, transfer, or receiving work. The source word is not a kind or universal slot. |
A declared post-state is part of a transformation description. An actual post-boundary state or changed entity is a fact about the subject. To call that entity or relation a result, name the later use, its participants, and the relation being asserted; acceptance, delivery, publication, and downstream effect remain separate. U.Transformation therefore has no generic ResultRef or OutputConditionOrPortRefs slot.
When the use needs an episteme about the transformation, identify it through C.2.1: exact claim content, the transformation or another subject as EntityOfConcern, and the effective reference scheme. Add scope, viewpoint, empirical grounding, edition, publication, or representation only when the use separately requires that relation.