#Structure-to-Narrative Rendering

A.6.3.NAR · Stable · Specialization pattern · Normative unless explicitly marked informative · Part A - Kernel Architecture Cluster

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

Type: Specialization pattern Status: Stable Normativity: Normative unless explicitly marked informative

Use this pattern when selected source structure must become a sequential narrative rendering for a declared reader or listener use. 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 route, or an event graph turned into a generated story draft.

#Relations

#Content

#Problem frame

Use this pattern when selected source structure must become a sequential narrative rendering for a declared reader or listener use. 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 route, or an event graph turned into a generated story draft.

Primary EntityOfConcern: one A.6.3 epistemic-viewing relation in which a source-bearing episteme, publication, model, graph, architecture view, evidence set, or situation is rendered as a narrative path while the same EntityOfConcern is preserved or a declared correspondence is used.

Plain starting vocabulary:

First useful move: write one compact StructureToNarrativeRenderingCase@Context for the case. Name the source material, selected source structures, source-structure selection rationale, source temporal posture, route family, narrating or rendering worker, reader-interest or use hypothesis, receiving narrative rendering, intended reader or listener role and use, ordering rationale, preserved structure, foregrounded structure, coarsened or lost structure, recoverability, admissible use, non-admissible use, and source-return condition.

What goes wrong if missed: a useful story becomes a substitute for the source structure. Readers remember a sequence, example, protagonist, conflict, or conclusion, but cannot reconstruct the source relations that made the narrative worth using.

What this buys: the narrative can help human use without pretending to be neutral compression, proof, authority, ethics, evidence, architecture, or the source itself.

Ordinary use: for low-reliance teaching, orientation, or internal explanation, one compact case note near the narrative is enough. It must still state what the narrative preserves, what it leaves behind, and when to return to the source.

Reliance-facing use: use the full field spine when the narrative will guide architecture work, design decisions, policy communication, safety work, generated-output admission, external teaching, or cross-context reuse.

Not this pattern when the current change is only same-regime wording (A.6.3.CR), only representation-scheme transition (A.6.3.RT), only coarsened narrower-use rendering (A.6.3.CSC), explanation-use adequacy on an existing MVPK face (E.17.EFP), changed EntityOfConcern (A.6.4), carrier export or serialization, generated-output admission (C.35), evidence, assurance, ethics, publication, or work authorization. Use the direct owner first and return here only when the structure-to-sequence narrative relation is live.

#Problem

Projects often need narrative because 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 route before humans can follow it.

Without A.6.3.NAR:

1. narrative is treated as style polish after the real work is done;
2. narrative is treated as a lossy summary even when sequence-making is the main representational move;
3. source structure, order, event model, and lost relations disappear behind fluent prose;
4. engagement is allowed to raise confidence, authority, ethical permission, or policy force without a direct owner;
5. generated narrative output is trusted because it is coherent or dramatic;
6. teaching material can be smuggled into pattern bodies instead of being kept as a separate test-run publication carrier or ordinary publication carrier.

#Forces

#Solution

Create a StructureToNarrativeRenderingCase@Context for the narrative relation.

Use this compact form. Fill only fields that change the admissible use or block a likely overread.

StructureToNarrativeRenderingCase@Context:
  sourceMaterialRef:
  selectedSourceStructureRefs:
  sourceStructureSelectionRationale:
  sourceTemporalPosture:
  routeFamily: direct-source-structure | architecture-mediated | mixed
  architectureMediationRef?:
  sourceStructureOwnerRef?:
  narratingOrRenderingWorkerRef?:
  readerOrListenerRoleRefs:
  readerInterestOrUseHypothesis:
  preservedEntityOfConcernRef?:
  declaredCorrespondenceRef?:
  receivingNarrativeRenderingRef:
  intendedReaderOrListenerUse:
  orderingRationaleOrTraversalRule:
  preservedStructure:
  foregroundedStructure:
  coarsenedOrLostStructure:
  epiplexityOrStructuralInformationRef?:
  recoverabilityClassOrSourceReturnCondition:
  eventModelSupport?:
  engagementOrMotivationClaim?:
  admissibleUse:
  nonAdmissibleDownstreamUse:
  neighboringPatternExits:

Work in this order:

1. Name the source material, the source structure that must survive, and its temporal posture: retrospective or reverse-engineered actual, live unfolding, prospective planned, prospective fictional, or mixed.
2. State the source-structure selection rationale and the reader-interest or use hypothesis. If these are only implicit in a draft, treat the draft as a candidate carrier until the rationale is reconstructed.
3. Name the route family. Use direct-source-structure for a situation, event stream, proof field, canon, or source pack rendered directly; use architecture-mediated when architecture understanding, architecture description, architecture view, architecture viewpoint, decision record, candidate structure, or telemetry is the mediating source.
4. Name the narrating or rendering worker, the receiving narrative rendering, and the intended reader or listener role and use.
5. State whether the same EntityOfConcern is preserved or whether a [C.34](/generated/patterns/C.34) correspondence is needed.
6. Choose the ordering rationale: event order, causal order, discovery order, didactic order, tension order, graph traversal, architecture-decision route, live-commentary route, prospective-scenario route, source-publication order, or another declared rule.
7. State preserved structure, foregrounded structure, coarsened or lost structure, and recoverability.
8. If the live question is how much structure was pulled into the narrative, create or cite the structural-information or epiplexity note instead of answering with fluency. For architecture-relevant uses this routes to [C.33](/generated/patterns/C.33); for declared narrative-quality evaluation this routes to the domain narrative evaluation owner, [A.19.ECS](/generated/patterns/A.19.ECS), and [C.16](/generated/patterns/C.16) as applicable.
9. Add event-model support when the narrative asks the reader to understand events, actions, mechanisms, goals, obstacles, state updates, or change.
10. Add engagement or motivation only as a declared-use claim. If persuasion, harm, affected parties, policy influence, bias, value conflict, or ethical assurance is live, route the claim to [D.1](/generated/patterns/D.1) through [D.5](/generated/patterns/D.5), [A.10](/generated/patterns/A.10), or [B.3](/generated/patterns/B.3) as applicable.
11. Close with admissible use, non-admissible downstream use, source-return condition, and neighboring-pattern exits.

#Ordinary and claim-bearing cases

Ordinary narrative renderings can stay lightweight. An internal explanation, teaching example, or orientation story usually needs only a compact note: source material, selected structure, sequence rule, visible loss, and source return.

Claim-bearing cases need the fuller record. A case is claim-bearing when the narrative will be used for design, architecture, policy, safety, public science communication, generated-output admission, cross-context reuse, assurance-facing training, or a disputed interpretation.

#Same-entity and correspondence-mediated profiles

Use the same-entity profile when the receiving narrative is still a rendering of the same EntityOfConcern and the source tether remains visible.

Use the correspondence-mediated profile when the narrative is produced from a source model, graph, architecture view, or generated relation set that corresponds to the source but is not the same representation. In that case, create or cite the C.34 correspondence record before the narrative is treated as same enough for a downstream use.

#Direct and architecture-mediated routes

Use the direct source-structure route when the narrative worker renders a situation, event stream, domain model, proof dependency field, evidence set, fictional canon, or source pack directly into a narrative path. View and viewpoint discipline may still help, but the central owner is the NAR relation plus any domain owner, not the architecture line.

Direct does not mean implicit. If the selected source structures, selection rationale, reader-interest hypothesis, ordering rationale, and loss account are left inside the writer's intuition, an LLM prompt, or a finished story, the output is only a candidate carrier or candidate prose, not an admitted narrative rendering. It can inspire a later NAR case, but reliance-facing use requires reconstructing and checking the missing selection and loss record.

Use the architecture-mediated route when the source structure is actual or possible holon structure that has been understood through architecture work: reverse-engineering an existing holon, comparing candidate future structures, using architecture descriptions and views, applying architecture decisions, or checking telemetry after realization. In this route the return chain is narrative rendering -> architecture description or view -> architecture as selected structures in context -> wider holon or source structures. Each arrow can select, coarsen, abstract, omit, or order structure, and each arrow needs its own source-return condition when the loss becomes live. C.33, C.34, C.32.*, architecture-description owners, and architecture-decision owners remain live. NAR governs only the narrative rendering of that architecture-relevant structural information.

The temporal posture matters in both routes. A historical reconstruction, a live football broadcast, a prospective project narrative, and a fictional continuation may all be narratives, but they have different source-return, evidence, uncertainty, ordering, and non-admissible-use obligations.

#Ordering rationale

The ordering rationale is not decoration. It is the structure-to-sequence rule.

Common ordering rationales:

If the source 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.

#Event model, viewpoint, and agency

If the narrative asks readers to understand events, actions, mechanisms, or change, state the event-model support. At minimum, name the event or mechanism type, participating holons or agents when present, causal or dependency links, update points, and what the narrative asks the reader to predict or revise.

If viewpoint, narrator, focalized object, protagonist, or agency choices affect understanding, keep them in domain narrative vocabulary unless a direct FPF owner is live. In FPF Core, the reusable claim is simpler: the viewpoint choice foregrounds some source structure and hides or weakens another structure for a declared use.

#Engagement, ethics, and assurance boundary

Engagement is a real use claim, but it is not truth or permission.

When an engagement or motivation claim matters, state:

• intended effect for the declared use;
• source structure that may not be distorted for that effect;
• affected reader, listener, group, or decision context when relevant;
• non-admissible uses that would overread the narrative;
• owner for ethical, evidence, assurance, or policy claims.

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. Narrative engagement never grants moral permission by itself.

#Reopen, lower, and return rule

A NAR case stays admissible only while its source material, selected source structures, intended use, ordering rationale, source-return condition, and neighboring-owner exits still match the narrative rendering's use. When one of these changes, repair the smallest affected part of the case before relying on the narrative again. Do not turn NAR into a general monitor for all narrative science; this rule is local to the declared NAR case and its owner-routing obligations.

#Archetypal Grounding

Tell: A.6.3.NAR is the pattern for making an ordered narrative path from selected source structure while keeping the source relation inspectable. It is not a pattern for writing a better story in general.

#Scientific mechanism narrative

A chemistry paper has calculations, candidate mechanisms, failed synthesis attempts, and an unresolved tension between theory and experiment. The narrative uses discovery order: failed attempts, structural clue, revised mechanism, new experiment, remaining uncertainty.

The NAR case records source structures calculation set, mechanism candidates, experiment attempts, and unresolved tension. It records preserved structure candidate mechanism and failed-attempt relation, foregrounded structure discovery route, lost structure full calculation detail, and source return return to source calculations before using the narrative for mechanism proof.

This is not only conservative retextualization because ordering and tension carry the use. It is not proof because the narrative does not replace evidence.

#Architecture trade-off narrative

An architecture team explains why one candidate structure was selected. The source includes module structure, data custody, placement constraints, architecture characteristics, and rejected candidates.

The route is architecture-mediated and prospective when the team is still choosing a future structure; it is retrospective when the team is reverse-engineering why an existing holon has the structure it has. The narrative follows tension order: current pain, candidate split, characteristic trade-off, rejected alternatives, selected structure, remaining residual. The NAR case records what structure the story preserves and which hidden structures remain non-admissible for implementation decisions until the architecture description, decision record, or synthesis owner is reopened.

#Architecture narrative repair after source change

Later, one rejected candidate gains a new measurement basis and a placement constraint changes. The old narrative still tells a coherent tension story, but it no longer preserves the live candidate set. The repair is local: lower the old narrative to historical orientation, reopen the NAR case, replace the selected-source-structure refs and ordering rationale, and add a new source-return condition pointing to the updated architecture source.

The captured and lost structures move to C.33: old rejected-candidate relation preserved as history, new candidate-set relation captured, and obsolete measurement basis marked lost for current decision use. C.34 may carry only the weakened correspondence that remains between the old narrative and the updated source. Implementation or decision use stays non-admissible until the architecture description, decision record, or synthesis owner is repaired.

#Live unfolding event narrative

A commentator narrates a football match while the source event is still unfolding. The route is direct source-structure and live. The source structures include score state, possession changes, tactical shape, player roles, momentum, and uncertainty about what the next play means.

The NAR case records that the narrative can orient the listener during the event, but later analysis, statistics, rule disputes, injury reports, or official results require source return. Live commentary may use tension and prediction, but it cannot treat provisional interpretation as settled event evidence.

#FPF seminar-route boundary

A team tests whether a future seminar series can explain FPF. The narrative route may use A.6.3.NAR to declare how FPF source structures are ordered for learners: EntityOfConcern discipline, problem frames, pattern use, relation records, source return, framework authoring, and improvement loops.

The probe evaluates whether NAR supports an external seminar-route publication carrier for declared teaching use. It is not a narrative-rendering quality result, not evidence that FPF is correct, and not permission to place seminar outlines, slides, scripts, or exercises inside Core pattern bodies.

The actual seminar outline, slides, exercises, and script are not part of this pattern. They belong in a separate test-run publication carrier or teaching publication carrier. This pattern governs only the structure-to-sequence relation used by that carrier.

#Franchise-continuation storycraft probe boundary

A storycraft team tests whether a continuation-style narrative for a well-known space-opera franchise can preserve admitted source structures without becoming a fan-service list or an unauthorized publication plan. The source material is the admitted canon or local source pack. The selected source structures may include continuity constraints, premise, theme, character-agency treatment, causal plot structure, viewpoint, stakes, and source-return refs.

A.6.3.NAR governs only the structure-to-sequence relation: which source structures are ordered into the proposed narrative path, which are foregrounded, which are lost or deferred, and when the worker must return to the source pack. Storycraft vocabulary, canon classification, generation method, rights or publication permission, and full narrative-quality evaluation stay outside Core. Use G.2 for the canon or source-pack claim, domain narrative owners and direct FPF owners for agency, responsibility, and declared-use rendering-quality claims, C.35 when generated drafts are used, and publication or rights owners when publication is live.

#Homotopy-theory explanation probe boundary

A teacher turns a graph-heavy mathematical source into a sequential explanation of homotopy theory. The selected source structures may include definitions, dependency order, examples, counterexamples, theorem prerequisites, proof-status boundaries, and source return to formal statements. The narrative order may be didactic dependency order rather than historical discovery order or proof order.

A.6.3.NAR records the chosen sequence rule and visible loss: which mathematical structures remain reconstructible, which proof details or generalizations are deferred, and when the learner must return to formal source statements. It does not certify the mathematical proof, replace the formal text, or turn analogy recall into understanding. Use mathematical-lens, proof, source, evidence, publication, and teaching-evaluation owners when those claims are live.

#Automated event-graph narrative

An LLM or NLG system receives an event graph, agent goals, constraints, and a domain schema, then proposes a story scene.

NAR records the relation only after source admission and generation owners have done their work. The case names source plan, selected event relations, ordering rule, preserved event constraints, coarsened or hallucinated structure, and source return. Generated fluency does not make the narrative authoritative; generated-output admission remains with C.35, source-pack claims with G.2, and evidence or assurance with their direct owners.

#Bias-Annotation

#Conformance Checklist

#Common Anti-Patterns and How to Avoid Them

#Consequences

Positive consequences:

• Narrative becomes a reviewable representation relation rather than ungoverned prose.
• Readers can benefit from sequence, tension, viewpoint, and event support without losing source-return discipline.
• Generated and human-authored narratives receive the same source-structure checks before downstream use.
• FPF Core stays small while narrative-studies, narratology, NLG, pedagogy, and storycraft details can mature outside Core.

Costs and trade-offs:

• Authors must write a small relation note for reliance-facing narratives.
• Some attractive narratives will be downgraded to orientation-only use because source structure is not recoverable.
• Engagement claims can trigger ethics, evidence, or assurance owners, which may slow publication but prevents persuasion from becoming hidden authority.

#Rationale

Narrative is a powerful way to make structure usable by humans. It can order events, mechanisms, evidence, options, architecture decisions, and learning paths. That strength is also the risk: a well-formed narrative can make a source look simpler, more certain, more complete, or more ethically acceptable than it is.

The chosen Core pattern is therefore narrow. It does not make FPF a narratology, storycraft, teaching, or NLG framework. It adds one reusable relation under A.6.3: selected source structure is ordered into a sequential narrative rendering for declared use, while preservation, loss, admissibility, and source return remain visible.

#SoTA-Echoing

#Relations

• Specializes: A.6.3 as a same-EntityOfConcern or declared-correspondence epistemic-viewing relation.
• Coordinates with: A.6.3.CR for same-regime textual re-expression, A.6.3.RT for representation-scheme transition, A.6.3.CSC for controlled semantic coarsening, A.6.4 for changed EntityOfConcern, and E.17.EFP for explanation-use adequacy.
• Uses: C.33 when the narrative rendering is being used as architecture-relevant structural information and its captured and lost structure must be made explicit, the domain evaluation owner when the same question is non-architecture narrative epiplexity, and C.34 when source structure and narrative structure are treated as same enough for downstream use.
• Coordinates with: C.35 for generated or discovered carriers that may contain candidate narrative renderings, G.2 for source-pack claims, E.6 and E.11 for learning-order and first-entry publication questions, and E.17 or E.17.AUD for publication-face and audience-unit questions.
• Uses: G.11 when source-return currentness, freshness, telemetry, or source-pack decay is the live reason a NAR case must be refreshed before reuse.
• Routes to: D.1 through D.5, A.10, and B.3 when value frame, multilevel harm, conflict, decision use, bias, impact, evidence, or assurance becomes live.
• Boundary: NAR governs the structure-to-sequence narrative rendering relation. It does not publish the narrative, authorize reliance, prove the source, admit generated output, decide ethics, create a teaching script, or make a domain narrative vocabulary part of FPF Core.

#A.6.3.NAR:End

Last Updated: 2026-06-30 — this section last modified in upstream FPF commit 9087581a (github.com/ailev/FPF)