Patterns

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

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 DPF Precision Restoration And Owner Map 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

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 DPF Precision Restoration And Owner Map 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)

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