NSTD.1:5 - Archetypal Grounding

NSTD.1:5.1 - Worked slice: FPF seminar from source spine to narrative route

A seminar author receives the request: “Tell a motivating story about FPF so people want to use it.” To turn that aim into a lesson, the author chooses what learners should be able to do: recognize a situation, select a suitable pattern and apply its conditions. The following record shares those choices with another teacher; a sole author could develop them in the draft itself.

NarrativePurposeIntake@FPFSeminarOrientation:
  sourceBasisRefs: selected FPF pattern bodies and relation records
  selectedSourceStructureRefs:
    - EntityOfConcern discipline
    - Problem frame and forces
    - Solution as admissible move under conditions
    - neighboring-pattern exits
    - quality and improvement loop entry
  sourceStructureSelectionRationale: new practitioners fail when they treat patterns as recipes rather than condition-bound moves
  sourceTemporalPosture: prospective planned learning route over current FPF source corpus
  renderingMediationMode: direct-source-structure
  renderingContribution: seminar author
  intendedReaderOrListener: new FPF practitioner; team lead evaluating local adoption
  readerInterestOrUseHypothesis: reader wants a first usable route through FPF without learning every pattern first
  intendedReaderOrListenerUse: reconstruct one pattern-use route and choose the next governing pattern
  narrativePurpose: orient attention and motivation toward source-returnable pattern use
  likelyMisreading?: not proof that FPF is correct; not replacement for pattern bodies; not authority for a local project
  sourceReturn: selected FPF pattern body and relation record
  additionalClaimQuestion: none unless the seminar makes assurance, policy, or affected-party claims
  refreshCondition: FPF edition or selected-source pattern changes; learner reconstruction test fails

The record above makes the choices available to another teacher; the writer can develop them while composing. The first paragraph may be memorable, but every memorable move has a source return. “A pattern is not a recipe” returns to source conditions, forces, and neighboring exits. “Start with the thing being changed” returns to EntityOfConcern. “Do not optimize the visible proxy indicator” returns to quality and proxy-risk owners. The seminar publication carrier can be engaging, but the intake prevents it from becoming a local mythology about FPF.

Evaluation through NSTD.6 later asks whether learners can rebuild the route: identify the source structure, say why the selected order was didactic, name what the story intentionally omitted, and return to the pattern body when they need authority. If learners only repeat the slogan “patterns are not recipes”, NSTD.1 did not select enough source structure for the declared use.

If an LLM produces a seminar draft, the intake keeps three positions separate:

renderingContribution: course-author or generator-operator role; recover the actual system, role assignment, and Work separately when those claims are made
narrativeVoiceOrViewpoint: teacher-facing explanatory voice under NSTD.4
generatedDraftInspectionRef: the NSTD.7 case that identifies the generated draft, source comparison and acceptance for its intended use; C.35 applies only when the result informs architecture work

One person may operate the tool, choose the voice and decide how to use the result. The output still needs comparison with the selected material; authorship alone does not establish its fidelity.

NSTD.1:5.2 - Worked slice: architecture-mediated narrative

An architect wants a narrative explaining a system’s future structure after candidate synthesis. Do not start with “tell the journey from chaos to architecture”. Start by deciding whether the narrative is architecture-mediated. If it is, architecture work remains live before narrative work.

NarrativePurposeIntake@ArchitectureDecisionStory:
  sourceBasisRefs: architecture candidate set, selected architecture description, decision record, expected characteristics, known residuals
  selectedSourceStructureRefs:
    - problem situation and forces
    - candidate structures considered
    - selected structure and rejected alternatives
    - expected architecture characteristics
    - residual exceptions and developer continuation boundary
    - telemetry or later actual-structure feedback condition
  sourceTemporalPosture: prospective future holon structure before implementation
  renderingMediationMode: architecture-mediated
  architectureMediationRef: architecture description and candidate synthesis records
  intendedReaderOrListener: developer team; product steward; later evaluator
  intendedReaderOrListenerUse: understand what structure to preserve while implementing and what may be locally detailed
  narrativePurpose: carry structural intent and trade-off rationale into development work
  likelyMisreading?: not the architecture itself; not implementation order; not assurance that realized structure will match
  sourceReturn: architecture description, architecture decision record, and future telemetry route
  refreshCondition: candidate set, selected architecture, decision, or actual-structure feedback changes

This case teaches the architecture bridge. The narrative worker is not exempt from architecture owners just because the output is prose. C.2.8 is live for the amount of structure this reader can extract, applied through NSTD.6; C.33 is live for architecture-description adequacy; C.34 is live if correspondence between described and realized structure matters; E.17 is live if the carrier is published; architecture decision owners remain live for decision authority. NSTD.1 only binds the narrative purpose to selected structures and reader use.

NSTD.1:5.3 - Worked slice: franchise continuation probe

For a continuation-style storycraft probe using a well-known space-opera franchise such as Star Wars, select the canon, premise and continuity constraints relevant to the proposed scene. A draft can help reveal which of those choices remain unclear. In this example the use is a private critique; a later publication would raise separate rights questions.

The request “Write a surprising sequel that feels epic” leaves those choices open. For the private critique, the writer chooses a continuation premise that preserves a character’s established motivation and the consequences of earlier events. A new event may extend the story; if it conflicts with the chosen continuity, revise the event or explain the changed premise. Ordering and suspense alone cannot repair that conflict.

NSTD.1:5.4 - Role-specific first moves

NSTD.1:5.5 - What this pattern teaches about FPF

NSTD.1 is often the first place where a narrative worker learns why FPF separates selected source material, description, evidence, assurance, ethics, publication, and improvement. A desired effect does not determine what the source supports. The writer chooses a purpose and checks that the selected source relations can support the intended account. This comparison can remain a short explanation; it need not become a formal intake.

An FPF seminar route wants learners to understand why pattern use is condition-based rather than recipe following. The selected source structures are EntityOfConcern, problem frame, forces, solution, consequences, and neighboring-pattern exits. The purpose is orientation for later reconstruction tasks. It is not permission to replace pattern bodies with seminar slogans. Source return points to the FPF patterns and the seminar publication carrier stays outside this DPF body.

A homotopy explanation starts differently. The selected source material is a mathematical corpus: definitions, examples, maps, equivalences, proof-status boundaries, and formal sources. The intended reader is not “any curious person”; it might be an undergraduate who must later distinguish intuitive pictures from formal definitions. The purpose can be “make paths, deformations, and invariants followable”, but the blocked overread says that the narrative does not prove the theorem, replace formal notation, or license analogy as definition. The intake therefore protects formal return before any metaphor is selected.

A live football commentary has a live unfolding source posture. The commentator’s purpose may be orientation and suspense, but the selected structures are event order, score state, possession changes, player actions, provisional interpretation, and later official source return. The intake blocks the overread that a dramatic prediction, blame cue, or emotional framing is evidence. If later official statistics contradict the live interpretation, the refresh condition is not optional.

A franchise-continuation storycraft test uses a prospective fictional source posture. The source structures are selected canon constraints, continuity requirements, premise constraints, character-agency constraints, and non-publication boundary. The purpose may be private storycraft testing, not authorized sequel publication. The private critique establishes no publication rights; consider those separately if the intended use changes.