fpf.tools
Library / Narrativization and Narrative Studies Principles Framework
Jump to passage
In this reading
Source · lines 2178–2201

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:05:10 UTC

NSTD.7:11 - SoTA-Echoing

NSTD.7:11.1 - Operational comparison against domain vocabulary

Narratology distinguishes story, discourse and presentation; generation methods distinguish selected content, its order and its realization. Use these distinctions to locate a defect: omitted material, misleading sequence, unsupported relation or wording. A tool may combine these operations internally, so evaluate the output without inventing a production history.

Keep domain terms when they help select or repair the operation. Resolve an ambiguity where it changes the claim or intended use; another FPF pattern is useful only if its particular question is at issue.

Gatt and Krahmer’s NLG survey (2018) distinguishes planning and realization. Alabdulkarim, Li and Peng’s story-generation survey (2021) reviews controllability, commonsense, characters and evaluation limits. Cardona Rivera, Jhala, Porteous and Young’s narrative-planning review (2024) examines plan-based narrative methods. Kumaran, Rowe, Mott and Lester’s SceneCraft (2023) generates interactive scenes from author instructions; Rahman, Yu and Cho’s G-KMS (2026) tests structured generation, repair and execution in a compact Unity RPG setting. Ma et al.’s survey (2026) identifies continuing coherence, consistency, diversity, control and evaluation problems. Nguyen-Trung and Nguyen’s NITA (2026) assigns interpretive judgement to the researcher in its qualitative-analysis method. These contributions support different operations and conditions, not one compulsory workflow for every narrative.

Operational payload:

  • From NLG, keep content planning, discourse planning, and realization separate. If a tool returns only final prose, inspect its source relation and ordering; reconstruct a plan when it helps repair or reproduce the result. A present-product judgement does not establish the tool’s hidden production history.
  • Story-generation surveys motivate testing the characteristics that matter to the output’s use, including coherence, control or diversity. Their findings do not create a universal admission form.
  • A plot or event plan guides generation. Compare the realized story with its intended goals and constraints rather than infer success from the plan.
  • For an output that must execute in an engine, inspect parsing, state reachability and relevant semantic constraints. A successful schema check alone leaves other narrative qualities untested.
  • From interactive game generation, executable or playability probes may be needed when the narrative must function inside an engine or workflow; text fluency alone is the wrong evidence.
  • In the NITA method, the qualitative researcher interprets proposed themes in relation to excerpts, questions and alternatives. Preserve that responsibility when using this method; it is not a claim that all automated narratives require a human interpreter.

The practical consequence is to preserve the speed of automated drafting while examining the particular relations, constraints and outcomes on which the receiving use depends.