E.10:0.2c.7 - input, raw material, source data, source material, artifact, output, result, outcome, deliverable, work product

These are high-risk relation-dependent source-word umbrellas, not final kinds or one result family. First name the exact entity and the exact object relative to which the word is being used. For epistemic source data or source material, close the exact source expression, episteme or publication, and source-to-use relation under C.2.P first. For physical raw material, name the relevant constituent, affected-referent, resource-use, supply, transfer, or transformation relation and use the pattern that defines it.

When the remaining current claim is relative to a method, plan, dated work, transformation, evaluation, delivery, transfer, or receiving use, apply A.6.P.WMR. Recover claim subject, modality and exact temporal extent, polarity, and recovery/support state independently. Closure is exactly one of four truthful families: an exact direct subject-relation claim, positive or governed negative; an exact A.6.1 operation-application binding; an exact local A.15.PROD or A.6.RCD claim; or an exact non-assertability result whose reason is independently factually unsupported, missing-information, or missing-governor. A failed known predicate and an unavailable fact keep their known governor and name no future subject pattern or relation declaration; only a genuinely absent predicate, condition, or defining pattern or declaration names the affected receiving use and future subject pattern or relation declaration. Classification, a generic result relation, a method-description field, planned filling, a designation that merely type-checks against an A.6.5 SlotSpec, or a polarity inference is not closure.

Before opening that branch, test whether the phrase already names an independently identified U.Episteme; U.View or U.EpistemeView; publication form; publication face, including a declared MVPK face; PublicationUnit; carrier, front-end, or rendering relation; project-side FPF kind and reference named by value; evidence carrier or evidence relation; document under a named source-basis, evidence-basis, architecture-basis, or review-basis relation or use; review target; C.11 ChoiceResult; measurement-result episteme; evaluation result; diagnostic finding; decision; or another project object whose record kind and defining rule are named by value. Retain ordinary input, output, result, outcome, or deliverable only while the exact defining relation rule remains recoverable. If no governor closes the selected WMR claim, return the bounded blocker. If the missing item is instead a non-WMR kind, retain an architecture-first candidate disposition under the pattern that defines that candidate. Do not invent either one inside pattern prose or replace it with a universal kind or relation.

For work product, name the thing and the claim being made about it: a corrected recording, a report’s content, an assembled device, or another particular entity. A.15.PROD distinguishes participation in production, the first satisfaction of an entity’s identity rule, and completion under a criterion. Apply only the question actually raised. A document can describe a wanted change without being that change; a publication occurrence, delivery and acceptance each need their own basis. A.15.2:4.2 keeps an expected output or delivery target in the plan from asserting its existence or completion.

For a recurring result of Work or result of a project, reuse the established meaning and obtain the facts for the new participants. A.6.P.WMR:4.7 explains that reuse, including production across entity kinds, preservation of a condition, joint Work and later use; :5.7 develops the authoring case and a missing-fact return. Different participant kinds do not by themselves require different result meanings, and the common word does not make those different relations one. A.15.6 supplies the actual-project and whole/part grounds when that claim is current.