NSTD.Reference:9 - Architecture and narrative work bridge
Architecture and narrative work both involve selecting and relating structures, but their results differ. The table identifies useful correspondences and the conditions under which an architecture method applies. A plot, synopsis or teaching route is not thereby an architecture description.
| Architecture question | Comparable narrative question | When the FPF contribution applies |
|---|---|---|
architecture-relevant problem pressure in C.32.P2S | narrative problem, communicative pressure, audience confusion, motivation gap, future-scenario need, story problem | Use NSTD.1 to name reader or listener use and source-structure selection rationale; use C.32.P2S only when the pressure is genuinely about holon architecture carry-through. |
| Which structure matters, and what is still unknown? | Which story-world constraint, event connection, mechanism or proof dependency does this account need? | State the relevant relations directly; use A.22 when a structural description is needed and C.30 only for architecture description. |
architecture structural view and viewpoint in C.30.ASV | focalization, narrative viewpoint, perspective, lens, whose path through the material, what the reader is allowed to see | Use NSTD.4 for voice or focalization wording; cite C.30.ASV when the viewpoint is over architecture-relevant selected structures. |
architecture description in C.30.AD | synopsis, outline, story bible, explanatory account, learning route, narrative-rendering publication carrier | Use A.6.3.NAR for structure-to-sequence rendering and E.17 for publication; use C.30.AD only when the source or target is an architecture description. |
candidate structure set and trade-off in C.32 | alternative plots, possible story plans, scenario branches, competing explanation routes, narrative design alternatives | Keep alternatives visible before picking the route; use NSTD.2 for ordering and NSTD.6 for declared-use quality. Use C.32 only for architecture candidate synthesis. |
Project architecture decision in C.32.PAD | Choosing a narrative route, plot, order or viewpoint | Use NSTD.2, NSTD.4 or NSTD.5 for the editorial choice. Use C.32.PAD when the choice actually concerns the architecture of the system being described. |
| Participants who use an architecture result | Writer, teacher, commentator, story designer or assisting agent | Identify the contribution needed for the narrative. Use A.2, A.13 or A.15.1 only for the corresponding system-role, agency or actual Work claim. |
reader-relative structural amount in C.2.8, architecture-description adequacy in C.33, and narrative source return in NSTD.6 | what selected relations this reader can extract from the narrative, what remains missing, and when the source or an architecture description must be consulted | Use NSTD.6 for NarrativeRenderingEpiplexity under C.2.8 and for the separate source-return judgement. Use C.33 for the architecture-description adequacy question. |
| Preserving a specified architectural relation through a change | Preserving canon, continuity or a selected explanatory relation through retelling | Compare ordinary narrative constraints directly. Use C.34 for an architectural preservation claim, including the losses and permitted use that claim needs. |
realized structure, operation, telemetry, feedback in C.32.P2S and G.11 | reader reception, learner reconstruction, field test, replay, audience misunderstanding, generated-output repair, official result after live commentary | Use NSTD.6, NSTD.8, E.23, and G.11 for evaluation, improvement, and refresh. Use architecture feedback owners only when actual holon structure or architecture-characteristic results are being checked. |
The comparison suggests possible training transfers, not an established transfer effect. An architect learning narrative work can practise presentation order, viewpoint and reader response while using familiar structural distinctions. A narrator learning architecture work must additionally learn how to identify the relevant real structures, compare design alternatives and check their consequences. Competence in one practice does not establish competence in the other.