PaperLab Case Thread Continuity
When to Use
USE WHEN: chapters reuse the same field, facility, well, pipeline, process, or
economic case across theory, notebooks, exercises, and capstone studies.
Pair with:
paperlab-chapter-flow-editor for narrative transitions,
paperlab-book-knowledge-graph for case graph links,
paperlab-notebook-regression-baselines for computed case outputs.
Registry Fields
Track recurring case parameters with:
- case id and public display name,
- parameter name and unit,
- base value and uncertainty range,
- source or chapter of origin,
- scenario tag,
- intended teaching role,
- confidentiality status.
Drift Classes
| Class |
Meaning |
| intentional-scenario |
value changes because scenario changes |
| rounding |
harmless numerical rounding |
| stale-value |
old value remains after later update |
| naming-drift |
same object has multiple names |
| contradiction |
incompatible values without explanation |
Output Schema
{
"case_id": "ultima_thule",
"parameter": "export_pressure_bara",
"values": [
{"chapter": "ch26", "value": 120.0, "unit": "bara"},
{"chapter": "ch31", "value": 150.0, "unit": "bara"}
],
"classification": "intentional-scenario",
"required_note": "Explain that Chapter 31 evaluates the high-pressure export case."
}
Safety Rules
- Protect private case identifiers and document names.
- Do not collapse uncertainty ranges to one number.
- Do not erase scenario variation that supports teaching.
1---2name: paperlab-case-thread-continuity-23description: |4 Maintain consistency for recurring field, facility, and design cases across5 PaperLab books. Use when a book uses a repeated scenario as a teaching thread6 and assumptions must not drift silently.7metadata:8 source: https://skillmd.com/skills/equinor/paperlab-case-thread-continuity-29---1011# PaperLab Case Thread Continuity1213## When to Use1415USE WHEN: chapters reuse the same field, facility, well, pipeline, process, or16economic case across theory, notebooks, exercises, and capstone studies.1718Pair with:1920- `paperlab-chapter-flow-editor` for narrative transitions,21- `paperlab-book-knowledge-graph` for case graph links,22- `paperlab-notebook-regression-baselines` for computed case outputs.2324## Registry Fields2526Track recurring case parameters with:2728- case id and public display name,29- parameter name and unit,30- base value and uncertainty range,31- source or chapter of origin,32- scenario tag,33- intended teaching role,34- confidentiality status.3536## Drift Classes3738| Class | Meaning |39|-------|---------|40| intentional-scenario | value changes because scenario changes |41| rounding | harmless numerical rounding |42| stale-value | old value remains after later update |43| naming-drift | same object has multiple names |44| contradiction | incompatible values without explanation |4546## Output Schema4748```json49{50 "case_id": "ultima_thule",51 "parameter": "export_pressure_bara",52 "values": [53 {"chapter": "ch26", "value": 120.0, "unit": "bara"},54 {"chapter": "ch31", "value": 150.0, "unit": "bara"}55 ],56 "classification": "intentional-scenario",57 "required_note": "Explain that Chapter 31 evaluates the high-pressure export case."58}59```6061## Safety Rules6263- Protect private case identifiers and document names.64- Do not collapse uncertainty ranges to one number.65- Do not erase scenario variation that supports teaching.