Teaching scenarios
Teaching scenarios follow the published profile contract and hold unrelated inputs steady so one atmospheric relationship remains legible.
Why control the input
Section titled “Why control the input”| Need | What a controlled scenario provides |
|---|---|
| Compare two states | Change one quantity while holding the rest steady |
| Explain uncertainty | Show deterministic and ensemble shapes side by side |
| Demonstrate absence | Omit an unsupported capability instead of substituting zero |
| Test a renderer | Regenerate the same document and expect the same scene |
| Teach an edge case | Construct a rare but plausible pattern without waiting for it to occur |
Offline model output can calibrate plausible ranges. Figures consume the fixed, committed profile.
Keep the frame smaller than the lesson
Section titled “Keep the frame smaller than the lesson”A figure needs a clear relationship, a meaningful static frame, units, and an accessible description. Add a caption when method or limits change the reading. Add controls only when changing an input reveals something the static frame cannot.
The scenario generator and validation gates own committed documents. Prose and components consume those artifacts.