NSTD.8:5.7 - 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.

Source-spine item	Narrative or teaching move	Interleaving or spacing move
Pattern entry condition	Recognition story, contrast case, or failed-use story.	Return after two other pattern cases and ask for owner choice without a label.
Forces	Tension sequence, stakeholder conflict, or trade-off map.	Compare with a different pattern’s forces in a mixed exercise.
Solution move	Demonstration, guided reconstruction, or worked slice.	Reuse the same project case later with a different repair owner.
Boundary and non-use	Counterexample, wrong-owner case, or blocked overread.	Start a later session with a delayed boundary retrieval question.
Relations	Neighboring-pattern exit exercise.	Interleave adjacent exits so the learner must discriminate them.
Quality and improvement	Low-value row and repair exercise.	Revisit an old low-value row after new material and require a changed-slice repair.

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:

Route type	Source spine	Narrative devices allowed	Reconstruction evidence
FPF onboarding route	Pattern entry, EoC, forces, solution, relations, checks, improvement loop.	Practitioner story, failed-use contrast, recurring source-return prompt.	Learner selects correct owner and reconstructs one pattern-use route.
Mathematical explanation route	Definitions, examples, theorem prerequisites, proof-status boundaries.	Analogy, diagram story, dependency sequence, counterexample.	Learner marks where analogy stops and returns to formal statement.
Architecture explanation route	Candidate structures, characteristics, decisions, trade-offs, telemetry.	Trade-off story, viewpoint over stakeholder role, decision-memory path.	Learner separates architecture description, decision, realized structure, and telemetry.
Generated teaching route	Selected source relations and the intended learner operation.	Generated examples or slides inspected through `NSTD.7`, with `C.35` only for architecture use.	Learner tasks for the intended outcome; direct comparison with the sources where fidelity is claimed.
Live debrief route	Event record, provisional interpretation, official correction, source return.	Recap story, tension order, role viewpoint.	Learner distinguishes observation, inference, prediction, and official update.

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.