The Laboratory Campus is intended to support non-profit, educational, and community learning use without blurring the line between learning material and core engine behavior. LabTalk remains the license/project mark for this area.
Suggested Onboarding
- Start with Getting Started.
- Read the Laboratory Campus Overview.
- Use DotTalk++ for command and script literacy.
- Use the Talk-family pages to learn tuples, tables, relations, and display concepts.
- Work through one small lab before expanding to larger datasets.
- Review the concise project notice.
Best Practices
- Keep sample datasets small and inspectable.
- Use scripts to make lessons repeatable.
- Label historical simulations as simulations.
- Keep proof transcripts separate from lesson prose.
- Do not treat curriculum incubator material as runtime truth until it is reviewed.
- Prefer read-only labs for first exposure.
Campus Roles
| Role | What The Campus Provides |
|---|---|
| Learner | Guided labs, small datasets, visible runtime behavior. |
| Instructor | Repeatable scripts, case paths, evidence labels, and lesson structure. |
| Maintainer | Registries, proof status, and boundaries between engine and education layer. |
| Non-profit program | A coherent learning-lab frame for database literacy and systems thinking. |
Proof Rule
Student-facing claims should be backed by one of:
- current source
- runtime transcript
- HELP/CMDHELP output
- CMDHELPCHK or SelfDoc validation
- reviewed case material
- an explicit simulation label