These examples show how the Laboratory Campus presents x64base and DotTalk++ as a collaborative learning environment. Each example should identify the concept, app, dataset, command path, proof state, and lesson goal.
Database Literacy Starter
Purpose:
Teach tables, records, fields, order, search, scan, and output.
Campus path:
HELP /ED MODEL
-> HELP /ED TABLE_RECORD_FIELD
-> HELP /ED INDEX
-> HELP /ED SCAN
-> DotTalk++ runtime transcript
-> student-facing lesson
EDREF is the name of the instructional help catalog (include/edref.hpp),
not a command. Until 2026-09-03 this path told a student to type it; the shell
answers Unknown command. HELP /ED <topic> is the real route and is what the
guided lesson already uses.
The first local campus portal slice already uses this path to run a read-only DotTalk++ script and capture a proof transcript.
Comments to Contracts to HELP
Purpose:
Show how source comments become structured contracts, HELP output, and validation evidence.
Campus path:
source comment
-> @dottalk.usage v1
-> comments evidence
-> CMDHELP artifact
-> CMDHELPCHK validation
-> campus lesson
This is the Self-Documenting Systems Lab.
Historical Data Systems Trail
Purpose:
Connect database history to live or simulated system behavior.
Campus path:
Punch cards / fixed records
-> COBOL / business reports
-> CODASYL / network traversal
-> xBase / DBF records and indexes
-> SQL / ERP / industrial data
-> cloud computing / distributed services
-> AI-era explainability
The Database Evolution Path is the first public version of this trail. It uses the LabTalk / DotTalk++ storyboard deck to connect punch cards, COBOL, ARPANET, JUMPS, CODASYL, xBase, ERP, cloud computing, and AI literacy.
Historical cases should separate reviewed facts, source memories, simulations, and runtime proof.