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.
| Test | Ask | If unclear |
|---|---|---|
| Source structure | Which relations matter to this reader: for example dependencies, cycles, alternatives or chronology? | Inspect the needed source portion with NSTD.1; a provisional sequence may help expose the missing relation. |
| Reader traversal | What should the reader encounter first to do the intended work? | Try two short orders and compare what each makes easier to recover. Authorial and expressive aims can be part of that use. |
| Hidden relations | Which necessary relation becomes hidden or weaker in this order? | Restore it in the passage or provide a usable return to the source. |
| Misreading | Does a visible feature of this sequence invite a wrong inference? | Correct that inference with the smallest useful sentence, marker or change of order. |
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.
| Symptom | Likely hidden order | Repair |
|---|---|---|
| Readers think the first-mentioned cause is the strongest cause. | Salience order mistaken for causal order. | Mark salience as viewpoint or teaching order; return causal-strength claims to the evidence or source governing pattern. |
| Learners can retell the lesson but fail formal exercises. | Didactic story order mistaken for proof order. | Add proof-return checkpoints and separate example order from theorem dependency. |
| Stakeholders read the explanation order as the project decision sequence. | Explanation order mistaken for decision or work order. | State the order actually used; refer to the decision record or work plan when the reader needs that different sequence. |
| Fans like a reveal but continuity breaks. | Reveal order hides source canon constraints. | Add source-pack return and causal and continuity support before dramatic reveal. |
| A generated story has plausible steps but drops a required source relation. | Generated sequence obscures its source constraint. | Compare the candidate with that relation; repair its plan or realization through NSTD.7. The defect can be evaluated before either is repaired. |
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.