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. |