Narrativization and Narrative Studies Principles Framework

DocID: NSTD within FPF Library.

Framework family: Domain Principle Framework (NSTD) License: Original framework content by Anatoly Levenchuk is licensed under CC BY 4.0; third-party material retains its own terms.

Table of Contents

Use the practical entries to find a useful route, the Architectural Reference to understand how the methods fit together, and a pattern body for its working instructions.

Pattern bodies

Reference sections

Readme - First Practical Entries

Practical entries

This framework helps turn material with connected ideas, events or constraints into a narrative that a reader can follow and use. The work includes choosing what must survive, deciding its order, designing the reader’s route and repairing misleading or unhelpful explanations. The entries below are selected examples, not a catalogue or coverage boundary. Bring the actual question; use the Table of Contents or a direct pattern when no example fits. Some difficulties need one bounded repair; others need several patterns working together. For a question already answered by one pattern, use its PatternID and title in the Table of Contents.

Begin with the material and the intended use. A research account, fictional continuation, live commentary and learning course can use the same methods while preserving different things. A narrative may explain an established result or make an unresolved question visible; the relevant research, professional or mathematical work supplies the warrant for a stronger claim. You can ask an assisting agent to explain or apply these methods in the language of your work, without framework jargon.

NSTD-INCIDENT - Repair a fluent account that implies an unsettled cause

• Situation: An incident account turns an observed sequence into an established causal explanation.
• Question: How can it explain the known events and decisions while preserving what remains unresolved?
• First useful result or blocker: An account suited to the audience’s question, or the causal result still needed for its decision.
• Start with: NSTD.3 for support of the event connections, using the supplied log and intended use.
• Stop or return: Finish with an accurate account of known events when that answers the question; obtain the causal investigation result when the decision requires it.

A team has a polished account of a service incident. Its constructed source log records a configuration change at 14:00, failed requests at 14:02, a rollback at 14:05 and restored service at 14:07. The causal investigation is still open. The draft says the change caused the failure and the rollback fixed it.

The existing source and intended use let the team enter NSTD.3 directly. It separates the observed sequence from the two causal claims. NSTD.2 then preserves chronology while making the unresolved explanation visible: the setting changed before the failures, and service returned after rollback; the log alone does not establish why. If the audience needs a causal conclusion to choose a remedy, the question returns to the investigation. If it needs an accurate account of known events, the corrected account can already serve that use.

NSTD.4 examines the account’s operator viewpoint. A source-backed description of what the operator saw can explain the rollback decision; selecting that viewpoint does not establish the operator’s responsibility for the original failure. The account should expose any other recorded condition that changes that interpretation. NSTD.5 may preserve the urgency and unresolved question without presenting the confident ending that the investigation has not supplied.

NSTD.6 tests the repaired version for that audience and use. Ask what happened, which explanation remains a hypothesis, and what information would be needed for the proposed remedy. Keep the response obtained before extra help. An expert walkthrough, an actual reader’s response and a formal estimate support different conclusions. If the reader still reconstructs a settled cause, repair the sentence or ordering that produces that reading and check the affected part again. If a later investigation establishes a mechanism, return its result to the explanation and reconsider the dependent conclusion.

Practical-Use Cards

These selected examples show extended combinations whose dependencies are easier to retain with a mantra. Choose and adapt the route to the actual difficulty; the cards do not prescribe a universal workflow.

NSTD-CONTINUATION - Develop an engaging continuation consistent with its source

• Situation: A fictional continuation needs both narrative interest and consistency with the established world.
• Question: How can the event connections, presentation order and viewpoint work together?
• First useful result or blocker: A usable scene or sequence, or an unresolved source condition.
• Mantra: Select constraints; connect events; choose what each viewpoint reveals; create interest; compare the result; repair the failed connection.
• Start with: NSTD.1 for the source and constraints; NSTD.2 for their presentation order.
• Stop or return: Finish with the supported continuation. Return a failed event connection to the source or proposed action, and weak engagement to viewpoint or presentation.

Expansion for NSTD-CONTINUATION

An author wants a continuation of a fictional story to be engaging while remaining consistent with the established world. NSTD.1 first selects the source material and the constraints the new story must respect: what characters know, what they can do, earlier events and the proposed continuation’s premises. That selection gives NSTD.2 something to order. The author can show a discovery late for suspense while keeping the underlying order of events recoverable.

Consider a constructed case: a character uses a key on Tuesday, but the supplied source says the character first obtains it on Wednesday. Moving the reveal of Wednesday’s event earlier in the text does not repair the Tuesday action. NSTD.3 tests the connection between obtaining the key and using it. The author must change the proposed action or establish a compatible earlier means of access, then check that proposal against the selected source. If neither is available, the scene remains unresolved.

NSTD.4 asks whose knowledge the chosen viewpoint reveals. The reader may be kept unaware of the key’s origin while the character already knows it; the two knowledge states must remain distinguishable. NSTD.5 can use that gap to sustain curiosity, provided the eventual explanation preserves the access condition. These decisions supply the material for NSTD.6: can the reader recover the event order, the available access and the difference between a delayed reveal and a missing cause? A continuity failure returns to source selection or event support. Weak suspense with intact continuity can instead return to viewpoint or engagement. The missing-key problem requires a supported event connection.

If an LLM drafts scenes, NSTD.7 connects these same decisions to generation: selected sources and constraints, content plan, ordering plan, wording, source comparison and evaluation before deciding the intended use. When fidelity remains in doubt, change the supplied access condition and inspect whether the generated scene responds, or ask a reader to reconstruct it without the prompt. A fluent scene that silently invents another key returns to planning or source qualification. The author remains responsible for accepting the scene. Publication rights require their own determination.

The result can be one usable scene, a repaired sequence or an unresolved source question. There is no need to construct an entire fictional universe before obtaining that result.

NSTD-LEARNING - Teach selection and use of methods across unfamiliar cases

• Situation: Learners can repeat separate explanations but cannot choose a repair in an unfamiliar project.
• Question: Which content, order and tasks will help them distinguish and perform the needed repair?
• First useful result or blocker: A learning route with the support each task needs, and an evaluation of the learner’s resulting understanding or use.
• Mantra: Name the learner’s next task; attach its prerequisites and support; vary the cases; inspect the response; repair content or timing.
• Start with: NSTD.1 for the learning purpose and NSTD.8 for the route across cases.
• Stop or return: Repair missing content or mistimed support where the response exposes it. Retain an adequate explanation; qualify learning and transfer claims by what was actually observed.

Expansion for NSTD-LEARNING

An engineering course presents source selection, ordering, viewpoint and evaluation in separate blocks. Learners can repeat each block’s explanation but struggle to choose a repair when an unfamiliar project story goes wrong. NSTD.1 turns that difficulty into the learning purpose: select and perform the appropriate repair in a new case. NSTD.8 separates this learning route from the source publication’s topic order.

The course can begin with a supported source-selection case, then introduce an ordering failure. It later returns to the first case with a viewpoint question and asks learners to distinguish the two repairs in unlabelled situations. NSTD.2 explains why this teaching order differs from the source’s organization. Before each task, NSTD.8 checks that the needed distinction, operation or accessible reference has been introduced. A deliberate initial attempt before instruction can help surface alternatives, but its subsequent explanation must resolve the difficulty.

NSTD.3 supplies concrete reconstruction questions; NSTD.5 selects examples or hooks that help learners stay with them. In the framework’s mathematical teaching case, a deformation image is useful only when the learner can recover which changes the formal definition allows and where the analogy ends. If that boundary is missing, adding another attractive image will not supply it. The formal definition and its mathematical justification remain in the source.

NSTD.6 evaluates the route and the account, expression and reader under the declared conditions, using C.2.8 for recoverable structure. First identify which necessary relations were recovered or missed; a count is useful only when the unit and selected set are defined. Keep this structural result separate from usefulness, human effort, retention and transfer. One successful response with a reference supports that observed use; it does not show unaided performance on unfamiliar work.

The response determines the return. A missing relation needs content repair; a demand encountered before its support needs a change in the route; an adequate explanation may need no change. Use E.22 when the improvement question or protected qualities need clarification, and E.23 to compare a worthwhile repair and re-evaluate what changed. Lessons, slides and exercises are the resulting teaching materials. The patterns explain how to construct and improve them.

Narrativization and Narrative Studies Principles Framework Architectural Reference

NSTD.Reference:1 - Problem frame and shared difficulty

This Domain Principle Framework helps authors, teachers, technical communicators, researchers and assisting agents construct and improve narratives from connected material. The material may concern observed events, mathematical relations, a proposed design, an unfolding event or a fictional world. A reader needs to recover selected relations in an order they can follow and use.

A fluent account can lose a condition, turn temporal order into a cause, hide another participant’s knowledge or teach a memorable slogan without its working distinctions. The task is to choose and arrange what matters, then detect and repair such losses. Narrative interest and clarity help that work; the warranted strength of the account still depends on its content.

The reader needs enough subject knowledge to identify the relevant material, or access to someone who can supply it. The methods help construct the account; a missing physical mechanism, proof step or factual observation may require work in that subject before a stronger explanation is possible. An accurate account of what remains unresolved can already be useful.

NSTD.Reference:2 - Solution and connected use

NSTD.1 relates reader purpose and source selection. NSTD.2 chooses presentation order while preserving the source relations needed for use. NSTD.3 tests the event, mechanism or dependency connections the account invites the reader to infer. NSTD.4 chooses voice and viewpoint; NSTD.5 develops attention and motivation without sacrificing needed content. NSTD.6 evaluates a narrative version, including a candidate. NSTD.7 connects planning, automated generation, inspection and repair. NSTD.8 organizes a learning route and its reconstruction or application tasks.

Enter at the demonstrated difficulty. A draft that implies a cause from chronology can begin at NSTD.3; it need not first receive a complete NSTD.1 record. A new explanation can start with the reader’s question and a few source relations, produce a short account and refine its selection during comparison. Evaluation can reveal the next useful repair or support keeping the sufficient result.

The Readme’s incident case illustrates the connection. A log shows a configuration change, failures, rollback and recovery. NSTD.3 leaves the two causal claims unsettled; NSTD.2 gives an accurate chronology. That account can answer what happened. A decision requiring the cause returns to the investigation. NSTD.4 checks whether the operator’s viewpoint falsely assigns blame, and NSTD.6 checks what the reader recovered.

NSTD.Reference:3 - Shared distinctions and conditions

A narrative account is content expressed in a form a reader can encounter. The source-to-narrative construction describes how it uses selected source content. This DPF uses A.6.3.NAR for that construction. Its ordinary entry is source selection, ordering and comparison. When citation, dispute or another receiving use depends on claim identity, NAR supplies the fuller construction between source and receiving epistemes. Public distribution alone does not require it.

Past events, live observations, proposed events and fiction have different truth conditions. Mark the difference where it changes understanding. A live inference may need later correction; a future scenario states assumptions; a fictional continuation can introduce events that satisfy its chosen premises and continuity constraints.

Sometimes the source is an architecture description or view. Preserve the decision, trade-off and actual-structure returns that matter to the narrative’s use. C.33 concerns architecture-description adequacy, C.34 a claimed structural correspondence, and C.35 a generated or discovered result intended to inform architecturing. Ordinary narrative generation does not select all three.

A displayed sequence may be one slice of a branching or constraint-governed structure. Where alternatives, loops, exits or stops change the reader’s action, preserve them or provide a usable return through A.22.CGUS, E.18.3 or the defining source. Showing one route does not settle which other routes remain possible.

Voice and focalization describe how an account presents its subject. A real writer, listener or organizational participant has a different relation to the work. Use the precise system-role, assignment, agency or Work conditions only for the corresponding claim. Ordinary contribution language and clear metonymy can remain ordinary.

NSTD.Reference:4 - Architectural Rationale, forces and performance across levels

The language separates contributions that can need different repairs while keeping their results connected. Changing order cannot supply a missing cause. Changing viewpoint can reveal an overlooked relation but can also obscure another. Increasing suspense can improve attention while delaying a prerequisite the reader needs. The shared comparison is therefore between the intended use, selected relations, their expression and the reader’s recovery.

Two alternatives are often sufficient: a direct factual answer with no narrative development, or a familiar genre convention that already serves the reader. Use the larger repertoire when a connected account introduces ordering, inference, viewpoint or learning difficulties. A fixed drafting pipeline would make these dependencies easy to list but would obstruct useful returns from a trial narrative to source selection. The patterns allow both direct entry and iteration.

The methods also participate in a vertical of ongoing work. While a teacher explains a counterexample, selecting its contrast, forming its sentences and observing the learner’s response are constituents of teaching at that moment. The whole task may require a distinction to be usable before the next exercise; that requirement can change the sentence, diagram or timing now. If the learner cannot yet recognize the mathematical objects, polishing the story cannot supply that capability. Add the needed explanation, reference or practice, or change the task. Likewise, a technical narrator must have the relevant subject knowledge or obtain that contribution from a specialist.

B.1.5.EW helps recover such simultaneous constituent and encompassing work; B.1.5.RS helps examine a replacement. The DPF describes part of the needed repertoire. Subject knowledge, language capability, available time, reader access and actual coordination may determine whether the combination can be performed.

There is no fixed number of useful refinement levels. A teaching application, genre-specific profile or local generation workflow can combine these same methods with narrower ones. A profile’s scope, a Method composition and a chapter’s position are different relations; the pattern numbering fixes addresses rather than an execution sequence.

NSTD.Reference:5 - Evaluation, typical failures and consequences

Before relying on a narrative, ask what the reader needs to recover, whether the account supports that recovery, and which remaining uncertainty changes the next action. Inspect an inferred cause or attribution against its source. For a draft or generated candidate, use the defect to choose a repair; acceptance is not a prerequisite for evaluation.

NSTD.6 applies C.2.8 to the account, its expression and a specified reader or observer. State the selected semantic relations, correctness criterion, preparation, help and budget as needed for the question. A qualitative comparison can suffice. A count also needs its grain and selected set. Retain which relations were recovered: equal counts may support different actions.

An expert walkthrough, an actual response and a formal estimate establish different things. One supported response does not establish unaided transfer or reliability across a population. Current product quality, fidelity to a named source and evidence of how the product was made are separate questions. Missing manufacturing notes do not prevent diagnosis of a visible defect.

Typical repairs follow those distinctions: qualify a cause inferred from sequence; restore a hidden viewpoint or condition; attach a prerequisite where the learner needs it; compare a generated scene with continuity constraints; or retain an adequate explanation when further work would add little. If repeated improvement is worthwhile, use E.22 to frame an unsettled question and E.23 to compare the change with protected characteristics, cost and risk in view.

The gain is an account whose content, order and use are easier to examine and change. The cost is the comparison and any necessary reader or subject work. Additional forms, probes and evidence are justified by what their result can change. A consequential permission, evidence, assurance or affected-party claim needs its own grounds; narrative quality alone does not supply them.

NSTD.Reference:6 - Source synthesis, coverage and relations

Narrative studies supplies several complementary contributions. Narratology distinguishes story, discourse, voice and focalization; cognitive narrative research examines event comprehension and reader processing; science communication makes the tension between engagement and supported claims visible; natural-language generation and narrative planning distinguish content, order, realization and control. Learning research contributes conditions for retrieval, spacing, interleaving and transfer. The Source Use And Refresh Map and each pattern’s SoTA-Echoing section state the adopted contributions and their limits.

The synthesis uses those distinctions as methods for recognizable work. It adapts staged planning into a revisable cycle and separates product evaluation from generation history. A purely stylistic account would miss source and dependency failures; a universal formal-admission procedure would add unnecessary work before ordinary explanation. Domain sources remain necessary when the proposed use exceeds a source’s actual reach or a newer result changes the method.

The publication foregrounds selection, order, event and mechanism support, viewpoint, engagement, evaluation, generation and learning routes. Its teaching, fiction, mathematical and live-event examples demonstrate different uses; they do not bound the repertoire or establish complete domain coverage. Genre craft, the full history of narratology, a complete learning-science curriculum, generation algorithms, legal permissions and formal metric calibration require their appropriate sources or more specialized methods.

The emphasis on explicit source relations can favor analytic and technical work. Expressive aims such as mood, voice and imaginative discovery remain legitimate; choose a fidelity or reconstruction criterion only when that use requires it. A provisional draft can help discover both the subject and the purpose. Actual field effectiveness and learning remain questions for observations qualified by their conditions.

This DPF depends on FPF’s general distinctions and adds narrative-domain methods. FPF does not depend on NSTD. The DPF Relations section explains the specific dependencies, teaching-publication relations and useful returns. In an architecture-mediated explanation, the reader may need to return from narrative to a description or view, then to the modeled structure and observations. A directly sourced explanation returns to its relevant material. Each representation may omit relations; inspect those omissions when they affect the use.

NSTD.Reference:7 - Worked combinations across narrative uses

The cases show how the methods combine across teaching, fiction, mathematics and live commentary. Each route can be shortened to the work the current difficulty needs.

Use a route to construct a narrative or to locate a defect in an existing one. An existing draft can be evaluated immediately; the absence of its production history does not prevent judging a visible problem. Return to the relevant construction step when repair needs it.

NSTD.Reference:7.1 - Case A - FPF Learning Route Probe With Seminar Carrier

Use: a seminar or slide series that teaches readers to apply FPF patterns. The complete course is a separate teaching publication; a worked teaching example may also appear in a pattern.

Patterns opened: NSTD.1, NSTD.2, NSTD.3, NSTD.5, NSTD.6, NSTD.8.

Selected content: what a pattern concerns, when and how to use it, how methods relate, when to consult a source, and how to evaluate and improve the result.

Temporal posture and rendering mediation mode: prospective planned learning route over current FPF source structures; direct source-structure mode unless an architecture-of-FPF explanation is explicitly opened as architecture-mediated support.

Ordering rule: didactic prerequisite order, with explicit divergence from monolith order when helpful.

Construction route:

1. NSTD.1: relate the learner’s task to the needed pattern content. For a first-use lesson, select a recognizable difficulty, the method’s first operation, its result and the next relevant method.
2. NSTD.2: order the selected content so that each exercise has the needed prerequisites. Depart from the source’s chapter order where that serves the lesson, retaining a return to any omitted condition.
3. NSTD.3: turn each session into a reconstruction target: after the session, the learner should be able to reconstruct one pattern-use route from source basis and selected source structure, not only repeat the teaching story.
4. NSTD.5: add motivation devices only where they protect attention without replacing source return; slogans and examples remain subordinate to reconstructable source structure.
5. NSTD.8: try a short learning sequence with a recurring anchor, a reconstruction or application task, and the support needed at that point. Drafting a slide can reveal a missing prerequisite; record the route when course coordination or revision needs it.
6. NSTD.6: evaluate the route once the above source and use basis is recoverable. A missing structural-amount basis returns to source-spine selection; a demonstrated relation loss calls for repair of the selection, expression or usable source return through the relevant NSTD method before style polish. Compare any numerical amount only at its stated scale and conditions.

Intentionally lost or deferred: full monolith detail, all neighboring patterns, all source-pack rows, and advanced formal variants. These return through source links.

Related work: use E.17 and E.17.AUD for teaching-publication and audience-unit questions, NSTD.6 for narrative quality, the subject sources for the taught claims, and A.10 for evidence claims. G.2/G.11 apply when synthesizing or refreshing a SoTA basis.

Low NSTD.6 repair: if learners enjoy sessions but cannot reconstruct pattern use, repair NSTD.2, NSTD.3, and NSTD.8 before changing only style.

NSTD.Reference:7.2 - Case B - Franchise Continuation Storycraft

Use: plan a continuation of an existing fictional world, such as a space-opera franchise. This case concerns narrative construction; it does not determine publication rights.

Patterns opened: NSTD.1, NSTD.2, NSTD.3, NSTD.4, NSTD.5, NSTD.6, NSTD.7 when generation is used.

Selected constraints: canon and continuity, the premise and theme, character motivation, causal plot relations, viewpoint and stakes. New events can be invented within those chosen constraints.

Temporal posture: prospective fiction based on a chosen canon or local premise set. Compare directly with those sources; an architecture description is needed only if the story work itself uses one.

Ordering rule: choose how plot events and revelations reach the reader. A delayed reveal can be intentional; repair a missing connection when it defeats the intended plot or understanding.

Construction route:

1. NSTD.1: choose the premise and the canon constraints the continuation will retain. Existing excerpts or a compact note may suffice; build a maintained source collection only when repeated work needs it.
2. NSTD.2: distinguish event order from reveal order. For a consequential action, ensure that the necessary means or motive are available in the story, even if the reader learns them later.
3. NSTD.3: build an event or mechanism support map for the proposed plot: initiating condition, constraint, conflict, action, consequence, update, and unresolved tension.
4. NSTD.4: choose the viewpoint and protagonist’s contribution. Clarify an attribution or omitted perspective only when it changes the intended account.
5. NSTD.5: try stakes, curiosity, identification or a familiar allusion for the intended reader effect. Keep a device when its contribution is worth its cost and it preserves the chosen narrative constraints.
6. NSTD.7: inspect generated candidates against the chosen premise and continuity. Repair, retain or reject them before deciding their use.
7. NSTD.6: evaluate continuity, character agency, causal plot support, viewpoint discipline, and NarrativeRenderingEpiplexity; repair structure before increasing drama.

Intentionally lost or deferred: exhaustive canon, production rights, fan-service catalogue, and publication permission. These are outside this DPF case.

Related work: select canon and its constraints through NSTD.1; inspect generated continuations through NSTD.7 and NSTD.6. Use NSTD.4 for voice and attribution. Additional agency, responsibility, ethics or publication-rights questions depend on the claim and intended use. Maintaining canon alone selects neither G.2 nor C.35.

Low NSTD.6 repair: continuity drift, premise mismatch, character-agency collapse, escalation without causal structure, fan-service replacing plot function, viewpoint confusion, or stakes without source return repair through NSTD.1 through NSTD.4, not by adding more dramatic prose.

NSTD.Reference:7.3 - Case C - Homotopy Theory Explanation

Use: graph-heavy and structure-heavy mathematical theory rendered into sequential explanatory narrative for learners.

Patterns opened: NSTD.1, NSTD.2, NSTD.3, NSTD.5, NSTD.6, and NSTD.8 if taught as a series.

Source structures that must survive: definitions, dependency order, examples, counterexamples, proof-status boundaries, theorem prerequisites, and source return to formal statements.

Temporal posture and rendering mediation mode: retrospective or atemporal explanatory route over existing mathematical source structures; direct source-structure mode unless a teaching architecture or knowledge-graph architecture is explicitly used as mediation.

Ordering rule: didactic dependency order with source-return to formal proof order.

Construction route:

1. NSTD.1: select the learner use and source structures: definitions, dependency graph, examples, counterexamples, theorem prerequisites, proof-status boundaries, and formal-source return.
2. NSTD.2: choose didactic dependency order; explicitly mark where it differs from formal proof order, historical order, or publication order.
3. NSTD.3: define the reconstruction target for each step: what the learner must be able to state, distinguish, use in an example, or return to as formal proof status.
4. NSTD.5: introduce an analogy, question or visual example where it helps the learner. Supply a condition before the learner’s next inference needs it; distinguish an intuitive image from a formal result.
5. NSTD.8: if the explanation becomes a series, turn dependencies into session anchors and reconstruction tasks rather than a sequence of entertaining analogies.
6. NSTD.6: evaluate whether learners can recover definitions, dependency order, example boundaries, proof-status boundaries, and source-return points; low values repair source selection and ordering before adding more metaphor.

Intentionally lost or deferred: full proof detail, every lemma, historical order, and advanced generalizations not needed for declared learner use.

Related work: C.29 supports a mathematical lens when one is being constructed; the mathematical source supplies the definition or proof. A.10 applies to an evidence claim and E.17 to the explanation’s publication form.

Low NSTD.6 repair: if learners can retell an analogy but cannot state definitions, dependency order, example boundaries, or proof status, repair NSTD.1, NSTD.2, and NSTD.3; do not raise engagement alone.

NSTD.Reference:7.4 - Case D - Live Event Commentary

Use: live commentary for an unfolding football match or analogous event stream, used for listener orientation and later review only under source-return conditions.

Patterns opened: NSTD.1, NSTD.2, NSTD.3, NSTD.4, NSTD.5, and NSTD.6.

Source structures that must survive: score state, event sequence, possession or control changes, tactical or situational structure, actor roles, uncertainty, provisional interpretation, and return to official result, telemetry, statistics, or recording.

Temporal posture and rendering mediation mode: live unfolding event stream; direct source-structure mode. Architecture-mediated mode opens only if the commentary is explicitly about structure of a team, venue, broadcast system, or other holon and uses architecture descriptions as admitted source basis.

Ordering rule: live event order with explicit prediction and uncertainty markers; later recap may use causal or tension order but must not erase which claims were provisional during the live event.

Construction route:

1. NSTD.1: identify what the listener needs from the live account, the available event source, the commentator’s viewpoint and which interpretations remain provisional.
2. NSTD.2: follow live event order while marking when the sequence is observation, inference, tactical interpretation, or prediction.
3. NSTD.3: preserve event and state-update support so listeners can reconstruct what changed, who acted, and what remains uncertain.
4. NSTD.4: keep viewpoint and agency wording from assigning responsibility, intention, or capability beyond the observable or sourced basis.
5. NSTD.5: use tension and suspense only as attention support; it cannot make predictions, disputed rulings, or emotional framing into settled evidence.
6. NSTD.6: evaluate whether the listener can distinguish observed event, provisional interpretation, uncertainty, and source-return obligation.

Intentionally lost or deferred: full official statistics, all off-camera events, post-match medical or disciplinary facts, and later tactical analysis. These return through official source refs, telemetry, or recording.

Related work: return to the official record for a disputed fact or correction. Use the relevant publication guidance for broadcasting; use D.1–D.5 when an actual harm or value conflict arises and G.11 when a changed source affects a maintained account.

Low NSTD.6 repair: if listeners remember drama but cannot distinguish observed event from commentator inference or later official correction, repair NSTD.1, NSTD.2, NSTD.3, and NSTD.4 before increasing engagement.

NSTD.Reference:8 - Support Maps

Open these maps when a pattern’s instruction leaves a source, meaning or neighboring-method question unresolved. They are optional reference material, not prerequisites for beginning a narrative.

Use the architecture bridge for an actual architecture-related narrative; the semiotic bridge for an unresolved representation or interpretation problem; the source map for a relied-on research claim; and the precision map to distinguish an overloaded term.

NSTD.Reference:9 - Architecture and narrative work bridge

Architecture and narrative work both involve selecting and relating structures, but their results differ. The table identifies useful correspondences and the conditions under which an architecture method applies. A plot, synopsis or teaching route is not thereby an architecture description.

The comparison suggests possible training transfers, not an established transfer effect. An architect learning narrative work can practise presentation order, viewpoint and reader response while using familiar structural distinctions. A narrator learning architecture work must additionally learn how to identify the relevant real structures, compare design alternatives and check their consequences. Competence in one practice does not establish competence in the other.

NSTD.Reference:10 - Semiotic and language-precision bridge

Narrative construction changes how signs, sequence and viewpoint make material available to a reader. Use the following neighboring methods when they address the actual difficulty. Ordinary drafting can proceed without a formal language-state profile.

Use FPF for the general definition or method and NSTD for the narrative operation that uses it. This keeps the dependency from NSTD to FPF while avoiding a second set of general definitions inside narrative practice.

NSTD.Reference:11 - Working meanings and direct source returns

These terms help distinguish questions that occur in narrative work. A local field name does not create a new Core kind. Use the cited definition when the particular claim needs its precision.

NSTD.Reference:12 - FPF contribution and compatibility

The definitions and general methods used by this edition are available in FPF Core. In particular, A.6.3.NAR supplies the source-to-narrative relation and its ordinary and claim-specific uses; C.2.8 supplies reader-qualified structural recovery; A.19.ECS and C.16 supply the evaluation distinctions used in NSTD.6. The support maps and the relations below identify the additional content used for each relevant claim.

NSTD depends on those definitions for the uses stated here. A relevant change calls for reconsidering the affected narrative instruction or evaluation; it does not require restarting unrelated uses. Compatibility across a changed Core edition is a separate question about that use. E.4.PFR explains this dependency distinction and G.11 the currentness question.

NSTD.Reference:13 - DPF relations

These relations explain how the methods combine and when their dependencies need to be revisited. A pattern citation locates the relevant definition or instruction; it does not own a subject or create an authority relation. Ordinary subject assertions below are sufficient for reading and use. A maintenance index may represent the same assertions through the optional forms in E.4.PFR.

NSTD.Reference:14 - Refresh the affected narrative use

Use this route when the package is already being applied and one of its source, evaluation, or carrier assumptions changes.

1. Revisit a source when a missing, stale or contradicted claim could change the narrative’s use. Use G.2 for a renewed SoTA synthesis; compare an ordinary event record or fictional canon directly.
2. Return to NSTD.6 when the evaluated object kind, declared use, value meaning, quality characteristic, evidence basis, or low-value repair route changes.
3. Use E.22 when the improvement question is underframed: purpose, floor, protected trade-offs, expected evidence, result form, or cost and risk are not explicit.
4. Use E.23 only for an exact changed narrative rendering version or declared changed slice with NSTD.6 re-evaluation planned.
5. Use G.11 refresh when FPF Core edition, generated-narrative practice, reader telemetry, teaching-test evidence, source pack, or the NSTD.6 evaluation characteristic space changes.
6. 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.

For source qualifications, citation and edition information, see the Sources and Edition Notes.

NSTD.Reference:End

Patterns

NSTD.1 - Choose a Narrative’s Purpose and the Source Structures It Must Preserve

Status: Stable

Type: DPF pattern body

Primary EntityOfConcern: selecting source structures and a narrative purpose that serve the intended reader. The optional intake below records one application of this method.

NSTD.1:1 - Problem frame

Use this pattern when a writer, narrator, teacher, architect, researcher, commentator, story designer, or tool starts with a message, lesson, theme, persuasive effect, desired memory, live commentary line, or future scenario before naming the source structures that must survive the narrative rendering.

First useful move: name the reader’s question, point to the available material and choose the relations or events the reader needs. Draft a short account, then compare it with that material. Refine the purpose or selection when the comparison exposes a gap. A few sentences can carry these choices; a completed intake form is not required.

What goes wrong if missed: the desired effect determines what the source is said to contain. Readers may remember the account but miss a relevant relation, mistake uncertainty for fact or be unable to find the material needed to check it.

What this buys: a useful account whose selected content supports its purpose and whose unresolved claims remain visible.

Use NSTD.4 when viewpoint or voice is the difficulty, and NSTD.7 when generation needs planning or inspection. Use C.35 only when the generated result is intended to inform architecture work. A separate evidence, ethics or publication question needs its own applicable method; merely drafting an explanation does not open all of those questions.

NSTD.1:2 - Problem

Narrative purpose is useful because a narrative rendering is made for someone and for some use. But ordinary purpose language is often too broad: “make it inspiring”, “tell the story”, “explain the architecture”, “make learners care”. Those phrases do not say which structures must be preserved, which distinctions may be coarsened, and which downstream use is blocked.

NSTD.1:3 - Forces

NSTD.1:4 - Solution

Start with a useful reader question and the available material. Select what the account must preserve, choose a provisional order and try a short narrative. Compare it with the source for omitted relations, unsupported additions and misleading connections. Stop when that account serves the intended use, or name the missing source relation that prevents it.

For example, a paragraph states that a valve opens when pressure exceeds a threshold. An operator asks why the valve opened. The first useful account names that condition and the observed pressure, if available. If only the opening was observed, say that the threshold crossing is still unestablished. Filling a record cannot supply that observation.

Use the following optional intake when another worker must continue the task, several alternatives must be compared or a maintained collection needs the same fields. Include only fields that change that use. The filled records later in this section illustrate richer cases; they are not the minimum entry cost.

NarrativePurposeIntake@Context:
  sourceBasisRefs:
  selectedSourceStructureRefs:
  unfoldingStructureRefs?:
  demonstrativeSliceRefs?:
  sourceStructureSelectionRationale:
  sourceTemporalPosture:
  renderingMediationMode: direct-source-structure | architecture-mediated | mixed
  architectureMediationRef?:
  sourceDefinitionOrConstraintRef?:
  renderingContribution?:
  narrativeVoiceOrViewpoint?:
  generatedDraftInspectionRef?:
  intendedReaderOrListener:
  readerInterestOrUseHypothesis:
  intendedReaderOrListenerUse:
  narrativePurpose:
  likelyMisreading?:
  sourceReturn:
  additionalClaimQuestion?:
  refreshCondition?:

Use unfoldingStructureRefs? only when one selected source structure is governed as a constraint-governed unfolding structure by A.22.CGUS, E.18.3, or a local FPF block. Use demonstrativeSliceRefs? only for the slice the narrative renders for the reader; the slice is not the whole selected structure.

The intake supports these decisions when they matter:

1. Identify the material and selected relations or events, explaining their relevance to the reader’s purpose. State whether they concern past, live, proposed or fictional events when that changes the account.
2. If the account depends on an architecture description, decision or observation record, keep the needed return to that material. A direct explanation of source claims needs no architecture account.
3. Name the writer’s contribution and intended reader in ordinary project terms. Use NSTD.4 when voice or viewpoint changes what the reader can recover; use NSTD.7 for a generated draft. A precise system-role classification or assignment uses A.2 or A.2.1. A claimed dated production Work additionally needs the A.13 and A.15.1 grounds for that claim. None of those precise claims is required merely to ask a teacher or agent for an explanation.
4. Relate the purpose to the selected structure and reader use. Revise the purpose or the selection together when either proves unsuitable.
5. Identify a likely misleading inference only when it changes this use. For example, a plausible incident chronology still leaves its causal explanation open.
6. Give the source or further question to return to when an omitted relation or stronger claim becomes necessary.

For a difficult intake, these four questions can expose the unresolved choice. Stop once the useful choice is clear; they are not four required documents.

A draft can help discover the needed selection. Before relying on it, explain which relations or events matter without using their accidental prominence in that draft as the reason. If the reader’s purpose is still unclear, ask a question or offer a small orientation account that helps settle it. Broader claims about completeness or fidelity remain open.

Use these contrasts when the purpose remains unclear:

• Admissible: “This route helps new FPF readers reconstruct why EntityOfConcern, forces, and neighboring-pattern exits matter during pattern use.” The selected structures are named and the use is reconstructive.
• Below floor for the declared reconstruction lesson: “Make the seminar inspiring so people like FPF.” Motivation can help learners continue, but this purpose does not yet identify the source relations they must reconstruct or use. An expressive-only event can have a different sufficient aim.
• Different task: “Use the narrative to prove FPF is correct.” An account can explain an argument, but the argument’s premises and inferences still need justification. Choosing a narrative purpose does not supply that justification.

For prospective or fictional material, select the relevant canon, premises, design constraints or future-state hypotheses. The narrative may add proposed events within those constraints. If a turn conflicts with them, change the turn or explicitly change the premise; excitement alone does not resolve the conflict. A formal source pack is useful when maintaining canon or comparing alternatives requires it.

When the narrative selects part of a constraint-governed unfolding structure, identify that wider structure and the chosen part. The selected structure may be ConstraintGovernedUnfoldingStructure@Context, an E.18.3 transformation-flow unfolding structure, a P2S local block, an improvement-loop block, or a narrative-ordering block under A.6.3.NAR. The writer may choose one DemonstrativeUnfoldingSlice@Context for the reader’s use. Identify omitted branches, alternatives, loops, constraints or exits when losing them would change the reader’s understanding or next action. The slice is not the whole selected structure and not a work order.

Use role-specific intake prompts when the worker is stuck.

Mood, audience reaction, style or genre can be part of a legitimate purpose. When source fidelity or learning is also intended, those aims leave the needed source selection unanswered. Resolve that question before claiming fidelity or learning; NSTD.4 and NSTD.5 can help realize the expressive aim.

Examples of the optional intake for different uses:

NarrativePurposeIntake@FPFLearningRoute:
  sourceBasisRefs: selected FPF pattern bodies and relation records
  selectedSourceStructureRefs: EntityOfConcern discipline; problem frame; forces; solution; neighboring exits; quality and improvement loop
  unfoldingStructureRefs: A.22.CGUS only when the lesson explicitly teaches source-to-next-use unfolding
  demonstrativeSliceRefs: first seminar route through selected pattern-use positions
  sourceStructureSelectionRationale: learners must reconstruct how a practitioner chooses and uses a pattern
  sourceTemporalPosture: prospective planned learning route over current source corpus
  renderingMediationMode: direct-source-structure unless architecture-of-FPF explanation is opened
  renderingContribution: teacher or course designer
  intendedReaderOrListener: new FPF author or reviewer
  readerInterestOrUseHypothesis: learner needs usable entry, not complete monolith memory
  intendedReaderOrListenerUse: reconstruct one pattern-use route and apply it to a new case
  narrativePurpose: orient attention and sequence learning tasks around source-returnable pattern use
  likelyMisreading?: lesson is not evidence that FPF is correct and not replacement for pattern bodies
  sourceReturn: FPF source patterns and teaching publication-carrier relation
  refreshCondition: FPF edition, learner telemetry, or route evaluation changes

NarrativePurposeIntake@HomotopyExplanation:
  sourceBasisRefs: formal definitions, examples, diagrams, proof-status notes, and selected textbook or lecture source basis
  selectedSourceStructureRefs: definition dependency; example and counterexample relation; theorem prerequisite; formal-source return
  sourceStructureSelectionRationale: learner needs an intuitive route that preserves formal boundaries
  sourceTemporalPosture: retrospective or atemporal explanation over existing mathematical material
  renderingMediationMode: direct-source-structure unless a teaching architecture is explicitly used
  renderingContribution: teacher, explainer, or tool-assisted author
  intendedReaderOrListener: learner who must later distinguish intuition from proof
  readerInterestOrUseHypothesis: learner needs recoverable dependency order and analogy boundary
  intendedReaderOrListenerUse: use examples and return to formal statements without treating metaphor as theorem
  narrativePurpose: make abstractions followable while preserving proof-status boundary
  likelyMisreading?: narrative does not prove the theorem, replace notation, or authorize informal equivalence
  sourceReturn: mathematical source or proof owner
  refreshCondition: source correction, learner failure, or changed learning objective

NarrativePurposeIntake@LiveCommentary:
  sourceBasisRefs: live observations, official event feed, telemetry, recording, later official result
  selectedSourceStructureRefs: event order; score state; possession or control changes; actor roles; uncertainty markers
  sourceStructureSelectionRationale: listener needs orientation during an unfolding event stream
  sourceTemporalPosture: live unfolding source with later refresh
  renderingMediationMode: direct-source-structure
  renderingContribution: commentator or live analyst
  narrativeVoiceOrViewpoint: live commentator voice following the unfolding event under `NSTD.4`
  intendedReaderOrListener: listener following the event and later checking the official event record
  readerInterestOrUseHypothesis: listener needs distinction between observation, inference, prediction, and official correction
  intendedReaderOrListenerUse: follow the event without treating provisional interpretation as fact
  narrativePurpose: maintain orientation and attention under uncertainty
  likelyMisreading?: commentary is not official evidence, blame assignment, or final tactical analysis
  sourceReturn: event source owner, official record, recording, telemetry
  refreshCondition: official correction, telemetry, or post-event evidence changes

NarrativePurposeIntake@FictionalContinuationProbe:
  sourceBasisRefs: selected canon or local source pack for private storycraft test
  selectedSourceStructureRefs: canon constraints; continuity; premise and theme; character agency; causal plot support
  sourceStructureSelectionRationale: storycraft probe tests whether the DPF protects source constraints under dramatic pressure
  sourceTemporalPosture: prospective fictional source structure
  renderingMediationMode: direct-source-structure unless fictional organization or technology architecture is live
  renderingContribution: story designer or tool-assisted writer
  intendedReaderOrListener: private reviewer of storycraft plan
  readerInterestOrUseHypothesis: reviewer needs to see whether continuity and agency survive the route
  intendedReaderOrListenerUse: private design critique, not publication
  narrativePurpose: produce a source-returnable continuation route for testing
  likelyMisreading?: no authorization, no exhaustive canon authority, no publication permission
  sourceReturn: source-pack and canon owner; rights and publication owner when those claims are made
  refreshCondition: source-pack correction, canon selection change, generated-carrier admission change

NSTD.1:4.1 - When claim identity matters

Use the precise construction in A.6.3.NAR:4.0.1 when the receiving use needs identifiable source and narrative claims for citation, dispute, consequential cross-scheme use or another stated reliance requirement. Recover source episteme X, narrative episteme Y and the construction between them; preserve the same EntityOfConcern and test any correspondence on which it depends. Public distribution by itself does not require this fuller account. A permission, evidence or assurance claim still needs its own grounds.

NSTD.1:5 - Archetypal Grounding

NSTD.1:5.1 - Worked slice: FPF seminar from source spine to narrative route

A seminar author receives the request: “Tell a motivating story about FPF so people want to use it.” To turn that aim into a lesson, the author chooses what learners should be able to do: recognize a situation, select a suitable pattern and apply its conditions. The following record shares those choices with another teacher; a sole author could develop them in the draft itself.

NarrativePurposeIntake@FPFSeminarOrientation:
  sourceBasisRefs: selected FPF pattern bodies and relation records
  selectedSourceStructureRefs:
    - EntityOfConcern discipline
    - Problem frame and forces
    - Solution as admissible move under conditions
    - neighboring-pattern exits
    - quality and improvement loop entry
  sourceStructureSelectionRationale: new practitioners fail when they treat patterns as recipes rather than condition-bound moves
  sourceTemporalPosture: prospective planned learning route over current FPF source corpus
  renderingMediationMode: direct-source-structure
  renderingContribution: seminar author
  intendedReaderOrListener: new FPF practitioner; team lead evaluating local adoption
  readerInterestOrUseHypothesis: reader wants a first usable route through FPF without learning every pattern first
  intendedReaderOrListenerUse: reconstruct one pattern-use route and choose the next governing pattern
  narrativePurpose: orient attention and motivation toward source-returnable pattern use
  likelyMisreading?: not proof that FPF is correct; not replacement for pattern bodies; not authority for a local project
  sourceReturn: selected FPF pattern body and relation record
  additionalClaimQuestion: none unless the seminar makes assurance, policy, or affected-party claims
  refreshCondition: FPF edition or selected-source pattern changes; learner reconstruction test fails

The record above makes the choices available to another teacher; the writer can develop them while composing. The first paragraph may be memorable, but every memorable move has a source return. “A pattern is not a recipe” returns to source conditions, forces, and neighboring exits. “Start with the thing being changed” returns to EntityOfConcern. “Do not optimize the visible proxy indicator” returns to quality and proxy-risk owners. The seminar publication carrier can be engaging, but the intake prevents it from becoming a local mythology about FPF.

Evaluation through NSTD.6 later asks whether learners can rebuild the route: identify the source structure, say why the selected order was didactic, name what the story intentionally omitted, and return to the pattern body when they need authority. If learners only repeat the slogan “patterns are not recipes”, NSTD.1 did not select enough source structure for the declared use.

If an LLM produces a seminar draft, the intake keeps three positions separate:

renderingContribution: course-author or generator-operator role; recover the actual system, role assignment, and Work separately when those claims are made
narrativeVoiceOrViewpoint: teacher-facing explanatory voice under NSTD.4
generatedDraftInspectionRef: the NSTD.7 case that identifies the generated draft, source comparison and acceptance for its intended use; C.35 applies only when the result informs architecture work

One person may operate the tool, choose the voice and decide how to use the result. The output still needs comparison with the selected material; authorship alone does not establish its fidelity.

NSTD.1:5.2 - Worked slice: architecture-mediated narrative

An architect wants a narrative explaining a system’s future structure after candidate synthesis. Do not start with “tell the journey from chaos to architecture”. Start by deciding whether the narrative is architecture-mediated. If it is, architecture work remains live before narrative work.

NarrativePurposeIntake@ArchitectureDecisionStory:
  sourceBasisRefs: architecture candidate set, selected architecture description, decision record, expected characteristics, known residuals
  selectedSourceStructureRefs:
    - problem situation and forces
    - candidate structures considered
    - selected structure and rejected alternatives
    - expected architecture characteristics
    - residual exceptions and developer continuation boundary
    - telemetry or later actual-structure feedback condition
  sourceTemporalPosture: prospective future holon structure before implementation
  renderingMediationMode: architecture-mediated
  architectureMediationRef: architecture description and candidate synthesis records
  intendedReaderOrListener: developer team; product steward; later evaluator
  intendedReaderOrListenerUse: understand what structure to preserve while implementing and what may be locally detailed
  narrativePurpose: carry structural intent and trade-off rationale into development work
  likelyMisreading?: not the architecture itself; not implementation order; not assurance that realized structure will match
  sourceReturn: architecture description, architecture decision record, and future telemetry route
  refreshCondition: candidate set, selected architecture, decision, or actual-structure feedback changes

This case teaches the architecture bridge. The narrative worker is not exempt from architecture owners just because the output is prose. C.2.8 is live for the amount of structure this reader can extract, applied through NSTD.6; C.33 is live for architecture-description adequacy; C.34 is live if correspondence between described and realized structure matters; E.17 is live if the carrier is published; architecture decision owners remain live for decision authority. NSTD.1 only binds the narrative purpose to selected structures and reader use.

NSTD.1:5.3 - Worked slice: franchise continuation probe

For a continuation-style storycraft probe using a well-known space-opera franchise such as Star Wars, select the canon, premise and continuity constraints relevant to the proposed scene. A draft can help reveal which of those choices remain unclear. In this example the use is a private critique; a later publication would raise separate rights questions.

The request “Write a surprising sequel that feels epic” leaves those choices open. For the private critique, the writer chooses a continuation premise that preserves a character’s established motivation and the consequences of earlier events. A new event may extend the story; if it conflicts with the chosen continuity, revise the event or explain the changed premise. Ordering and suspense alone cannot repair that conflict.

NSTD.1:5.4 - Role-specific first moves

NSTD.1:5.5 - What this pattern teaches about FPF

NSTD.1 is often the first place where a narrative worker learns why FPF separates selected source material, description, evidence, assurance, ethics, publication, and improvement. A desired effect does not determine what the source supports. The writer chooses a purpose and checks that the selected source relations can support the intended account. This comparison can remain a short explanation; it need not become a formal intake.

An FPF seminar route wants learners to understand why pattern use is condition-based rather than recipe following. The selected source structures are EntityOfConcern, problem frame, forces, solution, consequences, and neighboring-pattern exits. The purpose is orientation for later reconstruction tasks. It is not permission to replace pattern bodies with seminar slogans. Source return points to the FPF patterns and the seminar publication carrier stays outside this DPF body.

A homotopy explanation starts differently. The selected source material is a mathematical corpus: definitions, examples, maps, equivalences, proof-status boundaries, and formal sources. The intended reader is not “any curious person”; it might be an undergraduate who must later distinguish intuitive pictures from formal definitions. The purpose can be “make paths, deformations, and invariants followable”, but the blocked overread says that the narrative does not prove the theorem, replace formal notation, or license analogy as definition. The intake therefore protects formal return before any metaphor is selected.

A live football commentary has a live unfolding source posture. The commentator’s purpose may be orientation and suspense, but the selected structures are event order, score state, possession changes, player actions, provisional interpretation, and later official source return. The intake blocks the overread that a dramatic prediction, blame cue, or emotional framing is evidence. If later official statistics contradict the live interpretation, the refresh condition is not optional.

A franchise-continuation storycraft test uses a prospective fictional source posture. The source structures are selected canon constraints, continuity requirements, premise constraints, character-agency constraints, and non-publication boundary. The purpose may be private storycraft testing, not authorized sequel publication. The private critique establishes no publication rights; consider those separately if the intended use changes.

NSTD.1:6 - Bias-Annotation

A writer can select only the material that supports a desired conclusion. Compare the proposed account with relevant omitted relations and alternatives, then repair its selection or qualify its use. The converse mistake is to demand a completed source-and-role dossier before a simple explanation. Start with the useful account and add documentation only when another use consumes it.

NSTD.1:7 - Conformance Checklist

NSTD.1:8 - Common Anti-Patterns and How to Avoid Them

NSTD.1:9 - Consequences

The reader’s purpose and the source relations guide drafting together. The cost is selecting and comparing the needed content; a maintained intake adds documentation only when later coordination or comparison uses it.

NSTD.1:10 - Rationale

Narrative design begins from audience, communicative aim and available material. Relating those choices prevents the desired effect from silently determining what the source is said to contain. A narrative is the resulting account; the structure-to-narrative construction explains how it draws on the selected source.

NSTD.1:11 - SoTA-Echoing

NSTD.1:11.1 - Operational comparison against domain vocabulary

Narratology distinguishes story, discourse and presentation; cognitive accounts examine event models, perspective and memory; NLG separates content planning, discourse planning and realization. Use these distinctions to ask different practical questions: what material to select, what order to present, what the reader is likely to infer, and what wording to produce. Their terms retain their disciplinary meanings; FPF supplies additional distinctions only where a claim needs them.

For an incident explanation, selecting only events that support the desired conclusion can produce a fluent but misleading story. Selecting the reader’s question together with the relevant events, including an unresolved alternative, yields a draft that can be compared with its source. This DPF combines the source-selection and communication distinctions above for that use. The extra comparison costs effort, so keep it to relations that could change the account or its use. A free fictional invention has a different source obligation: preserve its chosen premises rather than pretend to report an actual event.

Hoffmann’s “The Tensions of Scientific Storytelling” shows that scientific story construction can organize attempts, mechanisms, and unresolved tensions for readers; Schmid’s Narratology: An Introduction and Chihaia’s Introductions to Narratology: Theory, Practice and the Afterlife of Structuralism show that presentation and audience-facing narrative traditions differ by source tradition; Castricato et al.’s “Towards a Formal Model of Narratives” supports explicit narrator-to-reader information flow, reader story-model evolution, and uncertainty; Dahlstrom and Ho’s “Ethical Considerations of Using Narrative to Communicate Science” warns that communicative purpose can become persuasion risk. The DPF uses audience and purpose to guide source selection, and makes temporal posture, mediation and participant distinctions explicit when they affect the narrative’s use. When a purpose, reader-use, science-storytelling, teaching, future-scenario, or persuasion-risk claim depends on a cited source basis, name that source basis and keep the claim within its boundary.

NSTD.1:12 - Relations

Uses A.6.3.NAR to define the Core narrative relation, A.16.1 when the first honest material is only a pre-articulation narrative cue, C.2.LS when language-state facets or thresholds shape the intake, G.2 for SoTA harvesting and synthesis across traditions, C.2.8 for reader-relative structural amount and C.33 for architecture-description adequacy, NSTD.4 for load-bearing voice or viewpoint, NSTD.7 for automated narrative construction and inspection, with C.35 only for a result entering architecture work, NSTD.6 for declared-use narrative evaluation, D.1 through D.5 when affected parties or persuasion are live, A.10 for evidence, B.3 for assurance, E.10 and F.18 for durable wording or naming repairs, and G.11 for source and telemetry refresh. Support-map entry: open Architecture and Narrative Work Bridge when renderingMediationMode is architecture-mediated or mixed; open Source Use And Refresh Map when a cited source basis is relied on or stale; open NSTD.Reference:11 — Working meanings and direct source returns when a local narrative term threatens to become ontology; open Name And Edition Route only for DPF-prefix or edition questions.

NSTD.1:End

NSTD.2 - Choose a Narrative Order That Keeps Needed Source Relations Recoverable

Status: Stable

Type: DPF pattern body

Primary EntityOfConcern: choosing and repairing a narrative sequence so that the reader can follow the relations needed for the intended use.

NSTD.2:1 - Problem frame

Use this pattern when a graph, mechanism, evidence set, architecture structure, candidate set, mathematical dependency structure, canon structure, or source tradition must be put into a sequence and the sequence changes what readers can recover.

First useful move: put a few connected items in a candidate order and compare the sequence with their source relations. If a reader could mistake presentation order for chronology, cause or prerequisite, mark the difference or change the order.

What goes wrong if missed: the order feels natural, but readers silently infer a different order kind: chronology, proof, causality, importance, decision order, work order, or moral priority.

What this buys: a readable path through the material that keeps important dependencies recoverable.

NSTD.2:2 - Problem

Narrative is sequential. Many source structures are not. Trees, graphs, mechanism diagrams, dependency sets, option sets, proof dependencies, and architecture views must be traversed. A chosen order preserves some relations and hides others. If the ordering rule is implicit, a fluent sequence can misrepresent the selected source structure.

NSTD.2:3 - Forces

NSTD.2:4 - Solution

Choose an order that serves the reader’s task, try a short passage and check what it makes the reader infer. Revise the order or add a return to the source when an important relation is hidden. Use the following optional note when a maintained route, handover or comparison needs to retain the choices; an ordinary draft can express them directly.

NarrativeOrderingRule@Context:
  narrativeRenderingRef:
  sourceStructureRefs:
  unfoldingStructureRef?:
  demonstrativeSliceRef?:
  orderingRuleKind:
  orderRationale:
  preservedSourceRelations:
  foregroundedSourceRelations:
  coarsenedOrLostSourceRelations:
  sourceReturnCondition:
  additionalClaimReferences?:

Useful choices include chronology, causal or logical dependency, discovery, teaching prerequisites, tension, viewpoint and decision explanation. These are examples, not an exhaustive classification. A label helps only if the actual sequence shows the needed relation; explain a departure when the reader could otherwise infer the wrong one.

Choose the rule through a four-question ordering test.

An account can combine orders. A lesson may introduce prerequisites, use a discovery story to motivate a distinction, then return to a proof. A live account may follow observations chronologically and a later recap explain causes. A continuation may reveal effects before causes. Make the transition clear wherever the intended reader needs to distinguish those orders.

When the source describes a constraint-governed unfolding structure (CGUS), the narrative follows one traversal or demonstration. Preserve the constraints needed to interpret it. Show omitted alternatives, loops, exits or stop conditions when their omission would change the reader’s choice or action; an illustrative path must not be mistaken for the only possible path or an instruction to execute every step.

Use this repair table when the narrative feels coherent but readers reconstruct the wrong structure.

Evaluate the sequence for its intended use through NSTD.6, including a draft whose order or source relationship is defective. If it conceals a critical dependency, repair that dependency before relying on the passage. A completed ordering note is not required to see the defect.

NSTD.2:5 - Archetypal Grounding

NSTD.2:5.1 - Worked example: choosing a path through a graph

A knowledge graph can connect concepts, dependencies, counterexamples, evidence and practice routes. To introduce part of it, choose a traversal that helps the reader encounter the necessary dependencies. The optional example note below retains those choices for a homotopy introduction.

NarrativeOrderingRule@HomotopyIntro:
  narrativeRenderingRef: HomotopyIntroNarrative@v1
  sourceStructureRefs:
    - topological space
    - path
    - deformation under constraints
    - invariant
    - example and counterexample
    - proof-status boundary
  orderingRuleKind: didactic prerequisite plus analogy-first cue
  orderRationale: learner needs visual intuition before formal return, but formal dependency must remain recoverable
  preservedSourceRelations: prerequisite relation; analogy-to-definition return; example-to-counterexample contrast
  foregroundedSourceRelations: deformation intuition and invariant question
  coarsenedOrLostSourceRelations: full proof order; advanced generality; categorical reformulation
  sourceReturnCondition: use the formal statement and proof when deciding a theorem, equivalence or proof claim
  additionalClaimReferences: `A.6.3.CSC`, `E.17.EFP`, `A.10`, `NSTD.6` when the corresponding claim is made

The introduction can begin with a picture of paths being deformed, then return to the formal definition. For example: “First picture a loop being deformed while its endpoints stay fixed. The next definition specifies which deformations are allowed.” This connects the intuitive sequence to its missing mathematical condition.

NSTD.2:5.2 - Before and after repair: architecture order

Before:

We tried several designs and eventually found the architecture that solved the coordination problem.

Failure: “eventually” supplies a chronology, while “solved” asserts a successful result. The account does not say which coordination problem was addressed, what trade-off was accepted or what observation supports success.

After:

Begin with the coordination problem, compare the candidate module splits, then explain the chosen trade-off and remaining interface exceptions. Consult the decision record for why that split was selected and observations of the implemented system for whether it reduced coordination work.

What changed: the explanation connects the choice to its problem, alternatives and remaining cost. A reader seeking the implementation sequence or an observed outcome has a different source to consult.

NSTD.2:5.3 - Before and after repair: live commentary

Before:

The midfield is late, so the press has failed, and that is why the match is turning.

Failure: live chronological observation is mixed with causal explanation and outcome projection. The source at that moment may support late movement and lost possession, but not a settled causal account.

After:

The midfield line arrived after the forwards began pressing, leaving space between them. That gap may explain the lost possession; the replay can help distinguish this explanation from a missed individual challenge.

What changed: the observed sequence remains distinct from the provisional explanation, with a specific question for later review.

NSTD.2:5.4 - Comparing candidate orders

Use NSTD.6 when a qualified quality result is needed. The number of worked examples alone does not determine an ordering-quality value.

NSTD.2:5.5 - SoTA-to-action translation

Narratology distinguishes selected material, story, discourse and presentation. Here those distinctions help the author separate what is included from the order in which it is encountered. NLG likewise distinguishes content selection, document planning and wording. A smooth sentence can still present a dependency in a misleading place.

A homotopy-theory explanation orders material by learner dependency: spaces, paths, homotopy, fundamental group, examples, proof-status boundaries. This is not the historical discovery order and not the formal proof order of a research monograph. The narrative must state that definitions and proof obligations remain in source-return formal statements.

Consider this constructed decision source: two teams maintain the same validation rule in separate modules. They compare a shared library with a shared service, then choose the service so that a rule change can be deployed once. They accept an extra service call and client handling of version mismatches. These are design expectations; runtime effects have not been measured.

Two short orders preserve the same source:

• Cost first: “The chosen service adds a call and requires version-mismatch handling. The teams accepted these costs to deploy a shared validation rule once, after comparing a library with a service. The runtime effect is not yet measured.”
• Decision first: “To deploy a shared validation rule once, the teams chose a service over a shared library. They accepted the extra call and version-mismatch handling; the runtime effect is not yet measured.”

For a new maintainer asking why the service was selected, the second order foregrounds the reason. For a reader investigating the added call, the first order foregrounds the relevant cost. Neither order supplies an observed improvement. Use the decision source for further alternative detail and measurements for a claim about the realized effect.

A franchise-continuation outline may order scenes by reveal and tension. That does not mean reveal order is causal order. The underlying causal and continuity order must still name premise constraint, character motivation, event cause, consequence, and canon-return point. If a later twist works only because a source constraint was hidden from the writer as well as from the reader, the order is not a legitimate reveal; it is a source-selection failure.

A scientific storytelling case may order experiments by tension: failed attempt, surprising measurement, revised hypothesis, unresolved conflict. That order can be useful because it mirrors inquiry, but it cannot make unresolved tension into evidence closure. The sequence must name which calculations, mechanisms, and experimental facts remain source-return points.

Worked repair sequence:

1. Initial symptom: “The team first tried A, then B, and finally discovered the right architecture.”
2. Hidden-order diagnosis: chronology is being read as decision quality and finality.
3. Source topology repair: name candidate structures, quality characteristics, rejected alternatives, and telemetry or decision basis.
4. Ordering repair: present the problem, alternatives and trade-off; distinguish that explanation from the implementation sequence.
5. Loss repair: state what the narrative omits, such as lower-level exceptions or candidates excluded for scope.
6. Source-return repair: link to architecture description, decision record, or candidate comparison when a reader needs authority.

Second worked repair sequence:

1. Initial symptom: “We introduce homotopy with loops, then groups, then examples, because that is the natural story.”
2. Hidden-order diagnosis: “natural story” hides the didactic prerequisite order and may be mistaken for formal proof order.
3. Source topology repair: list definitions, examples, theorem prerequisites, proof-status boundaries, and formal-source returns.
4. Ordering rule repair: choose didactic dependency order and explicitly state where it diverges from formal order.
5. Loss repair: record which formal details are deferred and where they return.
6. Evaluation repair: NSTD.6 checks whether learners can reconstruct dependency and proof boundaries, not whether they enjoyed the story.

Case matrix for ordering work:

Use the matrix when comparing possible orders. It can guide a first draft or diagnose an existing passage. Reconstructing an earlier author’s choices is useful for repair; judging the current sequence does not require establishing how it was originally written.

When two orders conflict, preserve both as named layers. A learning route may teach prerequisites first and later show historical discovery. A mystery-like story may reveal effects before causes while keeping an internal causal order. A live recap may reorder events by causal explanation after first recording live chronology. The reader must be told which layer they are following.

NSTD.2:6 - Bias-Annotation

This pattern blocks natural-sequence drift: a chronological, didactic, dramatic, traversal, or slide order is treated as if it were the source structure itself. The bias is especially likely when the order feels intuitive to the author. Repair by naming the ordering rule, preserved relations, foregrounded relations, lost relations, and source-return condition. Scope: DPF-local for source-structure-to-sequence rendering; it does not govern general serialization formats or publication order.

NSTD.2:7 - Conformance Checklist

NSTD.2:8 - Common Anti-Patterns and How to Avoid Them

NSTD.2:9 - Consequences

The reader can follow a manageable path without losing a necessary relation. The author must spend enough attention comparing the sequence with the source to detect omissions that matter.

NSTD.2:10 - Rationale

Narrative sequence is a transformation over structure. Making the ordering rule explicit preserves the useful similarity between serialization and narrativization: both choose an order for a structure, both preserve and lose relations, and both need a return path when the order is relied on.

NSTD.2:11 - SoTA-Echoing

Schmid’s Narratology: An Introduction distinguishes happenings, story, narrative and presentation. Chihaia’s survey of narratology introductions shows differences of tradition and audience. These are historical conceptual anchors. Gatt and Krahmer’s NLG survey distinguishes content selection from text structuring and realization. Cardona Rivera, Jhala, Porteous and Young’s The Story So Far on Narrative Planning examines plan-based construction and communication of stories. This pattern synthesizes those distinctions into an ordering method; it does not require a formal plan for every account.

Operational payload:

• From Schmid, distinguish selection, composition and linearization. Well-chosen material may still be ordered badly, so compare NSTD.2 ordering separately from NSTD.1 selection.
• From Chihaia, interpret terms such as plot, discourse or fabula within the tradition using them. Explain the ordering consequence when different traditions use a term differently.
• From NLG, distinguish what to say from how to order and express it. Inspect the needed content when fluent realization leaves the reader’s reconstruction incomplete.
• From narrative planning, distinguish the order of events from their presentation. Mark a divergence when it could mislead the reader about causality or dependency.
• For an architecture explanation, compare the account with the relevant structures and views. Use C.30.ASV, C.33 or C.34 only for the architecture question each defines.

For a short explanation whose reader must distinguish event order from cause or prerequisite, the best-supported line here is to keep those relations available while choosing the presentation order. The serious default is to preserve source order and improve only the prose. Compare two equally short accounts of the incident in the Readme: both retain the logged times, but the relation-aware account leaves the causal investigation open. Source order alone cannot expose that difference; the added comparison is justified by the reader’s remedy decision, not by a preference for more elaborate planning.

Adapt the distinction between content, structure and realization from NLG, and between events and their communication from narrative planning, in :4’s short-sequence comparison. Reject a required formal plan for an ordinary account: its cost is unnecessary when a few relations can be compared directly. For suspense or aesthetic rhythm, accept a different order when its effect matters and the needed relation remains available. Reopen this choice if a changed reader task requires another relation, if a reader repeatedly reconstructs the wrong order, or if an equally economical alternative preserves those relations more clearly.

NSTD.2:12 - Relations

Uses A.6.3.NAR, A.6.3.CSC, C.2.8 for structural amount, C.33 for architecture-description adequacy, C.34, E.17, E.17.EFP, A.16.2 when a route must back off or respecify after overcommitment, A.6.P when ordering rationale hides relation-kind claims, NSTD.6, and G.11. NSTD.6 applies the same C.2.8 characteristic to narrative recovery from architecture and non-architecture source domains. Reopen when source structure, reader use, ordering rule, source-return condition, route authority, relation precision, or low NSTD.6 ordering value changes. Support-map entry: open Architecture and Narrative Work Bridge when sequence is over architecture views, candidate structures, descriptions, correspondence, or actual-structure feedback; open Semiotic And Language-Precision Bridge or NSTD.Reference:11 — Working meanings and direct source returns when ordering terms hide coarsening, relation-kind, or quality claims.

NSTD.2:End

NSTD.3 - Repair Missing or Unsupported Narrative Connections (Coherence and Event Models)

Status: Stable

Type: DPF pattern body

Primary EntityOfConcern: repairing the connections through which a reader reconstructs a narrative’s events, mechanisms or dependencies.

NSTD.3:1 - Problem frame

Use this pattern when locally fluent narrative passages fail because readers cannot build a coherent model of source mechanism, event flow, dependency structure, architecture relation, state change, or proof dependency.

First useful move: take one passage the reader cannot explain, state the connection it suggests and compare it with the source or fictional premises. Add the missing connection, qualify an unsupported one or keep the unresolved question visible.

What goes wrong if missed: fluency is mistaken for source coherence. Readers remember the story but cannot say what changed, why it changed, which relation mattered, or where the claim stops.

What this buys: coherence is tied to recoverable source structure, not to smooth prose alone.

NSTD.3:2 - Problem

Narratives often use events and agents because they are easy to follow. But many source structures are not event sequences. Architecture structures, mathematical definitions, evidence graphs, mechanism diagrams, and source packs can be misread when forced into a fiction-like event model.

NSTD.3:3 - Forces

NSTD.3:4 - Solution

Work on the connection the reader needs: what changed, what depends on what, why an action follows or which condition limits the conclusion. The optional note below is useful when several passages, collaborators or later comparisons need to retain that analysis. A single passage can be repaired directly.

NarrativeEventMechanismSupport@Context:
  narrativeRenderingRef:
  sourceStructureKind:
  requiredReaderReconstruction:
  eventOrMechanismModel:
  participants?:
  dependencyOrConstraintRefs?:
  causalClaimBasis?:
  uncertaintyOrUnknownRefs?:
  reconstructionTaskRefs?:
  sourceReturnCondition:

Compare the intended reconstruction with the passage and its source. An unknown source relation and a relation merely omitted from the explanation call for different repairs.

Use the following questions to repair a passage; retain answers only where the working use needs them.

1. State the connection on which the passage depends, its source or premise, and what remains unknown.
2. Identify the relation and its grounds. For example, a time sequence, mathematical dependency, physical cause and fictional motivation answer different questions; they are not successive strengths on one scale.
3. State what the reader needs to reconstruct: for example a state change, explanation, prediction or limit of an analogy.
4. Find wording or omissions that invite a different reconstruction from the one supported.
5. Repair the connection: supply a missing step, correct its kind or strength, add a relevant uncertainty, or return to the source question. Keep a strong claim when its grounds support it; weakening every claim can also mislead.

Connectors are cues to inspect the complete claim, not automatic triggers for another procedure.

Reader reconstruction tasks should be concrete:

• “Name the mechanism and the unresolved relation” is better than “understand the mechanism.”
• “Distinguish observed event, inference, and prediction” is better than “follow the live story.”
• “Point to the formal statement where the analogy stops” is better than “get the math intuition.”
• “Recover which architecture trade-off was accepted and which exception remains” is better than “remember the project story.”

If the required reconstruction cannot yet be stated, clarify what the reader needs to do with the passage. Entertainment or initial orientation can be sufficient aims. A use that depends on a mechanism or inference needs a recoverable account of that relation.

NSTD.3:5 - Archetypal Grounding

NSTD.3:5.1 - Worked example: event support

A science narrative says: “The failed experiment forced the theory to change.” Compare the observed result with the prediction and alternatives: was a consequence refuted, an auxiliary assumption questioned, or a replacement supported? The repair should say which of those happened.

NarrativeEventSupportRecord@ExperimentTension:
  narrativeRenderingRef: ScienceStory@v1
  eventOrMechanismClaim: failed measurement challenged the prior mechanism hypothesis
  sourceStructureRef: measurement record, model expectation, uncertainty interval, alternative explanations
  relationStrength: observed mismatch plus mechanism hypothesis, not proof of forced theory change
  reconstructionTarget: reader can distinguish observed result, hypothesis pressure, and later evidence
  overclaimRisk: "forced", "proved", "settled", and "therefore" make the relation too strong
  sourceReturnCondition: return to the measurement and model assumptions when a stronger conclusion is needed

Before:

The experiment failed, so the old theory collapsed.

After:

The measured value lay outside the range predicted under these assumptions. The discrepancy calls for examining the mechanism model and the measurement assumptions; this experiment does not yet distinguish the proposed replacements.

The repaired passage retains the surprising result and the next research question, while distinguishing the mismatch from the still-undecided explanation.

NSTD.3:5.2 - Worked example: franchise plot support

In a continuation-style storycraft probe, a scene says that a character betrays an ally “because the plot needs a darker turn.” That is a narrative-function explanation, not source support. Repair it as source structure:

NarrativeEventSupportRecord@CharacterTurn:
  eventOrMechanismClaim: character changes allegiance under named pressure
  sourceStructureRef: selected canon constraint, prior motivation, current dilemma, consequence chain
  relationStrength: a proposed motive consistent with the selected fictional premises
  reconstructionTarget: reader can state motive, pressure, action, consequence, and canon-return condition
  overclaimRisk: author need or theme is treated as character cause
  sourceReturnCondition: return to source pack and agency constraints

For a story whose events should follow intelligible motives, the author’s desire for a twist does not supply the character’s reason. Add a pressure, choice or event that makes the turn intelligible, or revise the turn. A deliberately unexplained or absurd turn has a different artistic aim and should be judged for that aim.

NSTD.3:5.3 - Comparing relation support

These are diagnostic situations. Use NSTD.6 for a qualified evaluation rather than deriving a score from the presence of a support record.

NSTD.3:5.4 - Connecting to the relevant subject method

A connector does not settle the relation it expresses. “Because” can introduce a physical cause, a reason for acting or a mathematical dependence. Identify that relation first; open the corresponding FPF or subject method when the relation itself needs further work.

Suppose a design comparison says a proposed modular split removes one required hand-off between teams, but sends exceptional requests through a shared interface. The narrative can explain that change in dependency. Less routine coordination work is a prediction from the design; its realized cost remains unknown until observed. If observations are available, report the supported result rather than automatically weakening it to a prediction.

A science story can say that an experimental result “forced” a revised hypothesis only if the source line supports that constraint. Often the honest relation is weaker: the result made one hypothesis less useful, exposed a tension, or suggested a new mechanism to test. NSTD.3 keeps the tension narratable while preventing the narrative from closing evidence that the source left open.

A live match commentary may connect a late midfield movement with lost possession. State the observed sequence separately from that provisional tactical explanation, and identify what the replay could resolve.

In a homotopy explanation, a deformation story may help learners track invariance, but it is not a proof by itself. The support record says which formal relation the story illustrates, what the learner should reconstruct, and where analogy must return to definitions or proof-status boundaries.

Use rewrite diagnostics when a sentence sounds good but may overclaim.

These are conditional repairs, not substitutes to copy without their premises. For a supported strong case, suppose the mathematical source defines f(x) = 2x and the task supplies x = 3. “Under this definition, f(3) = 6” follows directly; weakening it to “perhaps 6” would lose the supported result. If the source instead contains only an input-output observation of 3 and 6, keep that observed pair and leave the general doubling rule unresolved. The words become no weaker or stronger than the supplied relation warrants.

If the repair makes the narrative less exciting, that is not automatically a defect. The repair preserves the source relation. Engagement can be rebuilt later through NSTD.5 around the safer relation instead of by restoring the overclaim.

Optional notes for more involved comparisons:

NarrativeEventMechanismSupport@ArchitectureTradeoff:
  sourceStructureKind: architecture-like and mechanism-like trade-off
  requiredReaderReconstruction: which required hand-off the proposed design removes, where exceptional requests go, and why an observed time saving remains unknown
  eventOrMechanismModel: ordinary requests no longer cross the removed hand-off; exceptional requests still require shared-interface coordination
  dependencyOrConstraintRefs: before-and-after dependency diagram; rule selecting exceptional requests; shared-interface responsibility
  supportingBasis: the stated design supports the dependency change and a conditional cost prediction; observed cost would need observations
  uncertaintyOrUnknownRefs: realized coordination time unmeasured; other candidate designs outside this sketch
  reconstructionTaskRefs: reader distinguishes the design change, remaining exception work and unmeasured cost effect
  sourceReturnCondition: consult the dependency comparison for the design claim and observations for an actual cost claim

NarrativeEventMechanismSupport@HomotopyAnalogy:
  sourceStructureKind: proof-like and definition-like dependency
  requiredReaderReconstruction: distinguish intuitive deformation image from formal equivalence relation
  eventOrMechanismModel: path deformation story used as analogy for invariant tracking
  dependencyOrConstraintRefs: formal definitions; examples; counterexamples; theorem prerequisites
  causalUseOwnerRef: none unless a causal learning claim is made
  uncertaintyOrUnknownRefs: analogy may fail outside named examples
  reconstructionTaskRefs: learner states where analogy stops and where proof returns
  sourceReturnCondition: formal source statement for proof or exercise use

NarrativeEventMechanismSupport@LiveCommentary:
  sourceStructureKind: live event stream with provisional interpretations
  requiredReaderReconstruction: observed event vs inference vs prediction vs official correction
  eventOrMechanismModel: state updates and tactical hypothesis under uncertainty
  participatingHolonOrRoleRefs: teams, players, officials, broadcast or event source roles when needed
  uncertaintyOrUnknownRefs: off-camera events; later telemetry; official review
  reconstructionTaskRefs: listener can say what was observed and what was inferred
  sourceReturnCondition: official record, recording, statistics, or telemetry

These sketches illustrate information that can matter in different cases. Use only the fields needed to repair or compare the passage. A missing field does not by itself make a coherent account inadequate.

NSTD.3:6 - Bias-Annotation

This pattern blocks fluent-coherence drift: smooth event language is mistaken for a mechanism, dependency, architecture, proof, or causal model. The bias appears when readers can retell the story but cannot reconstruct the selected source relation. Repair by naming the source-structure kind, the reconstruction target, the owner for causal or dependency claims, and the source-return condition. Scope: DPF-local for narrative coherence over selected source structure; it does not certify mechanism truth or causal evidence.

NSTD.3:7 - Conformance Checklist

NSTD.3:8 - Common Anti-Patterns and How to Avoid Them

NSTD.3:9 - Consequences

The benefit is that narrative coherence becomes testable. The cost is that some dramatic simplifications must be weakened or paired with source return.

NSTD.3:10 - Rationale

Narrative comprehension often depends on event models and causal schemas. FPF uses that strength but keeps event support distinct from causal evidence, mechanism truth, architecture evaluation, and proof status.

NSTD.3:11 - SoTA-Echoing

Nguyen’s A Review of Mechanistic Models of Event Comprehension (2024) compares accounts of prediction, hierarchy, updating and causal representation in comprehension. Hoffmann’s The Tensions of Scientific Storytelling (2014) illustrates how scientific accounts organize mechanisms and unresolved tensions. Gatt and Krahmer’s NLG survey (2018) distinguishes content selection and realization. This pattern’s synthesis is to compare the connection the passage suggests with the relation its source or premises support.

Operational payload:

• Event-comprehension models motivate checking the reader’s event boundaries, dependencies and predictions when those matter to the use. They do not establish that every reader builds the same model from every narrative.
• From scientific storytelling, unresolved tension is narratively useful. It must stay unresolved when the source is unresolved. A good story may preserve tension rather than close it.
• From NLG, inspect content as well as realization: a fluent connector cannot supply an omitted premise.
• For evidence, inference and causal claims, inspect the complete claim before selecting additional work. The occurrence of “shows”, “proves” or “because” alone does not require an assurance procedure.
• From architecture work, a mechanism-like story about structure must keep trade-offs, residual exceptions, and telemetry distinct. A before-and-after story is not by itself an architecture evaluation.

For a passage that implies an unsupported connection, the selected line is to inspect the event or dependency relation before polishing its connector. A serious alternative is local wording repair: replace “proved” by “suggested” or “caused” by “preceded”. At comparable effort on the one disputed sentence, that can be sufficient when it states what the source establishes; it fails when the weaker replacement also invents a fact. The incident case shows the decisive difference: retain the logged sequence and leave the cause unresolved instead of supplying a plausible mechanism.

Adapt event-model and content-planning distinctions in :4’s source comparison and :5’s diagnostics. Adopt scientific storytelling’s use of unresolved tension: the next investigation can remain part of the account. The accepted cost is consulting the relevant source relation rather than guessing a safer-sounding sentence. Keep a strong conclusion when that source supports it. Reopen if a new observation or argument establishes the connection, if the intended use needs a different relation, or if the reader still infers more than the repaired passage supports.

NSTD.3:12 - Relations

Uses A.6.3.NAR, NSTD.2, C.28, A.10, B.3, C.2.8 for structural amount, C.33 for architecture-description adequacy, C.34, NSTD.6, and G.11. Mechanism-support recovery can supply a C.2.8 structural result through NSTD.6; the event-mechanism quality judgement retains its own meaning and evidence. Reopen when the source mechanism, causal support, reconstruction target, or evaluation result changes. Support-map entry: open Architecture and Narrative Work Bridge when event, mechanism, dependency, or coherence support is architecture-relevant; open Source Use And Refresh Map when a source or cognition claim supports reconstructability; open NSTD.Reference:11 — Working meanings and direct source returns when event, mechanism, coherence, support, or cause language starts doing evidence or quality work.

NSTD.3:End

NSTD.4 - Choose Narrative Voice and Focalization while Keeping Agency Claims Grounded

Status: Stable

Type: DPF pattern body

Primary EntityOfConcern: choosing and repairing narrative voice and viewpoint so that the reader can recover the relevant events, participants and responsibilities.

NSTD.4:1 - Problem frame

Use this pattern when narrator, voice, viewpoint, focalized object, protagonist, actant, personification, or agency treatment changes what a reader understands, remembers, trusts, blames, or treats as capable of action.

First useful move: state viewpoint or focalized object, what it reveals, what it hides, and whether any source bearer is being personified or treated as an actor.

What goes wrong if missed: viewpoint looks like style while it changes source visibility and responsibility assignment. A structure, institution, model, or document can be written as if it decided, wanted, knew, or authorized.

What this buys: the narrative can use viewpoint and protagonist design without smuggling agency, capability, responsibility, or moral permission.

NSTD.4:2 - Problem

A narrator’s position determines what can be told and how it is presented. The reader may nevertheless attribute an action, knowledge or responsibility to a participant merely because that participant is prominent in the story. Choose the viewpoint for its narrative contribution and establish any consequential attribution on its own grounds.

NSTD.4:3 - Forces

NSTD.4:4 - Solution

Compare what the chosen viewpoint makes visible with what the reader needs. Add another view or a short clarification when a consequential relation is hidden. Use the optional record below when comparing viewpoints or handing the work to another author; the clarification can otherwise stay in the narrative itself.

NarrativeViewpointAgencyDiscipline@Context:
  narrativeRenderingRef:
  viewpointOrVoice:
  focalizedObjectRef:
  revealedSourceStructureRefs:
  hiddenOrWeakenedSourceStructureRefs:
  narrativeFunctionTerms:
  personificationOrAgencyWording:
  directOwnerRefs:
  blockedAgencyOverread:
  repairAction:

Use the following distinctions only when they change interpretation or action:

1. A narrative function such as narrator, protagonist or actant describes a contribution to the account. Ordinary use of “role” can retain that meaning.
2. A real participant may be a person, organization or technical system. When a precise classification matters, A.2 defines a local system-role kind whose candidates are U.System individuals. A.2.1 separately establishes an obtaining U.SystemRoleAssignment; neither a label nor prominence in a story supplies that assignment.
3. A precise agency claim uses A.13: the System, the applicable local kind and the obtaining assignment. A claimed dated Work occurrence additionally uses A.15.1. Ordinary explanation does not require these identities unless it asserts the corresponding facts.
4. A capability or responsibility claim needs its own grounds. Use A.2.2 for capability, the applicable organizational assignment for responsibility, and D.1 through D.5 when value, harm or affected-party conflicts matter.
5. An agency measurement or profile uses the selected characteristic and scale through A.19.ECS, C.16 and A.13 when that additional claim is needed.

Consider the following questions where the viewpoint could change the reader’s understanding or action.

The following terms answer different narrative questions. Stronger factual claims require additional grounds.

Keep ordinary metonymy when the intended reader can recover the relevant action and participant. “The paper proves the lemma” can refer to the proof it contains; it needs no invented author-work record. If “the architecture wants fewer dependencies” would instead be used to justify a decision or assign blame, state the actual structural constraint, choice and responsible participant. Clarify the action-changing ambiguity, not every figurative verb.

A useful repair can retain the viewpoint while making the needed relation explicit: who decides, what structure is highlighted, what relevant fact is hidden, and where the reader can obtain it. Choose the smallest clarification that resolves the difficulty.

NSTD.4:5 - Archetypal Grounding

NSTD.4:5.1 - Worked slice: viewpoint without false agency

An architecture explanation says: “The database wants to protect consistency, while the service wants speed.” This personification can foreground a trade-off. For a reader diagnosing latency, however, the needed relation is how transaction and replication choices affect response time.

NarrativeViewpointRecord@ArchitecturePersonification:
  narrativeRenderingRef: ArchitectureExplanation@v1
  viewpointOrVoiceKind: didactic personification
  focalizedSourceStructureRef: consistency and latency trade-off across selected architecture structures
  narrativeFunction: make the trade-off memorable and traversable
  hiddenOrWeakenedSourceStructureRefs: actual component responsibility, decision record, measured characteristics
  agencyOrResponsibilityRisk: component metaphor may be read as actor agency or authority
  literalizationRepair: explain the commit condition and latency consequence; identify who can change the configuration if that action is proposed
  sourceReturnCondition: return to architecture description and decision record for authority

Before:

The database refuses to let the service move fast.

After:

In this configuration the database waits for replica acknowledgement before confirming a commit. That choice protects the required consistency but increases the service’s response time. To change the trade-off, consult the configuration decision and measured latency; the personification only helped introduce it.

This repair keeps the narrative value while protecting ontology. The viewpoint is a lens over selected source structures, not a new actor.

NSTD.4:5.2 - Worked slice: narrator and reader roles

A future-project scenario can speak from an imagined user’s viewpoint to expose possible consequences. Describe it as a scenario so readers can distinguish the proposed experience from an actual user’s report or consultation. For example:

NarrativeViewpointRecord@FutureUserScenario:
  viewpointOrVoiceKind: prospective scenario voice
  focalizedSourceStructureRef: expected use situation and system interaction
  narrativeFunction: expose usability and risk questions before design is final
  hiddenOrWeakenedSourceStructureRefs: actual user evidence, policy claim, safety claim
  agencyOrResponsibilityRisk: imagined voice is treated as real stakeholder authority
  literalizationRepair: mark as scenario hypothesis and route evidence to user research owner
  sourceReturnCondition: return to source assumptions and later evidence

NSTD.4:5.3 - Choosing a viewpoint repair

Keep wording that already makes the relevant action clear. If a viewpoint hides a needed relation, add that relation, change perspective or name the responsible participant. Mark a scenario or metaphor when the reader could otherwise rely on it as an observation. Replace the device if its effect depends on concealing a fact needed for the intended use.

To compare alternatives, try a short literal account or another viewpoint and ask what the reader can now recover. For the database case, the comparison is whether the reader can explain the wait and locate the configurable choice. For the future-user case, it is whether the reader distinguishes a proposed experience from observed user evidence. Use NSTD.6 when a declared quality result is needed; these diagnostic questions are not a second ordinal scale.

NSTD.4:5.4 - FPF owner teaching

Viewpoint selects and highlights structure for a use. An architect’s view, a narrator’s voice and a protagonist’s function can help recover different aspects of the same case. When a real agency, assignment, capability or responsibility claim matters, recover that claim separately under its applicable definition.

A technical story says “the architecture wants to reduce coupling.” The useful content may be a criterion favoring fewer dependencies under a stated trade-off. An architect or team makes the choice; a system-role assignment is a relation involving that participant, not the participant itself. An architecture decision records or expresses the choice rather than acting as its maker.

In a franchise continuation, a protagonist centers attention, while the chosen premises determine what action is plausible. “The Force guided the decision” may be a sufficient story-world explanation in one scene and leave a character’s motivation unclear in another. Use the intended plot and reader effect to decide whether another connection is needed.

In a homotopy explanation, a space, path, or loop may be written as if it “wants” to deform or “remembers” a hole. That can help intuition, but the focalized object is not an agent. The repair is to state the formal relation being highlighted and where the personification stops.

In live commentary, viewpoint may follow one player, coach or tactical unit. This can make the stream intelligible while hiding off-ball actions or an uncertain ruling. Qualify a blame or capability claim when the unseen action or later official correction could change it; no commentary record is required merely to say so.

Use a literalization rewrite ladder.

Keep a necessary clarification close to the phrase. For example: “The architecture favors fewer dependencies under the selected trade-off.” If the figurative wording already conveys that relation unambiguously, no extra disclaimer is needed.

Use alternate viewpoint when one viewpoint hides a load-bearing source structure. A learner-facing story may first focalize the novice, then briefly switch to the maintainer who pays the cost of hidden coupling. A live commentary may follow the attacking player, then mark what the defensive line or official review could change. A future-scenario narrative may focalize a user, then return to the system owner for constraints and responsibility.

Filled viewpoint records:

NarrativeViewpointAgencyDiscipline@ArchitecturePersonification:
  viewpointOrVoice: teacher voice using personification
  focalizedObjectRef: selected architecture candidate
  revealedSourceStructureRefs: coupling pressure; cohesion target; interface exception
  hiddenOrWeakenedSourceStructureRefs: architect role assignment; decision record; telemetry
  narrativeFunctionTerms: "architecture wants" as memory aid
  personificationOrAgencyWording: architecture described as wanting fewer dependencies
  directOwnerRefs: architect role assignment; architecture decision; characteristic evaluation
  blockedAgencyOverread: architecture is not an agent and has no responsibility
  repairAction: add "more precisely" sentence naming characteristic pressure and decision owner

NarrativeViewpointAgencyDiscipline@FictionalProtagonistProbe:
  viewpointOrVoice: close protagonist viewpoint for private storycraft testing
  focalizedObjectRef: protagonist function in continuation route
  revealedSourceStructureRefs: character agency constraint; premise; causal plot support
  hiddenOrWeakenedSourceStructureRefs: alternative viewpoints; broader canon conflicts; publication rights
  narrativeFunctionTerms: protagonist; actant; motivation
  directOwnerRefs: source-pack and canon owner; agency and role owner when moral responsibility is claimed
  blockedAgencyOverread: protagonist centrality does not create moral permission or canon authority
  repairAction: record character action support and route rights and publication outside this DPF

NarrativeViewpointAgencyDiscipline@LiveCommentaryView:
  viewpointOrVoice: commentator follows attacking side under time pressure
  focalizedObjectRef: attacking player or unit
  revealedSourceStructureRefs: possession, pressure, chance creation
  hiddenOrWeakenedSourceStructureRefs: defensive shape, off-ball movement, official review
  narrativeFunctionTerms: "forced", "wanted", "could not"
  directOwnerRefs: event source owner; evidence owner for claims; ethics owner if blame or harm framing appears
  blockedAgencyOverread: live focalization is not settled blame or capability assessment
  repairAction: mark provisional interpretation and later source-return route

Before relying on a strong agency claim, resolve the actual ambiguity in the text. A compact explanation can identify the acting system, the decision or the limited metaphor. Use a record only when its later use warrants one; lowering every verb to “is presented as” would itself obscure real actions.

NSTD.4:6 - Bias-Annotation

A vivid protagonist or personification can draw attention away from the grounds of an attribution. Compare the narrative function with the actual action, capability or responsibility being claimed, and repair only the consequential mismatch.

NSTD.4:7 - Conformance Checklist

NSTD.4:8 - Common Anti-Patterns and How to Avoid Them

NSTD.4:9 - Consequences

The benefit is a usable viewpoint with clearer attribution. The cost is comparing what the viewpoint shows with what the reader needs; a short clarification may be enough.

NSTD.4:10 - Rationale

Voice and focalization change access to events, knowledge and consequences. A single viewpoint is often sufficient for a scene; an explanation or decision may need another perspective when the first conceals a relevant participant or relation.

NSTD.4:11 - SoTA-Echoing

Schmid’s Narratology: An Introduction and Chihaia’s survey of introductions are historical anchors for voice, viewpoint and narratological traditions. Chen and Xu’s perspective and focalization study (2026) found differences in reading-time and neural responses in its novel-reading tasks; it does not establish a universally better perspective. Nguyen-Trung and Nguyen’s NITA (2026) preserves the qualitative researcher’s interpretive contribution. The distinction here between narrative function and actual agency is the DPF’s synthesis with FPF, not a result established by those reading experiments.

For the database explanation, keeping the personification alone is a serious alternative: it is short and memorable. Adding the commit condition makes the latency consequence available for diagnosis while retaining the introduction. This is the pattern’s selected combination of narrative viewpoint and explicit attribution. Its cost is a short technical clarification, justified here by the diagnostic use; purely expressive uses need a different comparison.

Use the cited traditions for their distinct contributions. Narratology supplies voice and focalization; perspective-processing studies show that viewpoint can change reading responses in the studied conditions. NITA concerns interpretation in qualitative research, not mandatory human approval of every generated story. FPF’s role and agency distinctions apply when a real attribution needs to be resolved.

NSTD.4:12 - Relations

Uses A.6.3.NAR, A.13, A.2, A.2.1, A.2.2, A.19.ECS, C.16, D.1 through D.5, A.10, B.3, and G.11. Reopen when viewpoint changes source visibility or when new source-pack or FPF agency owners change the owner map. Support-map entry: open Architecture and Narrative Work Bridge when viewpoint or focalization is really an architecture view and viewpoint over selected structures; open Semiotic And Language-Precision Bridge when voice, focalization, salience, sign, or language-state choice changes interpretation; open NSTD.Reference:11 — Working meanings and direct source returns when protagonist, actant, agency, personification, or responsibility wording needs owner split.

NSTD.4:End

NSTD.5 - Choose Narrative Engagement Devices for the Intended Experience or Use

Status: Stable

Type: DPF pattern body

Primary EntityOfConcern: designing and revising narrative devices that help the intended reader attend, remember or continue, while preserving the relations and choices on which that use depends.

NSTD.5:1 - Problem frame

Use this pattern when readers lose attention before reaching a needed distinction, remember the wrong feature, or draw unwarranted confidence from an engaging account. It also applies when suspense, identification or another expressive effect is part of the intended experience.

First useful move: name the reader effect that would help, try one device in a short passage and compare it with a sufficient simpler version. Keep the device if its benefit justifies its cost without distorting a relation or choice that matters.

What goes wrong if missed: readers may stop before the useful part, or retain a vivid image while overlooking its limiting condition.

What this buys: attention and motivation directed toward the intended experience or work, with a way to repair distraction and overconfidence.

NSTD.5:2 - Problem

Narratives often work because they attract attention and organize memory. That value is real. But the same mechanisms can overpersuade, hide uncertainty, simplify conflict, or make a reader treat a narrative as evidence, assurance, or permission.

NSTD.5:3 - Forces

NSTD.5:4 - Solution

Try and compare the effect before adding more devices. The following optional note helps a team retain choices across revisions or audiences; a short passage can be improved without filling it.

NarrativeEngagementBoundary@Context:
  narrativeRenderingRef:
  intendedEngagementEffect:
  protectedSourceStructureRefs:
  languageStateFacetProfileRef?:
  coarseningOrPrecisionQuestion?:
  affectedReaderOrGroupRefs?:
  persuasionBoundary:
  nonAdmissibleUse:
  affectedPartyQuestion?:
  additionalClaimGrounds?:
  lowValueRepairAction:

Choose the device for the intended use. Preserve source relations when the account promises to explain them; preserve chosen premises when writing fiction. If a literary or simplified expression creates an action-changing ambiguity, repair that ambiguity directly. Use C.2.LS, A.6.3.CSC, E.17.EFP or E.10 only for the particular language, coarsening, explanation or precision question they address. Further evidence, assurance or ethics work depends on a consequential unresolved claim, not on engagement by itself.

Use this comparison to design engagement.

1. Name the intended engagement effect: attention, curiosity, emotional salience, identification, suspense, memorability, motivation, or willingness to continue.
2. Identify the relations, qualifications or choices the reader still needs to recover.
3. Try a device suited to the difficulty: for example an analogy for an abstract relation, an unresolved question for curiosity, or repetition for an easily lost distinction.
4. Compare what the device changes in order, salience, wording or repetition with the simpler passage.
5. Check the consequence for the needed relation: has an uncertainty become certainty, an analogy replaced a definition, or sympathy obscured a relevant alternative?
6. Keep, revise or remove the device. Use NSTD.6 for a qualified quality evaluation and NSTD.8 when learning is the aim. If the simpler passage already works and the added benefit is negligible, keep it.

Select any additional question from what readers will use the account to do.

Artistic language can serve atmosphere, felt experience and expression as well as instruction. For a memorial, preserving that experience may matter most; for a technical explanation, a missing condition may decide adequacy. Inspect language-state facets only when they help resolve the particular difficulty, rather than classifying every literary sentence.

NSTD.5:5 - Archetypal Grounding

NSTD.5:5.1 - Worked example: a failure story that teaches a usable distinction

A learning narrative about FPF uses a dramatic failure story: a team blindly follows a pattern checklist and damages its project. The story is engaging, but it may over-persuade if it implies that FPF prevents all such failures or that the named team is evidence. NSTD.5 keeps interest useful and bounded.

NarrativeEngagementBoundary@FPFFailureStory:
  narrativeRenderingRef: FPFLearningRoute@v1
  engagementDevice: failed-use contrast with tension and repair
  protectedSourceStructureRefs:
    - pattern conditions
    - forces
    - neighboring exits
    - evaluation and improvement route
  intendedEffect: keep attention and make misuse recognizable
  persuasionOrHarmRisk: reader treats story as proof of FPF superiority or as blame of a real group
  sourceFidelityRisk: checklist failure hides the actual source relation being taught
  precisionBackoff: identify the fictional example and point to the pattern's conditions of use
  evaluationReturn: `NSTD.6` checks reconstruction, not emotional agreement

Before:

This disaster proves why teams must use FPF.

After:

In this fictional case, the team’s checklist still assumed a stable workload after demand had changed. Before repeating the old action, compare its conditions with the present workload. The example illustrates that mismatch; whether FPF improves actual projects is a separate question.

NSTD.5:5.2 - Worked example: an engaging homotopy image with its limiting condition

A homotopy lesson uses the image of a loop “slipping around a hole”. The image is engaging and memorable, but it may cause learners to think all deformations are allowed. NSTD.5 protects the formal boundary:

NarrativeEngagementBoundary@HomotopyLoopImage:
  engagementDevice: vivid analogy
  protectedSourceStructureRefs: deformation under constraints, invariant, formal definition, proof-status boundary
  intendedEffect: sustain attention through abstraction
  persuasionOrHarmRisk: low, unless used to make a false certainty claim
  sourceFidelityRisk: analogy replaces condition-bound definition
  precisionBackoff: state where analogy stops and return to formal statement
  evaluationReturn: learner marks allowed and blocked deformation conditions

NSTD.5:5.3 - Engagement device selection matrix

NSTD.5:5.4 - Comparing engagement choices

Compare the intended effect and the content the reader needs. A more vivid version is worth keeping when it improves that use without concealing a consequential condition. If both versions work, their costs and expressive aims can decide. A comparison can be an expert walkthrough, a reader response or an observed result; state which basis supports the conclusion under NSTD.6.

NSTD.5:5.5 - Keeping the reader’s use in view

“Make it interesting” leaves an important question open: interesting for which reader and activity? A narrative can attract attention to a useful problem while preserving uncertainty and alternatives. The resulting motivation still needs to be distinguished from grounds for believing a factual claim.

In the fictional workload case above, a sufficient plain version is: “When demand changes, check whether the workload assumptions still hold before reusing the checklist.” The story adds a team caught in that mismatch. Compare the two versions for the same intended result: the reader identifies the changed assumption and the next comparison, without inferring that FPF guarantees success. An expert walkthrough can explain why the story makes the mismatch easier to notice; an actual attention or memory advantage remains a question for reader responses. Keep the story when that benefit or the intended expressive effect justifies its added length; otherwise keep the plain version.

A science-communication narrative may use tension around an unresolved experiment. Preserve the measurement, proposed explanation and unresolved alternative needed for the reader’s decision. If readers infer that a policy question has thereby been settled, repair that inference and address the separate policy question.

A homotopy lesson may use a memorable image of stretching loops. The image is admissible only if learners can still recover definition boundaries and source-return points. If the image helps memory but makes learners treat all deformations as equivalent without conditions, repair source selection and event or model support before adding more vivid imagery.

A franchise continuation may use suspense, stakes, and identification. Those devices are useful when they protect attention to causal plot and character agency. They fail when fan-service or shock replaces continuity, source constraints, or agency support.

Live commentary may use excitement to keep listeners oriented. The protected structures are observed event, provisional inference, score state, and uncertainty. Engagement fails when suspense turns prediction into fact or blame into settled responsibility.

The following examples show how a device can help or obstruct a particular use.

Preserve useful engagement. A dry explanation may lose readers before they reach its content; a vivid account may conceal a decisive condition. Compare the actual failure and repair it. Neither adding a dramatic device nor removing one is an improvement merely by itself.

Optional notes for maintained or collaborative work:

NarrativeEngagementBoundary@FPFLearningRoute:
  intendedEngagementEffect: motivation and memory for pattern-use reconstruction
  protectedSourceStructureRefs: EntityOfConcern; forces; solution; relations; source-return condition
  languageStateFacetProfileRef: plain teaching narrative with repeated anchors
  affectedReaderOrGroupRefs: new FPF authors and reviewers
  persuasionBoundary: may motivate study; may not prove FPF authority or tell readers to bypass checks
  nonAdmissibleUse: evidence of FPF correctness; replacement for pattern bodies
  lowValueRepairAction: add reconstruction task, source-return prompt, or lower motivational slogan

NarrativeEngagementBoundary@HomotopyAnalogy:
  intendedEngagementEffect: curiosity and retention for abstract structure
  protectedSourceStructureRefs: definitions; examples; proof-status boundary; formal return
  languageStateFacetProfileRef: analogy plus formal boundary markers
  persuasionBoundary: analogy may invite exploration, not replace proof
  nonAdmissibleUse: theorem proof, formal definition, or exam solution without source return
  lowValueRepairAction: add formal boundary, counterexample, or source-return step before more metaphor

NarrativeEngagementBoundary@FranchiseContinuationProbe:
  intendedEngagementEffect: suspense, identification, and stakes for private storycraft critique
  protectedSourceStructureRefs: canon constraint; continuity; character agency; causal plot support
  affectedReaderOrGroupRefs: private reviewers; no public audience permission implied
  persuasionBoundary: emotional satisfaction does not override source-pack or rights boundary
  nonAdmissibleUse: publication, canon authority, or rights claim
  lowValueRepairAction: repair continuity, agency, or causal support before increasing drama

NarrativeEngagementBoundary@LiveCommentary:
  intendedEngagementEffect: attention under unfolding uncertainty
  protectedSourceStructureRefs: observed event; provisional inference; score state; official return
  affectedReaderOrGroupRefs: listeners and any named parties if blame or harm framing appears
  persuasionBoundary: suspense and emotion do not settle blame, prediction, or official fact
  nonAdmissibleUse: final evidence, disciplinary judgment, or settled tactical analysis
  lowValueRepairAction: add uncertainty markers, source-return route, or lower blame wording

NSTD.5:6 - Bias-Annotation

This pattern blocks engagement-authority drift: attention, identification, suspense, memorability, or motivation is treated as truth support, ethics clearance, assurance, policy permission, or work authorization. Repair by naming protected source structures, persuasion boundary, affected readers when live, and direct owners for stronger claims. Scope: DPF-local for engagement in narrative renderings; it does not govern all persuasion or ethics work.

NSTD.5:7 - Conformance Checklist

NSTD.5:8 - Common Anti-Patterns and How to Avoid Them

NSTD.5:9 - Consequences

The method helps retain readers and make relevant relations memorable. Its cost is comparing the effect with what the reader needs; a small comparison can avoid both unnecessary ornament and unnecessary checking.

NSTD.5:10 - Rationale

Engagement design connects the intended reader effect with the content and choices that must remain available. This explains why a useful dramatic device in one account may be distracting or misleading in another.

NSTD.5:11 - SoTA-Echoing

Green and Brock’s transportation study (2000) connects immersion with story-consistent beliefs. Dahlstrom and Ho’s science-communication analysis (2012) examines purpose, accuracy and whether narrative is suitable. These are historical anchors. Mengelkamp, Golke and Appel’s reading-goal experiments (2025) found condition-dependent comprehension benefits, while overestimation remained across conditions. Georgiou et al.’s narrative-memory study (2025) distinguishes recall, recognition and summary. These findings motivate separate attention, recovery and confidence questions; they do not establish one universally superior engagement device.

Operational payload:

• Transportation research motivates checking whether confidence follows immersion rather than the grounds for a claim.
• Science-communication ethics makes the intended influence, required accuracy and choice of narrative explicit where they affect public reasoning.
• Reading-goal research supports making a learning aim clear while checking actual comprehension; stating a study goal does not guarantee accurate self-assessment.
• Memory research distinguishes retained gist from recalled detail. Select the aspect needed by the intended learning or later use.
• From FPF language-state and coarsening patterns, literary, compressed, or memorable wording is a change in representation, not an automatic quality increase.

The practical consequence is to evaluate the particular benefit sought and the content it may obscure, rather than use interestingness as a substitute for every quality question.

NSTD.5:12 - Relations

Uses A.6.3.NAR, NSTD.1, NSTD.3, NSTD.6, C.2.LS, A.6.3.CSC, E.17.EFP, E.10, A.6.P, C.16.Q, D.1 through D.5, A.10, B.3, E.17, and G.11. Reopen when reader telemetry, harm assessment, source fidelity, language-state profile, coarsening relation, precision repair, or persuasion boundary changes. Support-map entry: open Semiotic And Language-Precision Bridge when interesting, literary, artistic, memorable, hook, cue, coarsening, or explanation language becomes load-bearing; open NSTD.Reference:11 — Working meanings and direct source returns when engagement, adequacy, quality, value, or persuasion terms overload; open Source Use And Refresh Map when persuasion, memory, cognition, or ethics source claims carry the boundary.

NSTD.5:End

NSTD.6 - Declared-Use Narrative Rendering Quality Evaluation

Status: Stable

Type: DPF evaluation pattern body

Primary EntityOfConcern: NarrativeRenderingQualityEvaluationCharacteristicSpace@Context, an evaluation CharacteristicSpace for one evaluated narrative rendering kind and declared use.

NSTD.6:1 - Problem frame

Use this pattern when a team must decide whether one narrative rendering version, including an unaccepted candidate, is good enough for one declared reader or listener use. An editor may evaluate a directly authored or already existing product without knowing how its author produced it. State whether the present question concerns that product’s current quality, a promised source-to-result relation, or assurance about actual construction work; these questions need different evidence.

Evaluated object kind: NarrativeRenderingVersion@Context, an identifiable version of a narrative account in a form a reader can use. A seminar script, slide sequence or generated draft can express such an account. Select the narrative and its intended use within a larger source collection or teaching programme; evaluating that collection’s authority, the generation method or the whole programme is a different question. Missing source relations or poor quality are possible findings, not reasons to exclude a narrative candidate before evaluating it.

First useful move: identify the narrative version, reader and intended use, then select the relations and characteristics on which that use depends. Compare an adequate account with a deficient one. Distinguish those from a question about a different object, such as the generation method rather than its resulting narrative.

What goes wrong if missed: readability, elegance, engagement, expert approval, or generated fluency substitutes for epiplexity, source-return discipline, and bounded use.

What this buys: a repeatable evaluation that can feed E.23 improvement without confusing characteristics, measurements, eval programs, evidence, assurance, or gates.

Quality target: this pattern evaluates quality for one declared use under source-structure selection fit, NarrativeRenderingEpiplexity, ordering recoverability, temporal-posture and role fit, source-return readiness, bounded engagement, and owner-routed evidence, assurance, ethics, publication, and work claims.

NSTD.6:2 - Problem

Narrative rendering quality for declared use is not one property. A narrative can be fluent but structurally false, engaging but ethically unsafe, technically accurate but unusable for learners, or source-faithful but impossible to follow. A useful evaluation needs object-kind fit, characteristic slots, value meanings, evidence basis, missingness rules, floor, exceptional meaning, result-row shape, and repair actions.

NSTD.6:3 - Forces

NSTD.6:4 - Solution

Construct and use one narrative rendering quality evaluation characteristic space for one declared use. Reuse a sufficient current specification and result when their object, question and conditions still match.

For the structural-amount question, NarrativeRenderingEpiplexity specializes FPF C.2.8 U.ExtractableStructuralInformation: the structure this reader or observer can extract. Its three bearers are the receiving narrative episteme, the publication form expressing it, and the specified reader or observer. The selected source structure, correctness criterion, usable prior knowledge, operations, help, access and budget qualify this tuple. An unambiguous rendering reference can identify the account and expression. Use the existing epiplexity basis, scale and evidence fields below to retain the qualifications needed for the comparison; they do not create another bearer or record kind.

Begin with named additional and missing relations when a qualitative comparison answers the question. If a number is useful, count correctly recovered selected semantic relations at a declared grain, optionally as n/N for a fixed nonempty selected set. Each unit preserves participants, predicate, polarity, modality and action-changing conditions. Repeated words, headings or arrows do not add units. Retain which relations were recovered: equal counts can differ in suitability for the next use. A different ordinal or nonnegative structural weighting needs its own explicit structural meaning; a utility weighting is another score. A formal bit estimate needs the mapping in C.2.8, not merely the name epiplexity.

State whether the basis is a conditional design walkthrough, an actual reading or a mapped formal estimate. One response establishes the recovery observed in that trial and can ground an extractability estimate; it does not establish a maximum, impossibility after failure, or reliability across a reader class. An exact computational amount requires the corresponding method and model. Keep the first response, actual help and source returns. Familiar structure can be recovered from an expression; an expert’s independent correction of false or absent instruction earns that expression no credit. Recovery of what a source asserts and recovery of warranted subject structure use different correctness questions.

Compare forms with claims and relevant conditions held constant. Added or changed substantive claims can identify another episteme through C.2.1; changed access, preparation or help qualifies another comparison. A transfer or perturbation result belongs to its tested condition or robustness question and adds nothing to the original amount by itself. Compare effort and usefulness separately through C.11.CRC and C.11; keeping the sufficient rendering is an available result.

NarrativeRenderingQualityEvaluationCharacteristicSpace@Context:
  evaluatedObjectKindRef: NarrativeRenderingVersion@Context
  declaredUseScope:
  objectKindFitRule:
  discriminatingCaseSet:
  characteristicSlotSet:
  epiplexityBasisRule:
  scaleBindingSet:
  valueMeaningSet:
  evidenceBasisRule:
  missingnessAndLoweringRule:
  resultRowShape:
  floorAndExceptionalMeaning:
  protectedTradeoffSet:
  stopOrReopenCondition:
  neighboringGoverningPatternRefs:

Object-kind fit:

Default value meanings for the other ordinal content-quality characteristics follow. NarrativeRenderingEpiplexity uses its own structural scale above; the following 0–5 labels do not assign its amount, missingness or use threshold:

For reliance-bearing or teaching use, the default for structural recovery is that every relation declared necessary for that use must be recoverable under the specified support and evidence conditions. State those necessary relations at the grain the decision needs; a short account of the required distinction and stop can suffice. There is no generic structural-amount floor of 4. Keep the amount and satisfaction of the use condition separate: unrelated extra relations cannot compensate for a missing necessary relation.

The other load-bearing quality characteristics retain default floor 4 on their own scales, including OrderingRecoverability and SourceReturnReadiness. When the selected source structure is a constraint-governed unfolding structure, DemonstrativeSliceRecoverability is load-bearing and may not be below 4. A local low-risk orientation use may set those quality floors to 3 only if non-admissible downstream use is explicit. Neither numeral translates into a structural amount. A narrower use fixes its structure selection before evaluation; removing a difficult relation after observing the answer changes the basis rather than improving the original amount.

Result-row shape:

NarrativeRenderingQualityResultRow@Context:
  narrativeRenderingVersionRef:
  declaredUseScopeRef:
  characteristicId:
  characteristicName:
  scaleRef:
  value:
  evidenceBasisRefs:
  missingnessClass:
  loweringReason:
  repairAction:
  directOwnerRefs:
  reopenCondition:

Package the rows before feeding an improvement loop:

NarrativeRenderingQualityEvaluationResult@Context:
  evaluatedNarrativeRenderingVersionRef:
  declaredUseScopeRef:
  evaluationCharacteristicSpaceRef: NarrativeRenderingQualityEvaluationCharacteristicSpace@Context
  evaluationPurpose:
  evidenceBasisRefs:
  resultRows:
  protectedTradeoffSet:
  belowFloorRows:
  candidateImprovementProposalRows?:
  nonUseBoundary:
  stopOrReopenCondition:

When repeated improvement is wanted, open E.22 first if the quality question is not already framed. Then use E.23 with NSTD.6 as the object-under-improvement evaluation. This DPF does not mint a local loop kind.

NarrativeRenderingImprovementLoopInput@Context:
  e22QuestionFrameRef?:
  objectUnderImprovementRef: NarrativeRenderingVersion@Context
  objectVersionBeforeRef:
  objectUnderImprovementEvaluationRef: NSTD.6
  improvementAim:
  protectedTradeoffSet:
  costAndRiskAccount:
  allowedChangeSlice:
    narrativeRenderingVersion | NSTD.1-intake | NSTD.2-ordering |
    NSTD.3-event-model | NSTD.4-viewpoint | NSTD.5-engagement |
    NSTD.7-generation-and-inspection | NSTD.8-learning-route |
    evaluationCharacteristicSpace
  returnedFindingOrProposalRows:
  expectedReEvaluationResultForm: NarrativeRenderingQualityEvaluationResult@Context
  neighboringGoverningPatternRefs:
  stopContinueSwitchOrHoldCondition:

E.23 may claim improvement only after the changed object version is re-evaluated through NSTD.6 or through a declared stronger evaluation. If the loop changes the source pack, source-currentness, generated-carrier admission, learning publication carrier, publication face, ethics claim, evidence claim, assurance claim, or evaluation characteristic space, the loop must name the neighboring governing pattern and either keep it as the allowed change slice or open separate work. Style edits, prompt retries, or additional drama are admissible loop operations only when their expected movement under NSTD.6 is stated and protected trade-offs are checked. B.4 is relevant only when the narrative episteme or learning route is claimed to evolve across use and renewed operation; G.11 handles refresh when source currentness, reader telemetry, teaching-test evidence, generated-narrative practice, or FPF edition changes.

Before assigning values, recover the source and use basis for the question being answered.

For current-product evaluation, name the selected subject structures, intended reader work and necessary prerequisites, then trace what the present rendering preserves, hides or loses. Use the task and qualified subject sources to establish the needed structure; the rendering can help refine that basis but cannot excuse its own omissions. Recover its ordering rationale, source-return condition, and the event or mechanism, viewpoint, agency, engagement and learning-route relations that matter to this use through NSTD.1 through NSTD.5 and NSTD.8. Point to actual source and rendering passages. If this account is reconstructed now, identify it as an evaluation of the current product, with its uncertainties, not a record of what the author did. Missing manufacturing notes do not by themselves lower current-product values; missing subject basis, inaccessible return or unsupported relation still does.

For a promised transformation, compare the named source and result versions against the promised preservation or change. This can establish their present fidelity relation without establishing the actual sequence of manufacturing actions. For a claim about actual construction or repair, obtain records or other admissible evidence of those actions and distinguish them from a plausible reconstruction. Trace the applicable NSTD.1 selection, NSTD.2 ordering, NSTD.3 mechanism, NSTD.4 viewpoint, NSTD.5 engagement and NSTD.8 learning-route decisions. If their history cannot be established, leave that historical or assurance claim unsupported and return it to its owner. A good product does not supply the missing history.

A candidate can be evaluated before acceptance; the result can inform acceptance, repair or rejection. Additional requirements follow from the proposed use and claims. When generated or discovered content is intended to inform architecture work, C.35 supplies that assessment. Reuse as evidence follows A.10; assurance, publication authority and actual human learning-effect claims require their own grounds. None of those conclusions follows merely from a favourable narrative-quality result.

Use this evaluation sequence:

1. Object-kind fit: which narrative account and version is being assessed? Identify it in its text, slide sequence or other form. A question about the source collection, generator or whole teaching programme returns to the evaluation for that different object.
2. Evidence fit for the question: for current-product quality, recover selected source structures, ordering, source return and relevant relations from the subject/use basis and present rendering; for promised fidelity, compare the named source and result; for actual construction or repair, recover evidence of the claimed actions. Keep these conclusions distinct.
3. Declared-use fit: is the reader or listener use narrow enough to evaluate, and are non-admissible downstream uses stated?
4. Load-bearing characteristics: assign values only to the characteristics needed for the declared use, but include every characteristic whose failure would make the use unsafe or useless.
5. Low-value repair: for every value below floor, name the smallest repair route before proposing style, drama, or generation retries.
6. Re-evaluation route: if any repair changes the object version or selected source basis, plan a new NSTD.6 evaluation before claiming improvement.

Missingness and lowering rules:

A defined trial that recovers none of the selected relations supports observed recovery 0 on that scale, not impossible extraction. An empty denominator supports no fraction. Wrong-kind handling precedes amount assignment. A qualified design estimate can remain available without an actual trial; obtain a trial when its possible outcomes can change the receiving decision.

Default narrative rendering quality characteristics:

LearningRouteReconstructionFit is an additional characteristic for teaching uses. It uses the ordinal quality meanings above and the adjacent calibration below; it is not a structural-amount scale.

NSTD.6:5 - Archetypal Grounding

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.

NSTD.6:5.2 - An existing product and an unknown manufacturing history

An editor receives a handout narrative with a declared onboarding use, qualified subject basis and source-return links, but no manufacturing or repair journal. The editor reconstructs the needed source relations from the intended work and subject sources, follows their use through the present explanation and exercises, and tests a meaningful changed case. A missing return or a false relation is a current-product defect. No journal is needed to identify or repair it, and a strong present boundary test can support a high product value without inventing an earlier repair.

If the same editor is instead asked whether the handout faithfully transforms a named seminar, the seminar and handout must be compared. If asked whether the author performed a prescribed review or made a particular correction, evidence of that action is also needed. Current fidelity or a successful reader attempt cannot answer that historical question. A generated candidate receives the same current-product evaluation; its acceptance or production-history claims remain separate questions.

NSTD.6:5.3 - Before and after evaluation repair

Before evaluation statement:

The narrative is strong because readers liked it and remembered the main point.

Failure: engagement and memory are treated as total quality. Source recovery, relation strength, owner routing, and use boundary are absent.

After evaluation statement:

For the declared onboarding use, the illustrative recovery result is that learners can reconstruct the pattern-use route; a numerical amount needs a specified relation set, conditions and evidence. Source-return readiness receives value 3 because two slogans lack pattern-body refs, and engagement boundary receives value 4 because the failure story is marked as archetypal. The first repair is to add source-return refs for the slogans before changing style.

Now E.23 has a concrete changed slice: add two source-return refs and re-evaluate source-return readiness. Revisit the amount only if the changed access or explanation can change structural recovery. An earlier amount label is reusable only through its recoverable selection, scale, conditions and evidence; an unsupported 4 does not become 4/5.

NSTD.6:5.4 - Adjacent-value calibration

For structural-amount calibration, fix five relations in a narrative about reusing a review after a display change: reuse requires the same claims, the same question, and the same qualification window; an unavailable required argument stops the new check and returns it to the source; that stop preserves unrelated review results. This adapts C.37.CF’s content example. The condition, stop and source return form one compound unit at this declared grain. Hold the reader, case facts, material, operations, help and budget constant. The counts below illustrate nested constructed recovery sets, not three observed trials or a universal five-point rubric. Another selected set uses its own count or denominator without conversion to five labels.

The other characteristics use their own ordinal quality meanings:

NSTD.6:5.5 - Evaluation-to-improvement repair input without process theatre

NSTD.6 does not create a big improvement program. It creates result rows. A repeated improvement loop needs only:

NarrativeRenderingImprovementLoopInput@Context:
  objectVersionRef: narrative rendering version, including a candidate
  evaluationResultRefs: selected `NSTD.6` rows
  improvementAim: raise one declared value without lowering protected trade-offs
  allowedChangedSlice: wording, source-return link, ordering marker, viewpoint repair, engagement device, generated source plan, or learning task
  protectedTradeoffSet: source fidelity, owner routing, engagement, cost, reader burden
  expectedReEvaluationForm: rerun the affected `NSTD.6` rows and any neighbor owner checks

If the change is “regenerate until better”, the object version and changed slice are gone. If the change is “add a source-return link and an analogy-stop task”, E.23 can operate and NSTD.6 can re-evaluate.

NSTD.6:5.6 - FPF owner teaching

C.2.8 governs structural amount for architecture and non-architecture narratives alike. NSTD.6 applies it to the narrative and the selected observer/use conditions. C.33 retains the separate architecture-description adequacy question. Source-selection fit, source-return readiness, effort and usefulness remain separately judged; a story need not be an architecture description for its structural amount to be compared.

Pass case: an FPF seminar handout narrates how a practitioner moves from problem frame to forces to solution and checks. It names FPF pattern source sections, ordering rule, learner reconstruction task, and source-return points. Its necessary source relations are recoverable under the declared support; the other selected quality characteristics can reach 4 or 5 on their own scales. The handout is not evidence that FPF is correct, and those quality labels do not assign its structural amount.

Fail despite fluency: a polished architecture story says one chosen architecture “won” because it felt coherent, hides rejected candidates, omits architectural characteristics, and gives no source-return path. The needed architecture relations are missing, so the structural-use condition fails; assign an amount only when its selection and conditions are established. OrderingRecoverability and SourceReturnReadiness can fall below their own floors even if engagement is high.

Different object: an evaluator is asked whether a text generator is reliable across unseen topics. One narrative’s NSTD.6 result does not answer that question; the generator and its proposed operating range need their own evaluation. By contrast, a fluent generated story with an unknown source is still a narrative candidate: visible defects can be diagnosed, while source fidelity and structural amount remain unassigned where their required basis is unavailable.

NSTD.6:6 - Bias-Annotation

This pattern blocks proxy-as-quality drift: readability, fluency, liking, engagement, expert approval, or generated-text benchmark value replaces object-kind fit and declared-use rendering quality. It also blocks the opposite drift where a test program is treated as the characteristic itself. Repair by selecting the evaluated object kind, scales, value meanings, evidence basis, missingness and lowering rules, floor, result rows, and repair actions. Scope: DPF-local for evaluating narrative rendering versions; it does not govern evidence, assurance, gate, decision, or publication authority.

NSTD.6:7 - Conformance Checklist

NSTD.6:8 - Common Anti-Patterns and How to Avoid Them

NSTD.6:9 - Consequences

The benefit is a usable improvement target: E.23 can improve narrative versions because values, floors, evidence, and repairs are declared. The cost is heavier evaluation before reliance-bearing use.

NSTD.6:10 - Rationale

A.19.ECS says improvement cannot be better than its evaluation. NSTD.6 specializes that lesson for narrative renderings: first recover object kind and use, then choose characteristics that discriminate narrative rendering quality for that declared use.

NSTD.6:11 - SoTA-Echoing

FPF A.19.ECS and C.16 supply the evaluation and measurement distinctions. C.2.8 supplies reader-relative structural amount and its qualified formal epiplexity specialization; C.33 concerns architecture-description adequacy. Amount, extraction effort, learning and task usefulness can change independently. Language-state, coarsening and explanation patterns support the particular repairs named in the scale; they are not extra tests triggered by every stylistic change.

Castricato et al.’s model-theoretic account distinguishes narrator-to-reader information and evolving story models. Mengelkamp et al.’s reading-goal experiments found condition-dependent comprehension effects and persistent overestimation. Georgiou et al.’s narrative-memory study separates recall, recognition and reconstruction of order. These results support asking what a reader actually recovered, separately from fluency, confidence or enjoyment; they do not validate the DPF’s ordinal scale.

The competing shortcut is to rate a narrative by fluency or engagement alone. A fluent account that turns temporal precedence into cause demonstrates why that shortcut fails for a causal explanation. This pattern therefore evaluates the selected relations and the intended use separately from engagement, accepting the cost of a focused source comparison or reader task when it can change the judgement. For an expressive use without that causal claim, do not invent the same obligation.

Ma et al.’s story-generation survey identifies continuing coherence, consistency, diversity, control and evaluation problems. Rahman et al.’s G-KMS adds structured, semantic and engine-execution checks for its RPG setting. Select these checks for the claim being assessed: an observable continuity defect can be judged from the product, while a claim about reader experience needs an appropriate reader basis. Neither source makes a human study a prerequisite for inspecting an ordinary draft.

NSTD.6:12 - Relations

Uses A.19.ECS, A.17, A.18, C.2.8, C.16, C.16.Q, C.2.LS, A.16.1, A.16.2, A.6.3.CSC, E.17.EFP, E.10, A.6.P, C.33, E.22, E.23, B.4, A.10, B.3, E.17, C.35, and G.11. C.2.8 defines structural amount for all admitted source domains; C.33 is used when architecture-description adequacy is current. E.23 consumes NSTD.6 result rows only after object version, allowed change slice, protected trade-offs, cost and risk, and re-evaluation form are explicit. B.4 is used only for an evolution claim over a narrative episteme, learning route, or other holon under repeated use; G.11 handles currentness and refresh. Reopen when evaluated object kind, declared use, source pack, characteristic set, language-state profile, cue or backoff status, coarsening or explanation relation, precision-restoration result, epiplexity basis, value meanings, floor, evidence basis, allowed improvement slice, or low-value repair route changes. Support-map entry: open Architecture and Narrative Work Bridge when NarrativeRenderingEpiplexity is architecture-relevant or tied to C.33; open Semiotic And Language-Precision Bridge for language-state, coarsening, explanation, relation, or quality-word repairs; open Source Use And Refresh Map when evidence basis or source-currentness supports a value; open NSTD.Reference:11 — Working meanings and direct source returns when a characteristic name risks becoming a new ontology.

NSTD.6:End

NSTD.7 - Automated Narrativization and Story Planning

Status: Stable

Type: DPF pattern body

Primary EntityOfConcern: planning, generating and inspecting a narrative produced with a tool, so that its content and form serve the intended use.

NSTD.7:1 - Problem frame

Use this pattern when LLM, NLG, graph-to-text, data-to-text, story-planning, schema-governed generation, or search is used to produce or repair narrative renderings.

First useful move: give the generator the material, the relations it should preserve and the intended reader’s task. Obtain a small draft and compare it with the material for omissions, inventions and misleading connections. Evaluate those defects before deciding how to use the draft.

What goes wrong if missed: fluent wording or a valid output schema hides an unsupported cause, missing condition or continuity error.

What this buys: useful automated drafting with a way to detect and repair the losses that matter to the reader.

NSTD.7:2 - Problem

Automated systems can produce fluent narratives that lose a source relation or violate a story constraint. A plan helps control generation, while inspection tests the actual result. Either can reveal a need to revise the other.

NSTD.7:3 - Forces

NSTD.7:4 - Solution

Work from a content plan to an inspected draft. For a short account, the plan can be a few instructions or marked source relations. Inspect a candidate before accepting, repairing or rejecting it; prior acceptance is not required to evaluate it. Use the optional note below when another worker, an experiment or a maintained workflow needs to recover those choices. Keep only the fields that serve that use.

GeneratedNarrativeUseNote@Context:
  sourceMaterialRef:
  generatedDraftRef:
  intendedReaderAndUse:
  requiredRelationsOrConstraints:
  generationMethodRef?:
  contentPlanRef?:
  discourseOrEventPlanRef?:
  schemaConstraintRefs?:
  sourceComparison:
  evaluationRef?:
  useDecisionOrRepair:
  consequentialUseDecisionMaker?:
  architectureSynthesisAssessmentRef?:
  additionalClaimGrounds?:
  revisitCondition?:

Choose additional checks from the claim being made:

The following operations describe a useful generation cycle. They can be interleaved: an inspected draft may reveal a better content selection or order. A short task can combine planning in one prompt and comparison in one reading. Separate stages or records are useful only when the task, tool or receiving use needs them.

For schema-governed generation, distinguish a format check from a content check. A schema can require scene fields, character roles, locations, source references, branches or game-engine inputs. Check whether those fields contain the right relations and satisfy the intended constraints. Record the constraints when later maintenance needs them; use NSTD.6 for narrative quality and C.34 when architecture-specific structural preservation is at issue. Neither a valid schema nor a complete note establishes factual accuracy.

For LLM-assisted analysis or theme generation, compare proposed themes with the source excerpts and serious alternative readings. The researcher decides which interpretation the report supports and explains its limitations. A generated plan can become input to later narrative work once its relevant claims or premises are suitable for that use; a named admission record is not a universal prerequisite.

Select a probe when its possible result can change the generation method, repair or intended use:

1. Source perturbation: change one relevant constraint and compare the next output. A failure to reflect the change exposes a grounding problem. A successful probe supports that tested relation; it does not prove fidelity for every output.
2. Structure recovery: ask a reader to reconstruct the relations needed for the task without seeing the prompt. Retain the first answer and actual assistance. A missing relation may require content or order repair.
3. Responsibility: for a consequential organizational use, establish who decides and can correct or withdraw it. A tool-generated assertion of permission supplies no such assignment.

NSTD.7:5 - Archetypal Grounding

NSTD.7:5.1 - Generated-narrative pipeline: graph-to-text case

An AI agent receives a concept graph and produces a polished explanation. The author compares the needed dependency and example relations with the draft, evaluates consequential losses and repairs the account. The optional record below supports repetition of that comparison.

GeneratedNarrativeUseNote@GraphToTextTeaching:
  sourceMaterialRef: concept graph with dependency, example, counterexample and evidence links
  requiredRelationsOrConstraints: prerequisite chain, contrast pairs, evidence-return points
  generationMethodRef: LLM-assisted graph-to-text workflow
  contentPlanRef: selected nodes and relations
  discourseOrEventPlanRef: didactic dependency order with a contrast reveal
  generatedDraftRef: prose candidate
  sourceComparison: required relations compared with their sentences
  evaluationRef: relevant NSTD.6 questions and results
  useDecisionOrRepair: repair any missing prerequisite before the learner uses that inference
  revisitCondition: source graph, generator behavior or reader result changes

Pipeline steps:

1. Select the nodes, relations and returns the learner needs.
2. Choose an order through NSTD.2, then generate a short draft.
3. Compare the draft with the graph. If it says “B occurs because A” but the graph supports only “A precedes B”, replace the causal claim or obtain the missing causal account.
4. Use NSTD.6 to assess the repaired version for the intended reading. The draft need not have been accepted before this assessment.
5. Keep the adequate result. For repeated improvement, use E.23 with the version, changed part, protected characteristics and comparison basis.

NSTD.7:5.2 - Probe suite for generated narrative

NSTD.7:5.3 - Before and after repair: generated seminar outline

Before:

The generated outline sounds coherent and covers all important ideas, so it can be used as a DPF learning route.

Failure: neither the needed source relations nor the learner’s task is identified. “Covers all important ideas” has no comparison basis.

After:

The outline selects EntityOfConcern, forces, solution, neighboring-pattern exits and the improvement loop, ordered by their teaching prerequisites. Compare those relations with the source and try the intended reconstruction task through NSTD.8 and NSTD.6. A worked design estimate can support a provisional lesson; a claim about what learners actually recover requires a reading or teaching trial. C.35 becomes relevant only if the generated result is being used to inform architecture work.

NSTD.7:5.4 - Generated-storycraft boundary

For a franchise continuation, compare the generated scene with the selected continuity, premise and character-motivation constraints. A surprising event is acceptable when those relations support it; if it relies on a contradiction, repair the event or change the stated premise. Source perturbation can test a recurring generator problem. A private critique and a publication have different permissions questions. NSTD.6 can evaluate the candidate before either use is accepted.

NSTD.7:5.5 - Calibration for generated narrative

NSTD.7:5.6 - FPF owner teaching

NSTD.7 connects content planning, realization and evaluation. A generated account has claims expressed through a publication form; its fluency alone does not establish those claims. Use C.2.8 for reader recovery, A.10 for evidence claims and B.3 for assurance claims when they arise. C.35 is restricted to generated or discovered results intended to inform architecture work. Source changes and changed generator behavior can reopen an earlier comparison.

An LLM drafts an explanation of FPF pattern use from notes. Compare its selected relations, order and returns with those notes and the applicable pattern content. NSTD.6 can assess the candidate immediately; if the necessary subject basis is missing, it leaves that amount unassigned while retaining independently supported defect findings. An absent generation journal does not erase visible product qualities or defects.

A graph-to-text system turns an event graph into a match recap. The event graph, source timestamp, uncertainty markers, and official-result refresh route are admitted source basis for this rendering. The generated recap is a carrier. If the system adds causal explanations not in the graph, those claims are not admitted by graph-to-text success. Repair by lowering causal language, adding source return, or opening the evidence owner.

A game story-planning pipeline generates a branching scene. The schema may require objective, location, actors, traits, constraints, and available actions. NSTD.7 treats those fields as method and source-plan support, not as proof of playable, coherent, or ethically acceptable narrative. Structural, semantic, executable, and human probes remain separate from fluency.

An LLM proposes themes from interview notes for qualitative narrative analysis. The generated theme list is not the researcher’s interpretation by default. Human interpretive agency remains live: the researcher checks source excerpts, reflexive stance, alternative readings, and admissible use before any narrative rendering or report uses the generated material.

Use these examples to distinguish evaluation from acceptance:

When automated repair is used, preserve version identity. “Regenerate until better” destroys improvement evidence. Record the previous carrier, changed prompt or method, selected changed slice, expected value movement, protected trade-offs, and re-evaluation route. A generated variant can be more fluent and still worse on epiplexity, source return, or agency discipline.

Pipeline variants by source type:

If a pipeline variant requires a source type not covered by the current source pack, mark the case as a source-refresh trigger rather than silently generalizing. A graph-to-text claim, for example, may require a more specific graph-to-text source than a general NLG survey. A game narrative pipeline may need executable or playability probes that a plain text-generation source does not supply.

NSTD.7:6 - Bias-Annotation

Fluency can conceal a missing condition or invented cause. Inspect the relation that matters to the reader, rather than inferring source fidelity from style. The opposite error is to require a complete production dossier before evaluating an observable defect. Select additional checks from the claim and consequence, and keep candidate evaluation available throughout drafting.

NSTD.7:7 - Conformance Checklist

NSTD.7:8 - Common Anti-Patterns and How to Avoid Them

NSTD.7:9 - Consequences

The benefit is automated drafting with a tractable source comparison and repair cycle. Its cost depends on the relations and consequences being checked; a small adequate account can be retained without a separate dossier.

NSTD.7:10 - Rationale

Planning makes selected content and order available for control; inspecting the resulting narrative checks whether that control succeeded. Evaluation therefore belongs inside the generation cycle and can support a later acceptance decision.

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.

NSTD.7:12 - Relations

Uses G.2, C.35, A.6.3.NAR, C.2.8 for structural amount, C.33 for architecture-description adequacy, C.34, NSTD.6, A.19.ECS, C.16, E.22, E.23, A.10, B.3, D.1 through D.5, and G.11. E.22/E.23 use the evaluated version, changed part and relevant NSTD.6 results; a retry is an improvement only when comparison supports that conclusion. C.35 applies when the result informs architecture work; C.34 to architecture-specific preservation; G.2 to SoTA harvesting and synthesis across traditions. Reopen when the selected material, generator, method, schema, intended use, evaluation result or relevant research changes. Support-map entry: open Source Use And Refresh Map when generation, NLG, story-planning, schema, or source-pack claims are relied on; open NSTD.Reference:11 — Working meanings and direct source returns when generated source plan, plot plan, schema constraint, admission, correspondence, or responsibility words blur object kinds; open Semiotic And Language-Precision Bridge when prompt output changes language state, coarsening, cue, or quality wording.

NSTD.7:End

NSTD.8 - Design a Narrative Learning Route for Reconstruction and Use

Status: Stable

Type: DPF pattern body

Primary EntityOfConcern: designing and repairing a narrative learning route so learners can reconstruct and use the relevant source relations.

NSTD.8:1 - Problem frame

Use this pattern when a complex source structure must be taught, explained, or learned through a narrative route, and the route must preserve enough structure for learners to reconstruct and apply it later. The governed object is the instructional route and its relation to source structure, not every explanation or reference publication. A publication used only for lookup or a professional decision need not become a course.

First useful move: begin at one consequential transition. Recover the current question, what the learner has already met, the contribution now needed and the support actually available there. Try the next task with that support, then repair the missing connection or choose the next useful teaching move.

Architecture warning: the source corpus may have a good reference architecture and still make a bad learning route if copied directly into the course. Engineers often make a blocked topic route: one coherent module after another, with each topic concentrated in its own lesson. That can be excellent for a reference manual, API, or architecture description, but weak for learning when learners must discriminate neighboring cases, retrieve earlier distinctions, and transfer the structure under varied cues.

What goes wrong if missed: the explanation is engaging and memorable, but learners retain examples, slogans, analogies, and mood while losing architecture, relation records, proof obligations, pattern-use routes, source-return conditions, or improvement cycles.

What this buys: a route that helps learners use the source ideas, with the needed material available when the next task requires it.

NSTD.8:2 - Problem

A learning narrative uses sequence, examples, repetition, analogy and motivation to help the learner reconstruct and use source ideas. Those choices can also conceal a prerequisite or make an illustrative route appear to be the only way to perform a method. This pattern describes how to design and repair the route. Worked examples belong in a pattern when they explain its method; a complete course script is a separate teaching product.

A common engineering failure is the reference-manual course. The course follows the module architecture of the source: first all of topic A, then all of topic B, then all of topic C, each with concentrated examples. Learners can follow each block locally, but later fail to choose the right pattern, distinguish nearby structures, remember earlier conditions, or transfer across domains. The repair is not to destroy the source architecture. Keep the source architecture as source return, then design a different learning-route architecture with deliberate interleaving, spaced retrieval, recurring anchors, and transfer tasks.

NSTD.8:3 - Forces

NSTD.8:4 - Solution

Design the needed transition and its continuation. The optional route note below helps when a team maintains a course, compares versions or coordinates several teaching materials. Keep the fields that those uses need; a short explanation does not require a full course record.

LearningNarrativeRoute@Context:
  learnerUse:
  sourceStructureSpineRefs:
  unfoldingStructureRefs?:
  demonstrativeSliceRefs?:
  sourceArchitectureRef?:
  learningRouteArchitectureRule:
  learningStepOrderingRule:
  interleavingPlanRefs?:
  spacingOrRetrievalScheduleRefs?:
  recurringAnchorRefs?:
  sourceReturnLinkRefs:
  learnerReconstructionTaskRefs:
  applicationTaskRefs?:
  engagementBoundaryRef?:
  narrativeRenderingQualityEvaluationRef:
  improvementLoopInputRef?:
  learningPublicationCarrierRefs:
  blockedTopicOverread?:
  nonAdmissibleUse:
  refreshCondition:

A maintained course may have separate lessons, slides, exercises and recordings. Link them to the source ideas and learner tasks they serve. The size and publication form depend on the teaching work.

When teaching a constraint-governed unfolding structure, make the wider possibilities recoverable alongside the demonstrated path. Teach an omitted alternative or stop condition at the point where it changes the learner’s action. A route note can link the wider structure and the taught slice when that helps maintenance.

The following design questions connect the route’s components. They can be addressed together and revisited after an attempted task; each need not become a separate pass or work product.

Do not optimize the learning-route architecture for local neatness. A locally neat blocked route can be globally weak: it gives learners the answer key for the current block, so they do not practice selecting the right owner under mixed cues. Interleaving is useful when the learner must later discriminate similar patterns, methods, proof obligations, architecture structures, or source-return owners. Spacing is useful when the learner must still retrieve a structure after other material has intervened. Use them as design moves with declared learner use, not as decorative variety.

NSTD.8:4.1 - Check attachment and support at the next use

Inspect the relation between a block or learning aid and both its surrounding context and its later use. What question is active, what distinction or action does this example, image, explanation or exercise enable, why is it needed here, and where will its result be used? A question, worked example, caption, short transition or later payoff can carry that relation. There is no compulsory five-field form and no quota of connective phrases. A repeated word is not enough when the reader still cannot connect the two uses.

Then inspect the route prefix: the material encountered up to the point where a new reconstruction or action is required. Identify the relevant distinctions already introduced, necessary prerequisites expected of this audience, newly introduced objects or relations, still-open questions and the means available now. Ask the reader to use those means on the next task. A relation shown only much later cannot support the current action unless a usable return makes it available. An overview is useful when it exposes the needed relation, not merely because it lists topics.

Keep three different repair questions separate:

• A missing attachment: restore the relation between the active question, the block or aid and its next use; correct a wrong return or an unexplained visual edge.
• An unsupported new demand: supply the necessary contrast, map, worked operation, recap, accessible representation or introduction order before relying on that operation. Check the promised prerequisite and assistance first; do not simplify away needed subject structure.
• A deliberate preparatory attempt: let the learner try a bounded problem before the explanation when that serves the learning design, preserve the attempted alternatives, and use subsequent instruction to compare and resolve them. Difficulty or an incorrect first attempt is not by itself a material defect, but unresolved failure is not evidence of productive preparation.

Use a stable supported initial case when the learner needs it to build the distinction before mixed selection. Interleaving, spacing and retrieval serve the declared later task; they do not require every first encounter to mix unfamiliar alternatives. Conversely, making every block easy by naming its answer does not test later independent selection. Judge the actual point and contribution rather than choosing one universal order.

Preserve the first response before a cue supplies the distinction being tested. Report the allowed help, help actually used, source contribution and the reader’s prior expertise. A teacher-supported correction may fulfil the declared arrangement while leaving independent first recognition untested. An expert’s successful reconstruction does not erase a contrary report from a less-prepared reader. Use an appropriately scoped observation if that reader’s difficulty can change the repair.

Structural reconstruction demand is not experienced cognitive load. NSTD.6 applies C.2.8 as NarrativeRenderingEpiplexity to the narrative account, expression and observer under the selected reading conditions; it is neither a quantity to maximize unconditionally nor a burden meter. A material inspection or agent walkthrough can locate a missing relation and available support, but claims about human burden, learning, retention or transfer need their own observations and conditions. For reported burden, identify the person, segment, timing and instrument.

Recheck the changed attachment, the affected prefix and its next task while preserving unaffected source and route results. If the intended reader already recovers the relation and completes that task with the declared support, density alone is not a reason to insert another aid. Use E.23 for a worthwhile repair; shortening, added pictures or extra repetition are not improvements without a changed useful result and protected qualities.

Use reconstruction tasks at several depths.

Examples, stories, rhythm, repetition and analogy can all support learning. Keep a device when it helps the intended task. If a learner retains the device but misses a necessary relation, repair that connection rather than automatically adding or removing examples.

For a small route, a short learner attempt or observed confusion may answer the current repair question. A repeated course may need to retain the version, audience, task, assistance and result so later comparisons remain interpretable. Collect more only when the result can change the design or intended use. A local teaching revision is not by itself a claim about evolution under B.4.

If the route is improved across runs, first evaluate the concrete route version through NSTD.6. Use E.22 when learner value, floor, protected trade-offs, evidence, or result form are still underframed; use E.23 to repair a declared changed slice such as source spine, learning-step order, reconstruction tasks, learning publication carrier, engagement boundary, or evaluation characteristic space. Use G.11 when source currentness, learner telemetry, teaching-test evidence, generated practice, or FPF edition changes; use B.4 only when making an evolution claim about the learning route as a holon across repeated operation.

NSTD.8:5 - Archetypal Grounding

NSTD.8:5.1 - Worked learning route: FPF onboarding

This example sketches the route that a seminar, tutorial or exercise sequence could realize. The note is optional; the important relation is between each teaching move and the next learner action.

LearningNarrativeRoute@FPFOnboarding:
  learnerUse: new practitioner can apply one FPF pattern without treating it as a recipe
  sourceArchitectureRef: FPF pattern language and monolith and source pattern organization
  sourceSpineRefs:
    - `EntityOfConcern`
    - problem frame
    - forces
    - solution as condition-bound move
    - conformance and checking
    - neighboring exits
    - quality and improvement loop
  unfoldingStructureRefs: A.22.CGUS when the route teaches unfolding from source to next use
  demonstrativeSliceRefs: first pattern-use route through one selected project case
  learningRouteArchitectureRule: interleaved pattern-use route, not monolith-reference order
  learningStepOrder:
    - failed ordinary use
    - recover object of concern
    - read forces
    - choose solution move
    - check boundary and neighboring owner
    - repair one low-value result
  interleavingPlanRefs:
    - return to `EntityOfConcern` after forces, solution, and quality checks
    - mix adjacent owner-choice cases after each new pattern
    - revisit source-return boundary in examples from at least two domains
  spacingOrRetrievalScheduleRefs:
    - short delayed retrieval at the start of the next session
    - later mixed owner-choice task after intervening material
    - final transfer task with no block label
  reconstructionTasks:
    - name the source pattern section behind each story beat
    - choose the governing pattern for a new case
    - state one source-return condition
  engagementBoundaryRef: failure story is an archetype, not evidence
  evaluationRouteRef: `NSTD.6` learning-route rows
  improvementLoopInputRef: `E.23` when a comparison identifies a worthwhile improvement

In this onboarding route, the opening failed use may be preparation rather than a failed capability assessment. The subsequent recovery of the object of concern must work with the attempted alternatives: show which object the next move governs and why the tempting alternative does not answer that question. Before the later neighbor-choice task, inspect whether those neighboring entries and their distinguishing condition are already available. If not, introduce the contrast or provide an accessible source return; merely adding another unlabeled failure would not supply it. If the entries are available, the mixed case can test their selection instead of prompting the answer.

A concrete task in an introduction to FPF-based pattern use can use two neighboring NSTD methods already available in this publication. First make the distinction available: NSTD.2 changes presentation order while preserving needed relations; NSTD.3 examines the connection the account asserts. Then give the Readme’s incident log, whose causal investigation is still open, and its draft “the change caused the failure”. Ask: “Would moving the two logged events into chronological order settle this sentence? Which question must the repair answer?”

A supplied response in this design example is: “Put the change before the failure, so the cause is clear.” That response preserves chronology but still infers cause from order. If the distinction was unavailable, provide it and work through the two claims before another selection task. If this was a deliberate preparatory attempt, subsequent instruction should use that attempted answer to explain why chronology leaves the causal question open. If both entries were already available, return to the sentence and ask what the log establishes; then use a mixed case to check whether the learner selects a connection repair rather than an ordering repair. These continuations answer different difficulties.

A later diagram or recap should connect that choice to the next use. A wrong figure return calls for correcting the attachment, not automatically redesigning the entire course. After the repair, ask the reader to recover that relation and use it under the declared support. This is a worked design example with a supplied response, not an observation of a learner or a demonstrated learning gain.

A seminar file can add timing, facilitation notes and complete exercises. This pattern keeps the examples needed to explain route design without prescribing a complete seminar.

NSTD.8:5.2 - Worked learning route: repair topic-blocked practice

An engineering team wants a course on architecture patterns. Their first outline looks clean:

Lesson 1: all source-structure intake.
Lesson 2: all ordering rules.
Lesson 3: all viewpoint and agency.
Lesson 4: all engagement.
Lesson 5: all evaluation.

This outline gives learners the problem type inside each block. It may support first practice but leave later independent selection unpractised: a new failure may concern source selection, ordering, viewpoint, engagement, generation or the grounds for a claim.

Repair the route:

LearningNarrativeRoute@ArchitecturePatternCourse:
  learnerUse: engineer chooses and repairs the right pattern under mixed project situations
  sourceArchitectureRef: topic map and source pattern bodies
  sourceSpineRefs:
    - selected source structure
    - ordering rule
    - viewpoint and agency split
    - engagement boundary
    - narrative rendering quality row
    - source-return and owner routing
  learningRouteArchitectureRule: spaced interleaving around recurring project cases
  learningStepOrder:
    - one motivating project failure
    - source-selection repair
    - different project failure requiring ordering repair
    - return to first failure and add viewpoint risk
    - mixed owner-choice exercise
    - delayed retrieval of source-return boundaries
    - final transfer to an unseen case
  interleavingPlanRefs:
    - every session mixes at least one current pattern with one earlier pattern
    - adjacent failure modes are compared side by side
    - examples rotate across FPF seminar, architecture explanation, homotopy explanation, generated carrier, and live commentary
  spacingOrRetrievalScheduleRefs:
    - start each session with a no-label retrieval task from a prior session
    - return to `EntityOfConcern`, source-return, and owner-routing at increasing delays
    - require one late repair of an old low-value row after new material intervenes
  blockedTopicOverread: a clean topic block is not evidence of durable pattern choice
  evaluationRouteRef: `NSTD.6` rows for transfer, source return, and learner reconstruction

The repaired route still preserves the source architecture. It simply refuses to treat that architecture as the course order. The learner sees a pattern, uses it, leaves it, then returns under a different cue. That is the point: source modules can stay modular while the learning route deliberately crosses module boundaries.

NSTD.8:5.3 - Worked learning route: homotopy explanation

LearningNarrativeRoute@HomotopyIntro:
  learnerUse: learner distinguishes intuitive deformation picture from formal definition and proof boundary
  sourceSpineRefs:
    - topological space
    - path
    - homotopy relation under constraints
    - invariant
    - example and counterexample
    - proof-status return
  learningStepOrder:
    - image cue
    - constraint marker
    - formal definition return
    - example
    - counterexample
    - reconstruction task
  reconstructionTasks:
    - mark where analogy stops
    - state which deformations are not allowed
    - return one claim to formal source
  engagementBoundaryRef: vivid image cannot replace definition
  evaluationRouteRef: `NSTD.6` rows for ordering, language-state precision, and source return

If learners can retell the loop picture but cannot state the required constraint, repair the connection to the definition. A suitable example, counterexample or worked comparison may supply that repair.

NSTD.8:5.4 - Worked learning route: using this pattern language

A short course on this DPF may use the three probes: FPF seminar, franchise continuation, and homotopy explanation, with live commentary as a fourth transfer case. The route succeeds only if learners can see the same pattern set working across different domains:

The transfer question is the actual teaching test. Remembering case names is not learning. The learner must choose the live pattern and repair the failure in a new situation.

NSTD.8:5.5 - Before and after repair: teaching material inside pattern body

Before:

This pattern should include a full seminar script so readers can immediately teach narrativization.

Failure: a complete seminar script can obscure the reusable route method and its alternatives. A worked example that explains a particular operation remains useful inside the pattern.

After:

This pattern explains how to design the learning route, with worked examples of its operations. A complete seminar script, slide deck and session notes are separate teaching products. Their learner tasks and source returns can be evaluated through NSTD.6.

NSTD.8:5.6 - Evaluating the learning route

Select the outcome needed for the declared teaching use. Immediate reconstruction, delayed retrieval, discrimination among similar cases and transfer to a new case require different tasks and observations. Success at one does not establish the others. A one-off explanation may need only immediate reconstruction; a course promising durable independent use needs an appropriately delayed and varied task.

Use NSTD.6 with the observer, prior preparation, assistance and reading conditions stated. Keep an author’s walkthrough distinct from an observed learner result.

NSTD.8:5.7 - Connecting route design to publication and improvement

NSTD.8 uses E.11 for framework entry, E.17 for publication form, E.17.AUD for a separately usable audience unit, NSTD.5 for engagement and NSTD.6 for evaluation. E.22/E.23 support a selected improvement; G.11 addresses an applicable source or practice refresh. A one-off explanation and a maintained course need different amounts of recorded design.

An FPF learning route, such as a seminar series or tutorial sequence, teaches the framework across several steps. The source-structure spine includes EntityOfConcern discipline, relation precision, pattern bodies, DPF authoring, architecture synthesis, evaluation, improvement loops, and source-return discipline. The learning order is didactic, not proof of FPF architecture. Learner tasks ask participants to reconstruct one pattern-use route from source basis and selected source structure, not only repeat a story or slogan.

A homotopy mini-course may start with pictures and deformation stories. Its reconstruction task should reveal whether the learner can recover the required definitions and conditions. When an analogy conceals a constraint, a counterexample or comparison can show why the formal boundary matters.

A DPF onboarding route may teach narrative rendering through three cases: FPF seminar, franchise storycraft, and live commentary. The route is successful only if learners can reconstruct why all three open NSTD.1, why different patterns become live later, and why NSTD.6 evaluates a declared rendering version rather than a general story. The test is transfer across cases, not recall of the case names.

Use NSTD.7 to inspect a generated teaching draft against the source ideas and intended tasks. NSTD.6 can evaluate it before acceptance. Apply C.35 only when the generated result is being used for architecture work; producing a slide or example does not itself select that pattern.

Distinguish versions when comparing repeated teaching or maintaining materials. The following optional note is useful when the comparison needs these details.

LearningNarrativeRouteVersion@Context:
  routeRef:
  sourceSpineVersionRef:
  learnerRoleRef:
  learningStepOrderingRule:
  carrierRefs:
  reconstructionTaskRefs:
  evaluationResultRef:
  observedConfusionOrTelemetryRefs?:
  changedSliceSincePreviousVersion?:
  refreshCondition:

For a comparison, identify which material and order each group encountered and what changed. Re-evaluate the affected outcome before claiming improvement. An untracked slide change may still be useful, but cannot support a precise comparison of course versions. A relevant source change calls for reviewing the affected teaching content.

The following example plan connects subject content, the immediate teaching move and a later use. Adapt its timing and returns to the learner’s task.

The left column names the source ideas to recover; the middle names an immediate teaching move; the right shows a possible later return. Use the last column when delayed retrieval or mixed selection is part of the goal. Its presence alone does not establish learning, and its absence is not a defect in a route that does not need those outcomes.

Examples of different learning aims:

For a short one-off teaching note, the route can be tiny: one source-spine item, one ordering rule, one reconstruction question, one source-return link. For a repeated seminar or course, the route should have versioned carriers, task results, and low-value repairs. The size changes; the source-return discipline does not.

Do not use popularity as learning evidence. Attendance, satisfaction, applause, or “people liked the story” may be engagement telemetry, but it is not reconstruction evidence. Reconstruction evidence asks whether learners can rebuild the source relation, apply it to a new case, name a boundary, or choose a repair.

NSTD.8:6 - Bias-Annotation

A learning route can be mistaken for the subject it teaches: its lesson order, exercise sequence or analogy then replaces the source relations. Keep those relations available and show how each teaching move prepares the next learner task. Worked examples belong in a pattern when they explain its reusable method. Maintain a complete seminar or course separately when its timing, facilitation and session-specific exercises would obscure that method.

Copying the source corpus’s modules into a course can leave later selection unpractised. Keep the source modules available, then add interleaving or spacing when the learner must later discriminate, retrieve or transfer relations across topic boundaries.

NSTD.8:7 - Conformance Checklist

NSTD.8:8 - Common Anti-Patterns and How to Avoid Them

NSTD.8:9 - Consequences

The benefit is a path that helps learners recover and use the source ideas. Its cost is designing the necessary connections and obtaining observations proportionate to the learning claims made.

NSTD.8:10 - Rationale

Different learning aims require different combinations of explanation, examples, attempts, feedback and later returns. Keeping the subject structure accessible permits a teaching route to vary those combinations without making the lesson sequence the only account of the subject.

A modular source corpus can support lookup and a first introduction while still leaving later selection unpractised. When learners must choose among similar methods without a topic label, the learning route needs those contrasts and selection tasks. When later retrieval matters, it needs an appropriate delay and return. The source organization remains available; whether the learning order should follow it depends on the task and the support already available.

NSTD.8:11 - SoTA-Echoing

Mengelkamp et al.’s “Effects of Reading Goal Instructions on the Comprehension and Metacomprehension of Informative Narratives” makes study goals and metacomprehension risk visible; Georgiou et al.’s “Large-scale study of human memory for meaningful narratives” shows that long narratives can be remembered as gist and sequence rather than source detail; Hoffmann’s “The Tensions of Scientific Storytelling” supplies a science-storytelling example where unresolved tension and source return matter. Dunlosky et al.‘s “Improving Students’ Learning With Effective Learning Techniques” rates practice testing and distributed practice as high-utility techniques and treats interleaved practice as promising for appropriate situations. Rohrer and Taylor’s “The shuffling of mathematics problems improves learning” directly shows the risk of standard blocked textbook practice and the benefit of spaced and mixed practice in mathematics problems. Kang’s “Spaced Repetition Promotes Efficient and Effective Learning” gives a policy-level synthesis: spacing repeated encounters with material improves long-term learning and can be combined with tests. NSTD.8 retains the Dunlosky, Rohrer–Taylor and Kang contributions as historical anchors for spacing and interleaving questions. The bounded source contributions here inform learning-route design, reconstruction and source return, not a complete pedagogy doctrine.

For the attachment and prefix-support work, Noetel et al. (2022) supports mechanism-specific attention to signaling, correspondence and pacing rather than a rule to add pictures everywhere. Sinha and Kapur (2021) supports distinguishing problem solving followed by instruction from unsupported failure; its conditional, largely mathematics/physics evidence does not make all difficulty productive. Wesenberg et al. (2025) motivates checking whether a worked example also permits a consequentially wrong rule; the studied brief units do not establish a universal order for long routes. Krieglstein et al. (2025) shows why retrospective load reports need an explicit timing and segment: the reported primacy effect concerns self-report in the studied setting, not a conversion from source-structure density to human burden. These contributions qualify the choice of support and the inference from a reader response; none validates this entire route method or its ordinal values.

Operational payload:

• From reading-goal work, declare the learner use before the lesson route. A route for curiosity, exam preparation, professional use, or framework authoring needs different reconstruction tasks.
• From metacomprehension risk, ask learners to reconstruct or apply source structure, not only rate whether they understood.
• From memory work, long routes need anchors and returns. Repetition should protect source spine rather than repeat slogans.
• For durable retrieval, consider spaced practice and delayed retrieval rather than infer retention from immediate success. Judge the result under the actual schedule and task.
• From interleaving work, blocked topic practice can hide the real choice problem. Mix adjacent owners, cases, or problem types when the learner must later decide which structure applies.
• Preserve the source organization for lookup and source return. A first introduction may follow it when that supplies the needed support; choose a different order for a later task that requires contrasts, mixed selection or delayed retrieval.
• From scientific storytelling, unresolved tension can be taught honestly. The route can preserve open questions instead of pretending closure.
• For a claimed teaching improvement, compare the relevant route versions and affected outcomes. A low score is not required before a worthwhile improvement can be considered.

The practical result is a route whose explanations, attempts and later returns support the declared learner use. Keep an adequate source-aligned segment; repair a missing connection, an unsupported demand or an unpractised selection only where it changes the intended result.

NSTD.8:12 - Relations

Uses A.6.3.NAR, E.6, E.11, E.17, E.17.AUD, NSTD.1, NSTD.2, NSTD.5, NSTD.6, E.21, E.22, E.23, B.4, and G.11. NSTD.5 bounds motivation and interest; NSTD.6 evaluates one route version; E.22 frames under-specified quality questions; E.23 repairs a declared changed slice; G.11 refreshes source, telemetry, edition, or practice currentness; B.4 is only for evolution claims over the learning route. Reopen when learner use, source spine, source architecture, learning-route architecture, interleaving plan, spacing or retrieval schedule, teaching-test evidence, source currentness, edition, or evaluation result changes. Support-map entry: open Architecture and Narrative Work Bridge when the learning route narrates architecture, copies source architecture as course architecture, uses views, source spine, or actual-structure feedback; open Semiotic And Language-Precision Bridge when didactic coarsening, cue or backoff, explanation, style, or language-state choice matters; open Source Use And Refresh Map when teaching, memory, cognition, interleaving, spacing, or learner-test source support changes; use the refresh route when learner telemetry changes.

NSTD.8:End

Narrativization and Narrative Studies Principles Framework Sources and Edition Notes

NSTD.Sources:1 - Source use and refresh map

The sources below contribute to particular narrative operations. Older conceptual anchors remain useful within their scope; recent studies and systems add bounded results. The extension across factual, mathematical, fictional and live accounts is this DPF’s synthesis. A citation does not establish every condition of that synthesis.

Meretoja’s Narrative and Human Existence: Ontology, Epistemology, and Ethics remains philosophical background, not an independent warrant for the operations or scales above.

Return to the affected source when its claim is contradicted, overextended or no longer suitable for the intended use. Apply G.2/G.11 when the work is to synthesize or refresh the relevant SoTA traditions; ordinary comparison with a story’s canon or a lesson’s source remains direct.

NSTD.Sources:2 - Name and edition route

Package name: Narrativization and Narrative Studies Principles Framework.

Public prefix for package pattern ids: NSTD.*.

NSTD.* identifies this Domain Principle Framework’s patterns; A.6.3.NAR identifies the Core narrative-construction pattern.

Publication edition: 22 September 2026.

The Architectural Reference explains the connected language and the consequences of these sources for its use.

NSTD.Sources:End