F.12:4 - Core idea (didactic)

Before reporting the result, name nine things:

1. the exact U.PromiseContent claim being evaluated;
2. the actual Work occurrence or defined Work population whose delivery is in question;
3. the promised outcome or characteristic and its scope;
4. the relevant observations and measured values, including scale and unit;
5. the explicit window and population boundary;
6. the evaluation Method and the System’s dated evaluation Work that enacts it;
7. the exact A.6.1 operation application, including its selected inputs and result binding;
8. the acceptance rule and declared result scale, such as a Boolean, trichotomous, graded, N/A, or Inconclusive-including scale when that scale is actually declared; and
9. the PromiseContentUse, delivery, fulfilment, measurement, evidence-use, any separately defined indicator or proxy, reliance, and status relations that actually connect these claims.

The operation’s result value comes first. A RequirementStatus assertion of Satisfied or Violated is available only through the exact acceptance result and its F.10 rule. Insufficient evidence can support EvidenceStatus=Inconclusive and leave RequirementStatus=Pending, or it can yield a locally declared result such as Inconclusive when the acceptance scale says so; it never silently creates a mixed universal scale. A plain summary may say met, not met, or cannot judge while retaining that exact distinction. A SchemeSenseCell may help address a local meaning, but it cannot bear the promise, Work, observation, value, result, evidence, or status. A comparison table may display the argument, but it cannot establish any of it.