NSTD.8:5 - Archetypal Grounding

Worked learning route: FPF onboarding

This example sketches the route that a seminar, tutorial or exercise sequence could realize. The note is optional; the important relation is between each teaching move and the next learner action.

LearningNarrativeRoute@FPFOnboarding:
  learnerUse: new practitioner can apply one FPF pattern without treating it as a recipe
  sourceArchitectureRef: FPF pattern language and monolith and source pattern organization
  sourceSpineRefs:
    - `EntityOfConcern`
    - problem frame
    - forces
    - solution as condition-bound move
    - conformance and checking
    - neighboring exits
    - quality and improvement loop
  unfoldingStructureRefs: A.22.CGUS when the route teaches unfolding from source to next use
  demonstrativeSliceRefs: first pattern-use route through one selected project case
  learningRouteArchitectureRule: interleaved pattern-use route, not monolith-reference order
  learningStepOrder:
    - failed ordinary use
    - recover object of concern
    - read forces
    - choose solution move
    - check boundary and neighboring owner
    - repair one low-value result
  interleavingPlanRefs:
    - return to `EntityOfConcern` after forces, solution, and quality checks
    - mix adjacent owner-choice cases after each new pattern
    - revisit source-return boundary in examples from at least two domains
  spacingOrRetrievalScheduleRefs:
    - short delayed retrieval at the start of the next session
    - later mixed owner-choice task after intervening material
    - final transfer task with no block label
  reconstructionTasks:
    - name the source pattern section behind each story beat
    - choose the governing pattern for a new case
    - state one source-return condition
  engagementBoundaryRef: failure story is an archetype, not evidence
  evaluationRouteRef: `NSTD.6` learning-route rows
  improvementLoopInputRef: `E.23` when a comparison identifies a worthwhile improvement

In this onboarding route, the opening failed use may be preparation rather than a failed capability assessment. The subsequent recovery of the object of concern must work with the attempted alternatives: show which object the next move governs and why the tempting alternative does not answer that question. Before the later neighbor-choice task, inspect whether those neighboring entries and their distinguishing condition are already available. If not, introduce the contrast or provide an accessible source return; merely adding another unlabeled failure would not supply it. If the entries are available, the mixed case can test their selection instead of prompting the answer.

A concrete task in an introduction to FPF-based pattern use can use two neighboring NSTD methods already available in this publication. First make the distinction available: NSTD.2 changes presentation order while preserving needed relations; NSTD.3 examines the connection the account asserts. Then give the Readme’s incident log, whose causal investigation is still open, and its draft “the change caused the failure”. Ask: “Would moving the two logged events into chronological order settle this sentence? Which question must the repair answer?”

A supplied response in this design example is: “Put the change before the failure, so the cause is clear.” That response preserves chronology but still infers cause from order. If the distinction was unavailable, provide it and work through the two claims before another selection task. If this was a deliberate preparatory attempt, subsequent instruction should use that attempted answer to explain why chronology leaves the causal question open. If both entries were already available, return to the sentence and ask what the log establishes; then use a mixed case to check whether the learner selects a connection repair rather than an ordering repair. These continuations answer different difficulties.

A later diagram or recap should connect that choice to the next use. A wrong figure return calls for correcting the attachment, not automatically redesigning the entire course. After the repair, ask the reader to recover that relation and use it under the declared support. This is a worked design example with a supplied response, not an observation of a learner or a demonstrated learning gain.

A seminar file can add timing, facilitation notes and complete exercises. This pattern keeps the examples needed to explain route design without prescribing a complete seminar.

Worked learning route: repair topic-blocked practice

An engineering team wants a course on architecture patterns. Their first outline looks clean:

Lesson 1: all source-structure intake.
Lesson 2: all ordering rules.
Lesson 3: all viewpoint and agency.
Lesson 4: all engagement.
Lesson 5: all evaluation.

This outline gives learners the problem type inside each block. It may support first practice but leave later independent selection unpractised: a new failure may concern source selection, ordering, viewpoint, engagement, generation or the grounds for a claim.

Repair the route:

LearningNarrativeRoute@ArchitecturePatternCourse:
  learnerUse: engineer chooses and repairs the right pattern under mixed project situations
  sourceArchitectureRef: topic map and source pattern bodies
  sourceSpineRefs:
    - selected source structure
    - ordering rule
    - viewpoint and agency split
    - engagement boundary
    - narrative rendering quality row
    - source-return and owner routing
  learningRouteArchitectureRule: spaced interleaving around recurring project cases
  learningStepOrder:
    - one motivating project failure
    - source-selection repair
    - different project failure requiring ordering repair
    - return to first failure and add viewpoint risk
    - mixed owner-choice exercise
    - delayed retrieval of source-return boundaries
    - final transfer to an unseen case
  interleavingPlanRefs:
    - every session mixes at least one current pattern with one earlier pattern
    - adjacent failure modes are compared side by side
    - examples rotate across FPF seminar, architecture explanation, homotopy explanation, generated carrier, and live commentary
  spacingOrRetrievalScheduleRefs:
    - start each session with a no-label retrieval task from a prior session
    - return to `EntityOfConcern`, source-return, and owner-routing at increasing delays
    - require one late repair of an old low-value row after new material intervenes
  blockedTopicOverread: a clean topic block is not evidence of durable pattern choice
  evaluationRouteRef: `NSTD.6` rows for transfer, source return, and learner reconstruction

The repaired route still preserves the source architecture. It simply refuses to treat that architecture as the course order. The learner sees a pattern, uses it, leaves it, then returns under a different cue. That is the point: source modules can stay modular while the learning route deliberately crosses module boundaries.

Worked learning route: homotopy explanation

LearningNarrativeRoute@HomotopyIntro:
  learnerUse: learner distinguishes intuitive deformation picture from formal definition and proof boundary
  sourceSpineRefs:
    - topological space
    - path
    - homotopy relation under constraints
    - invariant
    - example and counterexample
    - proof-status return
  learningStepOrder:
    - image cue
    - constraint marker
    - formal definition return
    - example
    - counterexample
    - reconstruction task
  reconstructionTasks:
    - mark where analogy stops
    - state which deformations are not allowed
    - return one claim to formal source
  engagementBoundaryRef: vivid image cannot replace definition
  evaluationRouteRef: `NSTD.6` rows for ordering, language-state precision, and source return

If learners can retell the loop picture but cannot state the required constraint, repair the connection to the definition. A suitable example, counterexample or worked comparison may supply that repair.

Worked learning route: using this pattern language

A short course on this DPF may use the three probes: FPF seminar, franchise continuation, and homotopy explanation, with live commentary as a fourth transfer case. The route succeeds only if learners can see the same pattern set working across different domains:

The transfer question is the actual teaching test. Remembering case names is not learning. The learner must choose the live pattern and repair the failure in a new situation.

Before and after repair: teaching material inside pattern body

Before:

This pattern should include a full seminar script so readers can immediately teach narrativization.

Failure: a complete seminar script can obscure the reusable route method and its alternatives. A worked example that explains a particular operation remains useful inside the pattern.

After:

This pattern explains how to design the learning route, with worked examples of its operations. A complete seminar script, slide deck and session notes are separate teaching products. Their learner tasks and source returns can be evaluated through NSTD.6.

Evaluating the learning route

Select the outcome needed for the declared teaching use. Immediate reconstruction, delayed retrieval, discrimination among similar cases and transfer to a new case require different tasks and observations. Success at one does not establish the others. A one-off explanation may need only immediate reconstruction; a course promising durable independent use needs an appropriately delayed and varied task.

Use NSTD.6 with the observer, prior preparation, assistance and reading conditions stated. Keep an author’s walkthrough distinct from an observed learner result.

Connecting route design to publication and improvement

NSTD.8 uses E.11 for framework entry, E.17 for publication form, E.17.AUD for a separately usable audience unit, NSTD.5 for engagement and NSTD.6 for evaluation. E.22/E.23 support a selected improvement; G.11 addresses an applicable source or practice refresh. A one-off explanation and a maintained course need different amounts of recorded design.

An FPF learning route, such as a seminar series or tutorial sequence, teaches the framework across several steps. The source-structure spine includes EntityOfConcern discipline, relation precision, pattern bodies, DPF authoring, architecture synthesis, evaluation, improvement loops, and source-return discipline. The learning order is didactic, not proof of FPF architecture. Learner tasks ask participants to reconstruct one pattern-use route from source basis and selected source structure, not only repeat a story or slogan.

A homotopy mini-course may start with pictures and deformation stories. Its reconstruction task should reveal whether the learner can recover the required definitions and conditions. When an analogy conceals a constraint, a counterexample or comparison can show why the formal boundary matters.

A DPF onboarding route may teach narrative rendering through three cases: FPF seminar, franchise storycraft, and live commentary. The route is successful only if learners can reconstruct why all three open NSTD.1, why different patterns become live later, and why NSTD.6 evaluates a declared rendering version rather than a general story. The test is transfer across cases, not recall of the case names.

Use NSTD.7 to inspect a generated teaching draft against the source ideas and intended tasks. NSTD.6 can evaluate it before acceptance. Apply C.35 only when the generated result is being used for architecture work; producing a slide or example does not itself select that pattern.

Distinguish versions when comparing repeated teaching or maintaining materials. The following optional note is useful when the comparison needs these details.

LearningNarrativeRouteVersion@Context:
  routeRef:
  sourceSpineVersionRef:
  learnerRoleRef:
  learningStepOrderingRule:
  carrierRefs:
  reconstructionTaskRefs:
  evaluationResultRef:
  observedConfusionOrTelemetryRefs?:
  changedSliceSincePreviousVersion?:
  refreshCondition:

For a comparison, identify which material and order each group encountered and what changed. Re-evaluate the affected outcome before claiming improvement. An untracked slide change may still be useful, but cannot support a precise comparison of course versions. A relevant source change calls for reviewing the affected teaching content.

The following example plan connects subject content, the immediate teaching move and a later use. Adapt its timing and returns to the learner’s task.

The left column names the source ideas to recover; the middle names an immediate teaching move; the right shows a possible later return. Use the last column when delayed retrieval or mixed selection is part of the goal. Its presence alone does not establish learning, and its absence is not a defect in a route that does not need those outcomes.

Examples of different learning aims:

For a short one-off teaching note, the route can be tiny: one source-spine item, one ordering rule, one reconstruction question, one source-return link. For a repeated seminar or course, the route should have versioned carriers, task results, and low-value repairs. The size changes; the source-return discipline does not.

Do not use popularity as learning evidence. Attendance, satisfaction, applause, or “people liked the story” may be engagement telemetry, but it is not reconstruction evidence. Reconstruction evidence asks whether learners can rebuild the source relation, apply it to a new case, name a boundary, or choose a repair.