NSTD.6:5.1 - Value bank: full result rows

Use this bank when a narrative rendering “sounds good” and therefore tempts the worker to skip evaluation. Each row illustrates evaluation of a narrative version for one declared use; prior acceptance is unnecessary. The same text may receive different values for a different use.

Case	Characteristic	Value	Evidence basis	Low-value repair
FPF seminar handout	`NarrativeRenderingEpiplexity`	Qualitative illustration; no numerical amount established	The case assumes learners can recover `EntityOfConcern`, forces, solution and neighboring exits. These aspect names do not define equal semantic units, a denominator or an observed reading protocol.	Retain the stated recovery. If transfer matters, try choosing a governing pattern in a new situation and qualify that separate result; it does not increase the original amount.
FPF seminar handout	`SourceReturnReadiness`	`4`	In this constructed handout, each slogan links to its pattern; the exercise sends the reader to that pattern’s conditions before applying the slogan in a new situation. This supplies a when-and-where return, but no changed-condition response or boundary replay for `5`.	Reopen if the task, reader preparation or source access changes, or if the reader cannot locate or use the return. Repair that failure even when the source text is unchanged.
FPF seminar handout	`EngagementBoundedness`	`4`	The constructed failure story is marked as fictional and asks the reader to compare workload conditions; it does not present the anecdote as evidence that FPF guarantees success. This is a design judgement, not an observed attention gain.	Reopen a changed reader effect or stronger benefit claim; restore a condition the persuasive use needs or obtain grounds for that particular claim.
Homotopy explanation	`LanguageStatePrecisionAndCoarseningFit`	`3`	Analogy is vivid but learners may not know where formal conditions return.	Add an analogy-stop line and a formal boundary task.
Homotopy explanation	`OrderingRecoverability`	`4`	Didactic order is named and proof order is deferred by value.	To reach `5`, add a second problem where learner maps story order to formal dependency order.
Franchise continuation probe	`SourceReturnReadiness`	`4`	An illustrative repair of the Readme’s key case puts this return in the draft: “If a scene assumes access before Wednesday, consult the supplied premise that the character first obtains the key on Wednesday.” The condition and destination are explicit.	If the premise or proposed access changes, reopen that continuity comparison. Check a changed case when robustness matters; private or public use alone does not change this value.
Live commentary	`EventMechanismSupport`	`3`	Observation and provisional interpretation are separated, but later telemetry return is only generic.	Add specific official record, replay, or statistics return condition.
Generated graph-to-text narrative	`EventMechanismSupport`	`2`	The draft states “A caused B”, while the source graph establishes only that A preceded B.	Return to `NSTD.3` or `NSTD.7`: remove the unsupported cause or obtain the needed causal account.