E.10:0.2c.6 - source, target
These are relation words, not final kinds.
Recover the relation or use that makes something a source; common cases include a selected source U.Episteme, exact EpistemePublicationRelation occurrence or reference when availability is material, publication form or carrier when either is the source object, U.View over a source U.Episteme, document with named source-basis, evidence-basis, architecture-basis, or review-basis relation or use, independently established evidence-use relation recovered through A.10, authority-reference relation, named FPF pattern cited as source, file carrier, exact source edition, source-local meaning under an effective scheme, source frame only when its defining pattern and endpoint kind are present, the actual source-side participant of an obtaining named relation, the source-side A.6.5 SlotSpec only when a reusable relation declaration is current, or project-side FPF kind and reference named by value.
Recover the relation or use that makes something a target; common cases include an EntityOfConcern, target U.Episteme, review target, FPF rule being applied, project target, work target, target publication form, project-side FPF kind and reference named by value, target frame, target-side situation or model-use boundary only when its defining rule is current, the actual target-side participant of an obtaining named relation, or the target-side A.6.5 SlotSpec only when a reusable relation declaration is current.
Generic object and target are not final recovered kinds. Keep them only when the sentence explicitly declares a named field or participant designation inside a current episteme, such as ObjectKindUnderImprovement, ObjectVersionUnderImprovement, or ObjectVersionUnderQualityEvaluation; names a review target; or states one direct-relation participant meaning whose actual-participant kind is supplied by value nearby. If a reusable relation declaration is current, name its A.6.5 SlotSpec separately. When the governed kind is known, write that kind by value: FPF pattern version, DRR, FPF corpus slice, publication form, PublicationUnit, file carrier, system carrier, exact changed referent, exact entity or value bound as the result of one particular A.6.1 operation application, candidate proposal, evidence or provenance relation, gate decision, work plan, method description, object-under-improvement evaluation, or another named FPF kind.
Do not recover an FPF pattern, publication form, PublicationUnit, pattern body, or view as a carrier. U.PresentationCarrier is the publication-side carrier kind used under E.17 and E.24.PUB; ordinary carrier wording names the relation to the system, medium, file, rendering, front end, or transport object that bears or renders a publication or symbol. If the text means the FPF pattern publication form, write FPF pattern publication form; if it means the file, rendered, front-end, or transport side, name that exact carrier or relation.
Common repair examples:
| Problem wording | Recovery needed |
|---|---|
target version in improvement prose | ObjectVersionUnderImprovement or ObjectVersionUnderQualityEvaluation, unless target is quoted source wording |
pattern carrier | FPF pattern publication form when the pattern is the publication form; file carrier or rendering only when the system-side bearer is being claimed |
object evaluation when the evaluated kind is known | object-under-improvement evaluation name, such as PatternQualityQBundle, DRRDecisionAdequacyEvaluationCharacteristicSpace, FPFPillarAdequacyEvaluationCharacteristicSpace, or declared local evaluation |
thing, object, target, artifact, or material as final head | FPF kind named by value, project-side FPF kind, or blocker |
Do not publish “source and target” if the selected relation needs the actual FPF kind.