A.6.3.NAR - Structure-to-Narrative Rendering
Type: Specialization pattern Status: Stable Normativity: Normative unless marked informative
A.6.3.NAR:1 - Problem frame
Use this pattern when selected source structure must become a readable sequential account for a declared reader or listener use. In plain language: turn this structure into a narrative that this reader can follow without hiding what the narrative leaves behind. Typical cases include a scientific mechanism turned into a paper section, an architecture trade-off turned into a team explanation, a conceptual graph turned into a lesson sequence, or an event graph turned into a story draft.
Start from the reader’s practical need. Select the source structures that matter for that need, choose a useful order and connective account, draft the narrative, then compare it with the sources for preservation, foregrounding, loss and unsupported additions.
Plain starting vocabulary:
| Term | Plain meaning |
|---|---|
source material | The episteme, publication, model, graph, architecture description or view, evidence set, situation record, event stream, proof field, or source pack from which the narrative is prepared. In an exact case, distinguish the source episteme from every form, carrier, world-side object, or additional input. |
selected source structures | The relations, constraints, events, mechanisms, dependencies, conflicts, alternatives, or changes that must remain recoverable for the reader’s use. |
source-structure selection rationale | Why these structures, rather than other available structures, serve this reader or listener use. |
source temporal posture | Whether the material concerns retrospective or reverse-engineered actuality, live unfolding, prospective planned structure, prospective fiction or canon, or a mixed case. State it only when it changes how the narrative may be read. |
rendering mediation mode | Whether the narrative uses source claims directly or depends on an architecture description, view, decision, telemetry record, or another independently identified description. |
reader or listener use | What the reader or listener must understand, decide, predict, reconstruct, or do after using the narrative. |
ordering and connective account | The chosen event, causal, discovery, didactic, tension, traversal, or other order, plus the links that explain why one step follows another. |
narrative rendering | The receiving sequential account. A page, audio file, slide, or publication carrier can express or make it available without being the account’s claim-bearing identity. |
loss and return | What the narrative omits, weakens, rearranges, or cannot support, and where the reader returns when that missing structure matters. |
narrating or rendering worker | The person, team or system preparing the narrative. A dated Work claim follows A.13 and independent A.15.1 admission; F.6 applies only when precise assignment-bound attribution matters. Any authority claim has its own grounds. |
structural-information question | How much of the selected source structure can this reader correctly extract from the narrative under the stated preparation, access and budget? Use C.2.8 for the characteristic, C.33 for architecture-use adequacy and the applicable domain evaluation for a local scale. |
First useful move. Write a useful narrative and give the reader enough source and ordering information to see what it preserves, foregrounds or omits. A compact note can carry that information. Add a source-return condition when omitted structure or a changed question requires it; any excluded downstream use follows F.19:4’s full guard test.
What goes wrong if missed. A memorable sequence substitutes for the source structure. Readers retain the story but cannot reconstruct the relations that licensed it, or they treat a connective sentence added for fluency as a source claim.
What this buys. Narrative ordering can make tangled structure usable while selection, sequence, loss and unsupported additions remain inspectable. Any proof, evidence or authority claim still needs its own grounds.
Ordinary use. For low-reliance teaching, orientation, or internal explanation, the useful narrative with the needed source and ordering information is enough. Exact endpoint identities and a formal construction record are not prerequisites for this first result.
Reliance-facing use. Open the exact branch only when the receiving use makes claim-level identity and preservation evidence material: for example, the narrative must travel independently, be cited or disputed, support a new operation of inspection or reasoning through a change of representation, enter generated-output admission under an identity-bearing receiver, support consequential reliance, or satisfy another named receiver that requires exact identity. A public context is a cue to ask which receiving requirement applies; publicness alone is not sufficient.
Then recover source episteme X, receiving narrative episteme Y, and construction n : X -> Y, together with the additional source dependencies, scheme relation, loss, evidence, or assurance required by that receiving use.
Carrier export, generated-output admission, publication, evidence, assurance, ethics, and work authorization are separate questions; apply the corresponding pattern only when that claim is current.
A.6.3.NAR:2 - Problem
Projects often need narrative because selected source structures are too tangled for a reader to use directly. A mechanism, architecture, model, evidence set, or event graph may need a beginning, order, tension, action, update point, or learning path before its intended reader can follow it.
Without A.6.3.NAR:
- narrative is treated as a final style-polishing step;
- narrative is treated as mere lossy summary even when sequence-making is the main representational move;
- selected structure, ordering decisions, event models, and lost relations disappear behind fluent prose;
- engagement is allowed to raise confidence, authority, ethical permission, or policy force without the current evidence relation, assurance result, ethical basis, or policy basis required for that stronger claim;
- generated narrative output is trusted because it is coherent or dramatic;
- exact identity and assurance fields are demanded before an ordinary reader-useful narrative exists, making the pattern needlessly hard to enter.
A.6.3.NAR:3 - Forces
| Force | Tension |
|---|---|
| Selected source structure vs reader sequence | A reader often needs an ordered path, while the selected source structure may be a graph, mechanism, option set, architecture, or evidence field rather than a line. |
| Engagement vs truth boundary | Tension, viewpoint, protagonist, and pacing can help attention, but they do not widen truth, evidence, authority, ethical permission, or admissible downstream use. |
| Compression vs recoverability | A narrative foregrounds some structure and leaves other structure behind. The useful loss must be visible. |
| Event comprehension vs non-event structure | Some selected source structures involve events and actions; others involve dependencies, constraints, alternatives, or architectures. The pattern must support both without forcing a fiction model. |
| Domain richness vs a usable common method | Narrative domains use different ordering, viewpoint and evaluation conventions. Use the relevant domain distinctions while keeping the source-to-sequence comparison explicit. |
A.6.3.NAR:4 - Solution
Produce the ordinary useful result first:
- Name the reader or listener and the practical use: what must become understandable, reconstructible, predictable, or discussable.
- Point to the source material and select only the structures needed for that use. Say why those structures matter.
- State temporal posture or mediation only when it changes the ordering or the trust boundary.
- Choose an ordering and connective account: event, causal, discovery, didactic, tension, traversal, or another explicit rule.
- Draft the smallest narrative that lets the reader follow that path. For technical prose, use F.19 for plain-language repair.
- Compare the draft back to the source material. Record what it preserves and foregrounds, what it omits or weakens, and which connective or interpretive statements are not source claims.
- State the supported narrative use. When omitted structure or a changed question requires return, identify the source to restore or the stronger claim-specific question and its governing pattern. Any excluded use follows F.19:4’s full guard test.
Use this compact note when it helps make the source-to-narrative comparison inspectable; otherwise keep the needed information in the narrative and its source references. Include only entries that affect use or block a locally grounded overread:
| Narrative note entry | Practical question |
|---|---|
| Reader/listener and use | Who needs the narrative, and what should it enable? |
| Source material | What page, episteme, graph, model, record, or source pack will the author return to? |
| Selected structures and rationale | Which selected source structures matter, and why these? |
| Ordering and connective account | Why does this path help the reader, and which links are explanatory additions rather than source claims? |
| Preserved and foregrounded | What can the reader still recover, and what receives extra attention? |
| Omitted, weakened, or unsupported | What is deferred, lost, rearranged, or newly suggested without source support? |
| Use boundary | What use does this narrative support, and within which limits? |
| Return or stronger question | When must the reader restore source material, or what stronger claim-specific question must be answered before the use continues? |
A.6.3.NAR:4.0.1 - Exact construction branch
Open this branch when the identified receiving use depends on exact claim identity and preservation, under §1. Citation, distribution or generated status is a cue to examine that need, not a requirement by itself. Apply E.24.PUB separately when a publication occurrence, form, carrier, audience or bounded publication use matters.
Then establish the A.6.3 construction n : X -> Y:
- identify source episteme
Xand receiving narrative epistemeYindependently under C.2.1 by claim content, EntityOfConcern, and effective interpretation rules (ReferenceScheme); - require the same EntityOfConcern; a narrative about another concern requires A.6.4;
- state how claims in
Xand any named additional source epistemes construct the sequential claim content ofY; - state the endpoint scheme relation, ordering rule, preserved and foregrounded content, admitted loss, prohibited strengthening, applicability, and return; and
- cite every correspondence relation on which the construction depends and test it under its direct predicate.
Recover X as the source episteme whose claim content and EntityOfConcern supply the narrative source, and recover Y as the receiving narrative episteme. Treat input models and publications according to their source claims and keep forms and carriers in their direct roles. If the receiving item lacks recoverable claim content, an EntityOfConcern, or an effective reference scheme, keep it as candidate prose or a carrier and stop before asserting exact NAR.
When the exact branch is needed, use this fuller local record if the receiving use needs this form; otherwise retain the required construction information in the account already being used:
StructureToNarrativeRenderingCase:
sourceEpistemeRef: X
receivingNarrativeEpistemeRef: Y
viewingConstructionRefOrStatement: n : X -> Y
additionalSourceEpistemeRefs?:
exactCorrespondenceRelationRefs?:
selectedSourceStructureRefs:
sourceStructureSelectionRationale:
sourceTemporalPosture?:
renderingMediationMode?: direct-source-claims | architecture-mediated | mixed
architectureMediationEpistemeRef?:
sourceStructureDefinitionClaimEpistemeRefs?:
sourceStructureConstraintClaimEpistemeRefs?:
narrativeConstructionWorkRef?:
narratingOrRenderingSystemRef?: U.EntityRef resolving to an admitted U.System
narratingOrRenderingSystemRoleKindRef?: U.KindRef resolving to one local system-role kind
narratingOrRenderingSystemRoleAssignmentRef?: U.RelationRef constrained to U.SystemRoleAssignment
readerOrListenerSystemRefs[]?: U.EntityRef values resolving to admitted systems
readerOrListenerSystemRoleKindRefs[]?: U.KindRef values resolving to local system-role kinds
readerOrListenerSystemRoleAssignmentRefs[]?: U.RelationRef values constrained to U.SystemRoleAssignment
readerInterestOrUseHypothesis?:
intendedReaderOrListenerUse:
orderingRationaleOrTraversalRule:
preservedStructure:
foregroundedStructure:
coarsenedOrLostStructure:
unsupportedStrengtheningBlocked:
epiplexityOrStructuralInformationRef?:
recoverabilityClassOrSourceBasisReturnCondition:
eventModelSupport?:
engagementOrMotivationClaim?:
admissibleUse:
nonAdmissibleDownstreamUse?:
strongerClaimQuestionsAndActions[]?:
selectedSourceStructureRefs identifies the selected structures. A PatternID mentioned in sourceStructureSelectionRationale or surrounding prose only locates the content used to recognize or test them; it is not another structure reference. Include sourceStructureDefinitionClaimEpistemeRefs or sourceStructureConstraintClaimEpistemeRefs only when the identity of one or more definition or constraint claims changes reconstruction, comparison, dispute, or reliance. Both lists may be present and each resolves only to claim-bearing C.2.1 epistemes of the named kind.
Resolve X and Y to their C.2.1 identities and use this record only for the construction account. When production history matters, recover each performer’s A.13 core and independently admit dated narrative-construction Work under A.15.1; add F.6 afterward only when precise assignment-bound attribution is current.
Include readerInterestOrUseHypothesis only when an assumption about the reader affects selection or ordering; retain it as a hypothesis. Include each optional System, system-role-kind, or assignment reference only when its referent and direct claim obtain independently.
Connect source epistemes, parameters, methods, tools, and Y through direct relations or A.6.1 bindings. If the Work first constitutes Y and that inception claim matters, use A.15.PROD to test that separate local claim.
epiplexityOrStructuralInformationRef? refers to a qualified C.2.8 comparison or estimate when the narrative use depends on structural amount. Identify the receiving narrative episteme, its expression, the observer and relevant preparation, access and budget. A formal epiplexity or other mathematical estimate uses the C.29 model-to-characteristic correspondence; a domain estimate retains its scale and evaluation conditions. The field remains optional for the ordinary narrative and note.
nonAdmissibleDownstreamUse?, also named groundedNonAdmissibleDownstreamUse?, is one optional explanatory field governed by F.19:4’s plausible-reader test.
Publication remains separate. E.24.PUB identifies any occurrence that makes selected episteme Y available to an audience and bounded use through one independently identified expression and the state or realization of its independently identified carrier. Any selected reusable publication form constrains that expression separately. C.2.1 identifies Y, A.6.3 governs the construction n, and E.17.0 independently decides whether Y has U.View membership.
Use this optional unfolding block when an independently identified selected structure must be carried into a reader-facing sequence with explicit loss and return:
NarrativeUnfoldingStructureBlock:
sourceEpistemeRef: X
structureBeingRenderedRef:
unfoldingStructureBeingRenderedRef?:
narrativeOrderingStructureRef:
readerActSequenceHypothesis?:
receivingNarrativeEpistemeRef: Y
preservedStructure:
lostOrCoarsenedStructure:
narrativeStructureUseReturnCondition: return to source episteme X, then through its designation relations to the selected source structure when an omitted branch or exact order matters; apply the relevant pattern for any stronger claim
blockedOverread?: optional explanatory guard under F.19:4's plausible-reader test
structureBeingRenderedRef, narrativeOrderingStructureRef, and any receiving narrative episteme occupy different positions. Use unfoldingStructureBeingRenderedRef only when the source structure is itself a constraint-governed unfolding structure. Apply A.22.CGUS identity and membership tests to the source or narrative-ordering structure whose CGUS membership is claimed. The block records references to those structures; ordinary NAR does not require such a qualification. returnCondition names the same value as narrativeStructureUseReturnCondition, not a second return rule.
A.6.3.NAR:4.1 - Ordinary and reliance-facing cases
An internal explanation, teaching example, orientation narrative, or early team account normally closes with the narrative and its source comparison. A compact note is useful when it makes their relation inspectable.
Move progressively. Add temporal posture, event-model support, mediation, viewpoint, engagement, or worker history only when each distinction changes the use or blocks a likely error. Open the exact construction branch only at its declared trigger. A reliance-facing case then carries forward the ordinary narrative and its source comparison, adding only the exact account required by the receiving use.
A.6.3.NAR:4.2 - Exact same-EntityOfConcern and correspondence-mediated profiles
This subsection applies only after the exact branch is open. Exact NAR is same-EntityOfConcern: X and Y designate the same concern even when their effective reference schemes differ. Similar content or a declared correspondence does not relax this rule. If the receiving narrative concerns another entity, use A.6.4 and state the retargeting relation there.
Use the direct-source-claims profile when n constructs Y from claims in X and fixed configuration. A situation, event stream, domain model, proof-dependency field, evidence set, fictional canon, or source pack can contribute only through claims in X or through named additional source epistemes and relation occurrences. The raw object, graph, set, or pack is not the source endpoint.
Use the correspondence-mediated profile when n depends on relations among X, additional source epistemes or their designated structures. Recover each needed relation under its defining predicate and identify the source assertion used by the construction. That assertion may remain within a broader source episteme; a separate relation-description episteme is needed only when the use depends on it. C.34 applies only when its correspondence test fits the architecture use.
A.6.3.NAR:4.2.1 - Direct and architecture-mediated routes
In the direct route, the source episteme states or designates the source situation, event structure, proof dependencies, canon claims, or source-pack claims that n orders. Viewpoint discipline may help, but X, Y, and n remain the central objects.
In the architecture-mediated route, one architecture-description, architecture-view, decision, candidate-structure, or telemetry episteme participates as X or as a named additional source episteme. Independently recover any selected A.22 structures, world-side holons, decisions, relations, or telemetry occurrences that its claims designate. The return chain is Y to source episteme(s), then through their designation relations to structures or occurrences when those are current.
Keep every selection, coarsening, abstraction, omission, ordering, and correspondence explicit by using the applicable C.32.*, C.33, C.34, architecture-description, or decision test. NAR defines only n’s source-to-narrative construction, preservation, loss, and return boundary.
In either route, identify temporal posture when it affects interpretation. A historical reconstruction, live commentary, prospective project narrative and fictional continuation have different source claims, uncertainty and ordering conditions. A dated narrative-construction Work claim remains separately governed by A.13 and A.15.1, with F.6 only for precise assignment-bound attribution.
A.6.3.NAR:4.3 - Ordering rationale
The ordering rationale is the structure-to-sequence rule.
Common ordering rationales:
| Ordering rationale | Use when |
|---|---|
| Event order | The selected source structure is a sequence of happenings or state changes. |
| Causal order | The selected source claims describe causal links whose order matters to understanding a mechanism, dependency, intervention, or consequence. |
| Discovery order | The narrative teaches how a claim, design, or explanation was found. |
| Didactic order | The source material is reordered so a learner can build prerequisites and reconstruct the selected source structures later. |
| Tension order | The narrative preserves conflicts, trade-offs, obstacles, failed attempts, or unresolved alternatives. |
| Traversal rule | The source material presents a graph, architecture, relation set, or option field and the narrative follows a declared path through it. |
If the source material only changes carrier form, file format, export layout, OCR extraction, or byte order, this pattern is not open. Carrier serialization alone is not narrative rendering.
A.6.3.NAR:4.4 - Event model, viewpoint, and agency
If the narrative asks readers to understand events, actions, mechanisms, or change, state enough event-model support to preserve the relevant happening or mechanism type, participants, causal or dependency links, update points, and what the reader is expected to predict or revise.
If viewpoint, narrator, focalized object, protagonist, or agency choices affect understanding, keep their detailed vocabulary in the narrative domain. In FPF Core the reusable check is: which selected source structure does the viewpoint foreground, hide, or weaken for this declared use? Invoke another FPF pattern only for a specific stronger claim that pattern defines.
A.6.3.NAR:4.5 - Engagement, ethics, and assurance boundary
Engagement is a use claim. When engagement or motivation matters, state the intended effect, the source structure that may not be distorted for that effect, the affected reader or decision context, and the return condition. Use F.19:4’s plausible-reader test for any optional explanatory guard.
Use D.1 for ethical value-frame entry, D.2 through D.4 for multilevel conflict and decision use, D.5 for bias, human impact, or ethical assurance, A.10 for evidence, and B.3 for assurance. Apply only the patterns needed by the current claim.
A.6.3.NAR:4.6 - Reopen, lower, and return rule
An ordinary narrative remains fit while its source material, selected structures, reader use, ordering/connective account, loss statement, and return still match the actual use. An exact case additionally depends on the current identities of X and Y, the construction n, its source relations, and every qualification used by the receiving claim. Repair the smallest affected account and its dependent claims.
| Trigger | Required move |
|---|---|
| Source material or selected structures change | Compare the narrative with the changed source. Retain it when the change leaves its selected structures, claims and supported use unchanged; otherwise repair the affected ordering, preservation, loss, unsupported additions or return, and restrict only uses no longer supported. |
An exact discriminator of X, Y, an additional source episteme, or a depended-on relation changes | Reidentify only the changed object; restate the affected part of n, preservation, loss, and return. Use C.33 only for architecture-relevant captured/lost structure and G.2 only for its SoTA harvesting/synthesis claims. |
| Intended reader or listener use becomes stronger, broader, or more reliance-facing | Reassess the narrative for the changed use and retain any already supported use. Open the exact branch only if the changed receiver now makes claim identity material, and add only the identity, source-chain, evidence, assurance, ethics, publication, or policy account that receiver requires; otherwise revise the ordinary account only as needed. |
| Ordering rationale or connective account changes | Reopen the ordering and visible-loss account. Use RT as well when the receiving operation still depends on changing the representation language or reasoning medium after the ordering is settled; use CSC when a narrower-use coarsened episteme is primary. |
| Source material is missing, stale, or unreachable, or a stronger claim still lacks its claim-specific result | Identify and restrict the uses that depend on the missing, stale or unreachable source or absent claim-specific result. Restore source access or obtain the needed result when the receiving task requires it; preserve already supported uses. Use G.11 when currentness or freshness is the live defect. |
| Generated output, source-pack plan, schema, or admission result changes | Use C.35 for admission of an affected generated result to architecture use and G.2 for its SoTA harvesting/synthesis claims; reopen NAR only for the affected source-to-narrative relation, loss, and return. |
| Domain narrative vocabulary or relevant narrative, NLG, or cognitive SoTA changes a relied-on field | Refresh that domain basis and replay the affected use; do not enlarge Core vocabulary merely to mirror the domain source. |
| Downstream use requires evidence, assurance, ethics, publication, policy, decision, or work authority that NAR does not supply | Keep NAR as the narrative construction account and state the stronger claim under A.10, B.3, D.1–D.5, E.24.PUB, or the pattern that defines the needed decision or Work relation. |
| A correspondence or preservation claim weakens | Use C.34 for the correspondence that remains only when the receiving architecture use is within its scope, and C.33 for captured/lost architecture-relevant structures. Revisit a depended-on C.2.8 structural comparison and its domain evaluation when the weakened claim changes what counts as correct recovery. Lower uses that required stronger sameness. |
| Observer preparation, access, assistance or budget changes for a relied-on structural-amount claim | Reopen that C.2.8 comparison under the changed conditions. Revise the narrative when the changed recovery no longer supports its stated reader use. |
A.6.3.NAR:5 - Archetypal Grounding
Tell: NAR turns selected source structure into a reader-useful sequence while keeping ordering, loss, unsupported strengthening, and source return visible. It is not a general story-writing pattern.
A.6.3.NAR:5.1 - Scientific mechanism narrative
A chemistry paper has calculations, candidate mechanisms, failed synthesis attempts and unresolved tension between theory and experiment. If the sources establish the discovery history, an internal explanation can follow it: failed attempts, structural clue, revised mechanism, new experiment, remaining uncertainty. Its note identifies the preserved claims and deferred calculations; any connective added to explain the sequence is distinguished from a source assertion. A mechanism-proof question returns to the calculations and experiment record.
When a receiving use needs exact preservation of this account, identify source episteme ChemistryMechanism-X and narrative episteme ChemistryDiscovery-Y about the same reaction case. DiscoveryNarrativization : X -> Y states the selection, scheme relation, discovery order, preserved and lost claims, any grounded proof-use exclusion, and source return. The calculation files express source content; the paper form and carrier express the narrative. Their file labels alone identify neither episteme.
A.6.3.NAR:5.2 - Architecture trade-off narrative
An architecture team needs to explain a candidate selection. It can order the account by the binding constraint, compared alternatives, decision and remaining trade-off. Preserve the decision’s stated basis rather than inventing the sequence by which the team discovered it.
Source fixture. For project system S, data must be processed at Plant P. Under the same workload W, candidate C1 processes at P with a measured median latency of 40 ms; C2 processes at regional site R outside P with a measured median latency of 30 ms. Decision D selects C1 because the placement constraint is mandatory. D does not authorize implementation.
Narrative. Decision D selects C1 because it processes S's data at Plant P, as the mandatory placement constraint requires. C2 processes at regional site R outside P, which would violate the mandatory placement constraint. Under W, its measured median latency was 30 ms, 10 ms lower than C1's 40 ms. D does not authorize implementation.
Comparison. The narrative foregrounds the constraint before the performance trade-off. It preserves both candidates, sites, workload, measured characteristic and decision basis; the 10 ms difference follows from the two comparable medians. It asserts no discovery history or actual implementation. This short fixture omits no source claim. For a changed workload or placement rule, return to the measurement and decision basis before carrying the selection forward.
When the receiver needs exact claim identity, ArchitectureTradeoff-X and ArchitectureRationale-Y concern the same project system, and ArchitectureRationaleNarrativization : X -> Y states the construction and return. Independently identified A.22 candidate structures are designated by the source claims. The posture is prospective during choice and retrospective when recounting the decision; publication, decision, synthesis and performed Work remain separate.
A.6.3.NAR:5.2.1 - Architecture narrative repair after source change
Later, a rejected candidate gains a new measurement basis and a placement constraint changes. The old story remains coherent but no longer preserves the live candidate set. Lower it to historical orientation, update the selected structures and ordering, state the changed loss and residual, and restore return to the current architecture description or decision material. In an exact case, reidentify only source epistemes whose C.2.1 identity changed, and restate the affected construction n under A.6.3.
C.33 carries captured and lost architecture-relevant structures: preserve the old rejected-candidate relation as history, capture the new candidate-set relation, and mark the obsolete measurement basis lost for current decision use. C.34 carries only a correspondence that remains. Implementation or decision use stays non-admissible until the architecture claim, decision result, or synthesis result and any required use relation are current.
A.6.3.NAR:5.2.2 - Live unfolding event narrative
A commentator narrates a football match while it unfolds. The ordinary narrative selects score state, possession changes, tactical shape, player roles and positions, momentum, and uncertainty, then uses event and tension order for live orientation. Here player roles is ordinary football language for tactical contribution and behaviour—such as pressing, covering, marking, playmaking, or providing width—not an asserted FPF system-role kind or assignment. The narrative does not turn provisional interpretation into settled event evidence.
Later analysis, statistics, rule disputes, injuries or official-result use returns to the event record and official sources. When replay or dispute depends on exact claim identity, identify event-record episteme MatchState-X, commentary episteme LiveNarrative-Y and their construction LiveNarrativization. The match is the concern, source claims describe its events, and audio expresses the narrative through its form and carrier.
A.6.3.NAR:5.3 - FPF seminar-route boundary
A team orders selected FPF claims for learners: EntityOfConcern discipline, problem frames, pattern use, relation records, source return, framework authoring, and improvement loops. The first result is a teachable route whose note records prerequisite order, deferred detail, reconstruction tasks, and return to exact FPF passages.
A separate E.24.PUB occurrence may make a selected narrative episteme available through a teaching form and carrier; publication neither constitutes the narrative episteme nor establishes the NAR construction.
A.6.3.NAR:5.4 - Franchise-continuation storycraft boundary
A storycraft team develops a proposed continuation using canon constraints, premise, theme, character agency, causal plot structure, viewpoint and stakes. The new events come from that story construction. NAR then orders the proposed events and relevant canon claims into a readable account, making selection, foregrounding, loss and source return explicit.
For an exact same-entity continuity account, identify the source episteme describing the proposed continuation and any additional canon-source epistemes, then identify ContinuationNarrative-Y about that same continuation. The construction states how its assertions follow from those sources. Canon alone does not supply newly invented events. Canon classification, story generation, rights, publication and narrative-quality evaluation remain separately governed. G.2 applies to SoTA source-pack synthesis and C.35 to generated results intended to inform architecturing, only when those uses are current.
A.6.3.NAR:5.5 - Homotopy-theory explanation boundary
A teacher turns graph-heavy mathematical material into a didactic sequence of definitions, dependencies, examples, counterexamples, theorem prerequisites, and proof-status boundaries. The ordinary note records which structures a learner can reconstruct, which proof details or generalizations are deferred, and when to return to formal statements.
When a mathematical use needs exact preservation, identify HomotopySource-X and HomotopyNarrative-Y about the same mathematical EntityOfConcern and state the construction, ordering and loss. Mathematical-lens, proof, source-use, publication and teaching-evaluation claims retain their applicable tests.
A.6.3.NAR:5.6 - Automated event-graph narrative
An LLM or NLG system uses source claims designating an event graph, agent goals, constraints, and a domain schema, then performs generation Work and proposes the resulting story-scene carrier. The first inspection compares the proposed sequence with the selected event relations, marks preserved constraints, omissions, and hallucinated connective claims, and limits use to candidate review.
Use C.35 when the generated result is intended to inform architecturing; it tests that result’s next architecture use. If reliance-facing use later opens exact NAR, independently identify EventPlan-X and StoryScene-Y, then state EventNarrativization : EventPlan-X -> StoryScene-Y, the additional source dependencies, loss, prohibited strengthening, and return. The graph and schema are not X; the system’s generation Work, evidence, assurance, and publication remain separate.
A.6.3.NAR:6 - Bias-Annotation
| Bias | How NAR counters it |
|---|---|
| Story-substitution bias | Requires selected source structure, visible loss, bounded use, and source return before the narrative is relied on. |
| Formality-first bias | Produces a useful narrative and source comparison without opening an exact identity record that the receiving use does not need. |
| Engagement-authority bias | Treats engagement as a bounded use claim; evidence, assurance, ethics, and policy force remain with the patterns that define those claims. |
| Sequence-naturalization bias | Makes the ordering and connective account explicit instead of letting a fluent order look inevitable or source-given. |
| Carrier-serialization bias | Keeps file export, stream order, OCR, and layout changes outside NAR unless selected source structure is ordered into a narrative path. |
| Generated-fluency bias | Keeps generated output as candidate material until source comparison and any independently required admission pass. |
| Narratology-import bias | Keeps narratology and storycraft detail in domain practice instead of creating automatic FPF Core kinds. |
A.6.3.NAR:7 - Conformance and counterexample replay
| Check | Pass condition |
|---|---|
CC-NAR-1 | An ordinary user can produce a readable narrative before supplying exact endpoint identities or assurance fields. |
CC-NAR-2 | Reader/listener use, source material, selected structures, and the reason for selecting them are clear. |
CC-NAR-3 | The ordering and connective account are explicit enough to distinguish source relations from narrative links added for readability. |
CC-NAR-4 | The narrative has been compared with its source for preservation, foregrounding, omission, weakening, rearrangement, and unsupported strengthening. |
CC-NAR-5 | The supported use is clear; source return is specified when omitted structure or a changed question requires it. Any excluded use passes F.19:4’s full guard test. |
CC-NAR-6 | Temporal posture, mediation, event-model support, viewpoint, engagement, and worker history appear only when each changes use or blocks a likely overread. |
CC-NAR-7 | Evidence, assurance, ethics, policy, publication, decision, and Work claims use the patterns that define or test those claims. |
CC-NAR-8 | The exact branch opens when the identified receiving use depends on claim identity and preservation. Citation, distribution or generated status alone does not establish that need. |
CC-NAR-9 | In that branch, X and Y are independently identified by claim content, EntityOfConcern and effective interpretation rules (ReferenceScheme); a model, file or prose label alone supplies none of those identities. |
CC-NAR-10 | Exact n : X -> Y states same EntityOfConcern, claim construction, endpoint scheme relation, ordering, preservation, loss, prohibited strengthening, applicability, and return. |
CC-NAR-11 | Additional source epistemes and correspondence dependencies are exact when used; Work, system, system-role kind or assignment, method, publication, carrier, evidence, assurance, and U.View membership remain separately identified and must satisfy their own definitions or tests. Completing the exact record does not itself authorize reliance. |
CC-NAR-12 | Changes to the source, selected structure, order, loss, use, exact identity, depended-on relation or return are checked for their effect on the narrative. Preserve unaffected uses; repair affected content or restrict only uses no longer supported. |
Counterexample replay:
| Case | Required result |
|---|---|
| Ordinary entry | A team can turn an architecture trade-off structure into a useful explanatory sequence and loss note without first inventing X, Y, n, Work, or assurance records. |
| Preserve vs retarget | Exact NAR requires the same EntityOfConcern; a different narrated concern requires A.6.4 even when derived from X. |
| Same vs different scheme | Narrative order may be primary in either case. Use RT as well when a change of representation language or reasoning medium supports an operation beyond narrative ordering. Scheme difference alone establishes neither n nor correspondence. |
Candidate vs U.View | A valid narrative episteme and NAR construction can fail conformance to viewpoint P. That failed test grants no U.View membership through P; conformance to another viewpoint remains independent. |
| Source publication/form/carrier | A publication can make X available and a form or carrier can express it; none becomes X, and a narrative page or audio file is not Y. |
| Narrative order | Chronology, tension, or didactic order is a declared construction rule, not automatically world-side event order, proof order, performed-Work order, or an obtaining relation. |
| Controlled loss | If Y is usable only under declared loss, narrower use, and source return, coordinate CSC; NAR ordering alone does not make the loss admissible. |
| Grounded source, ungrounded narrative | Grounding of X or a designated evidence set does not ground Y; recover a separate EpistemeEmpiricalGroundingRelation for Y only when its own claims satisfy that rule. |
| Selected structure overread | NAR may order an A.22 structure designated by source claims. Identify the source and receiving epistemes independently; keep the selected-structure and narrative-ordering positions distinct. |
A.6.3.NAR:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | What fails | Repair move |
|---|---|---|
| Identity dossier before narrative | Ordinary teaching or orientation stalls before anyone receives a useful account. | Draft the smallest reader-useful sequence and source comparison first; open exact identity only when a named receiving use triggers it. |
| Good story as source replacement | The narrative is memorable, but later users cannot recover the selected source structure. | Restore the selected structures, preservation/loss, bounded use and source return in the narrative or its source comparison; add an exact construction account only when the receiving use requires it. |
| Tacit selection as narrative success | The author or model picked structures, but no one can explain why they serve this reader. | Recover the selection rationale and intended reader use. Retain only a use supported by that account; if none is established, keep the narrative as a draft for revision. |
| Sequence by habit | Chronology, textbook order, or dramatic order is used without saying why it helps or what it hides. | State the ordering/connective account and compare it with the source. |
| Engagement as evidence | Attention, transportation, or emotional uptake is treated as stronger truth or permission. | Keep engagement as a bounded use effect; use A.10, B.3, or D.1–D.5 only for the specific evidence, assurance, or ethics claim. |
| Narratology word import | Plot, focalization, voice, protagonist, suspense, or narrator are treated as automatic Core kinds. | Keep domain vocabulary in narrative practice unless a separate Core decision admits a reusable distinction. |
| Generated narrative by fluency | LLM output is accepted because it reads coherently. | Compare it with selected source claims, use C.35 when the generated result is intended to inform architecturing, and open exact NAR only if the receiving use requires it. |
A.6.3.NAR:9 - Consequences
Positive consequences:
- A reader receives a usable sequence before formal identity work is required.
- Selection, ordering, connective additions, loss, and return remain inspectable.
- Exact episteme identity and source dependencies remain available when the receiving claim needs them.
- Human-authored and generated narratives face the same source-comparison boundary; their production histories remain separate from the narrative relation.
- Domain narrative conventions can be used without confusing them with FPF Core kinds.
Costs and trade-offs:
- Authors must compare the narrative with the source rather than judging it by fluency alone.
- Reliance-facing narratives require exact identity and preservation work proportionate to the receiver’s use.
- If missing selected structure or source return makes the stated use unsupported, narrow the use to one whose requirements still hold, or keep the narrative as a draft.
- Evidence, assurance, ethics or policy claims add their own required work.
A.6.3.NAR:10 - Rationale
Narrative makes non-linear structure usable by giving readers a path through events, mechanisms, evidence, options, architecture decisions, or prerequisites. That strength is also the risk: a well-formed story can make a source look simpler, more certain, more complete, or more permissible than it is.
The narrow reusable move is therefore reader-first and progressive. Choose structure for a use, order it, connect it, draft the account, and expose loss and return. Exact n : X -> Y is the stronger description of that move when a receiving use needs claim-level identity; it is not the entrance fee for every explanation.
A.6.3.NAR:11 - SoTA-Echoing
| Source or practice anchor | Contribution | NAR use | Scope and limits |
|---|---|---|---|
| Roald Hoffmann, “The Tensions of Scientific Storytelling” (American Scientist, 2014) | Adopt as practice grounding: scientific narratives order calculations, failed attempts, mechanisms, unresolved tensions, and discoveries rather than merely decorating results. | Grounds the discovery-order worked case and the need to retain unresolved tension and source return. | Historical practice anchor, not current cognitive SoTA. |
Wolf Schmid, Narratology: An Introduction (2010), and Matei Chihaia, Introductions to Narratology: Theory, Practice and the Afterlife of Structuralism (2012) | Adapt source material, selection, composition, order, viewpoint, and presentation as domain distinctions. | Grounds the ordering/connective account and viewpoint-sensitive loss. | Historical domain anchors; fiction-specific vocabulary does not become FPF Core ontology. |
| Tan T. Nguyen, “A Review of Mechanistic Models of Event Comprehension” (2024); Lijuan Chen and Xiaodong Xu, “Neural and Behavioral Evidence for Differential Processing of Narrative Perspective in Novel Reading” (2026); Christoph Mengelkamp, Stefanie Golke, and Markus Appel, “Effects of Reading Goal Instructions on the Comprehension and Metacomprehension of Informative Narratives” (2025); Antonios Georgiou, Tankut Can, Mikhail Katkov, and Misha Tsodyks, “Large-scale study of human memory for meaningful narratives” (2025) | The named studies examine event models, prediction and update, reading-goal effects, reconstruction, memory loss, metacomprehension error, and viewpoint-sensitive recovery. | Supports triggered event-model/viewpoint fields, reader-use entry, source comparison, and return. | These studies inform narrative use. A claim about a narrative’s effects, assurance, ethical permissibility or policy authority requires grounds applicable to that claim. |
Albert Gatt and Emiel Krahmer, “Survey of the State of the Art in Natural Language Generation” (2018); Amal Alabdulkarim, Siyan Li, and Xiangyu Peng, “Automatic Story Generation: Challenges and Attempts” (2021); Rogelio E. Cardona-Rivera, Arnav Jhala, Julie Porteous, and R. Michael Young, “The Story So Far on Narrative Planning” (2024); Vikram Kumaran, Jonathan Rowe, Bradford Mott, and James Lester, “SceneCraft: Automating Interactive Narrative Scene Generation in Digital Games with Large Language Models” (2023), DOI 10.1609/aiide.v19i1.27504; Yuan Ma, Richard Susilo, Patrik Haslum, and Hanna Suominen, “Text-to-Text Automatic Story Generation: A Survey” (2026); Aynigar Rahman, Aihe Yu, and Kyungeun Cho, “Game Knowledge Management System: Schema-Governed LLM Pipeline for Executable Narrative Generation in RPGs” (2026) | Adopt content and narrative planning, grounding, controllability, schema constraints, repair, and evaluation limits for automated cases. | Grounds the generated event-graph case, generated-fluency boundary, source comparison, and conditional C.35 architecture-use exit. | The 2018/2021 surveys are historical anchors; the 2024/2026 planning, survey and schema-governed work supplies the later sources used here. |
Melanie C. Green and Timothy C. Brock, “The Role of Transportation in the Persuasiveness of Public Narratives” (2000); Michael F. Dahlstrom and Shirley S. Ho, “Ethical Considerations of Using Narrative to Communicate Science” (2012); Hanna Meretoja, “Narrative and Human Existence: Ontology, Epistemology, and Ethics” (2014, background only); FPF D.1 through D.5 | Adapt engagement as an effect with a bounded-use and ethical boundary. | Grounds the engagement check and the anti-pattern against treating engagement as evidence or permission. | Historical/background anchors. Current evidence, assurance, ethics, and policy claims still require their own sources and FPF patterns. |
A.6.3.NAR:12 - Relations
- Specializes:
A.6.3for structure-to-sequence narrative construction. The ordinary entry exposes selection, ordering, loss, use, and return; the triggered exact branch states same-EntityOfConcernn : X -> Yand any correspondence dependencies. - Coordinates with:
A.6.3.CRfor same-regime textual re-expression,A.6.3.RTwhen the receiving operation depends on a representation transition,A.6.3.CSCfor controlled semantic coarsening,A.6.4for changed EntityOfConcern, andE.17.EFPfor explanation-use adequacy. - Uses when current:
C.2.8for extractable structural amount, the applicable domain evaluation for its local scale,C.29for a mathematical estimate’s correspondence,C.33for captured and lost architecture-relevant structure, andC.34for a correspondence claim needed by architecture work. - Coordinates with:
A.22.CGUSfor its ordinary branch when continuation conditions need clarification. For a claimed source or narrative-ordering CGUS, establish that structure’s identity and membership; the optional unfolding block records references to that structure. - Coordinates with:
C.35for generated results entering architecture work,G.2for its SoTA harvesting/synthesis claims,E.6andE.11for learning order and first-entry publication questions, andE.17for publication-form use,E.17.0for viewpoint conformance,E.17.AUDfor audience, andE.24.PUBfor publication questions. - Uses when current:
G.11for source-return currentness;D.1–D.5,A.10, andB.3for the ethics, evidence, or assurance claims they define. - Uses when current:
F.19for plain language in technical narrative and for the plausible-reader test of an optional explanatory guard. - Boundary: NAR defines the structure-to-sequence construction, preservation, loss, and return boundary.