Refresh Route
Use this route when the package is already being applied and one of its source, evaluation, or carrier assumptions changes.
- Revisit a source when a missing, stale or contradicted claim could change the narrative’s use. Use
G.2for a renewed SoTA synthesis; compare an ordinary event record or fictional canon directly. - Return to
NSTD.6when the evaluated object kind, declared use, value meaning, quality characteristic, evidence basis, or low-value repair route changes. - Use
E.22when the improvement question is underframed: purpose, floor, protected trade-offs, expected evidence, result form, or cost and risk are not explicit. - Use
E.23only for an exact changed narrative rendering version or declared changed slice withNSTD.6re-evaluation planned. - Use
G.11refresh when FPF Core edition, generated-narrative practice, reader telemetry, teaching-test evidence, source pack, or theNSTD.6evaluation characteristic space changes. - Distinguish the teaching or narrative product from observations about its use. Reuse an observation only for the claim and conditions it actually supports; a worked example may remain in the pattern that explains the method.