The Cases and Storyboard lane is the public doorway into the Laboratory Campus case-study material. It connects the local LabTalk / DotTalk++ systems storyboard deck, reviewed career/source-memory stories, database-history lessons, and proof-backed classroom labs.
This lane should be easy to find because it explains why the campus exists: database systems are not only commands and formats. They are stories about records, people, operations, mistakes, evidence, recovery, and learning.
Source Deck
The current source teaching artifact is the LabTalk / DotTalk++ Systems Storyboard Deck, maintained as a private/local source artifact rather than a public download.
The hosted site summarizes the deck instead of bundling the large PPTX into the public website source. The deck remains a local/source artifact that can feed classroom material, SelfDoc catalog work, generated manuals, and reviewed website summaries.
What It Covers
The storyboard currently connects these case families:
| Case Family | Learning Role |
|---|---|
| Punch cards, records, and batch processing | Shows why layout, order, correction, and validation mattered before interactive screens. |
| COBOL and business reports | Shows records, fields, reports, and repeatable institutional workflows. |
| JUMPS and mainframe-scale consequences | Shows that database errors can affect real people, pay, status, and audit trails. |
| CODASYL and owner-member relationships | Shows operational relationships before relational SQL became dominant. |
| xBase, dBASE, Clipper, FoxPro, and Visual FoxPro | Shows accessible application building from tables, indexes, screens, and reports. |
| Earthkids to CAREPAX | Shows practical local application work, market fit, receivables, scheduling, and lessons learned. |
| Document imaging, ERP, auto-ID, and process data | Shows transactions connecting documents, inventory, shipping, invoicing, and industrial operations. |
| DotTalk++ and the AI-era campus | Shows why transparent, inspectable database systems still matter when AI enters the workflow. |
Proof-Aware Case Pattern
Campus cases should not be loose anecdotes. They should move through the same proof-aware path as other Laboratory Campus material:
source memory -> reviewed case note -> dataset or simulation -> command/UI demo -> proof artifact -> lesson
That separation matters. Some cases can be tied to live runtime proof. Some are reviewed history. Some are source memory. Some need simulation because the original software, hardware, or data cannot be published.
Where To Go Next
- Database Evolution Path - detailed public sequence from punch cards and COBOL through cloud computing and AI.
- Lesson Platform - how cases become student and career lessons.
- Career Lessons - lessons learned while building and recovering data systems.
- Runtime Evidence Gallery - reviewed screenshots and proof artifacts.
- Suggest a Lesson - structured intake for case ideas, datasets, and lessons.
Current Status
This lane is active Laboratory Campus alpha material. It is intentionally visible because it gives context to the technical work, but it should remain honest about proof level: public pages should separate reviewed fact, local source memory, simulation, runtime evidence, and planned classroom material.