Atlas node · Learning / Systems · workshop prototype / staged proof

Class Hub

Educator-operated learning infrastructure for workshop pacing, student-facing modules, and inspectable data boundaries.

Repository →

What a class doorway can protect

Class Hub treats teaching infrastructure as a doorway with obligations. It gathers pacing, links, assignments, and access without asking the classroom to disappear into a platform it cannot inspect.

A learning system shapes attention before any lesson begins. The question is who can see the structure, who can repair it, and what student or workshop data is asked to travel farther than it needs to.

Staged teacher, student, and data-lifespan screens now make the workflow visible with synthetic records, while source-level preflight and review gates keep deployment and publication claims inspectable.

The public claim is about a privacy-conscious workshop prototype, not live deployment, formal compliance, student outcomes, reviewed translations, or a universal LMS replacement.

What it is

Class Hub is a self-hosted workshop LMS prototype where access, pacing, links, assignments, support signals, and data-lifespan controls stay visible to the educator or maintainer.

What it lets people do

It lets teachers assemble course-facing modules and workflows without surrendering the whole teaching environment to opaque platform defaults.

What is public now

Evidence status

Status: workshop prototype / staged proof. Public-safe teacher, learner, and data-lifespan screenshots support claims about workshop pacing, educator control, student-facing simplicity, and inspectable data boundaries. They do not establish live deployment, formal compliance, classroom outcomes, reviewed translations, or full-season reliability.

Next proof object: A deployment or restore receipt, only if operational reliability becomes part of the public claim.

Boundary note

Every screenshot below was staged locally with synthetic records. No real student identities, submissions, classroom records, institution details, or live deployment information are included.

What remains unresolved

  • The page should not imply institutional adoption, student outcomes, formal compliance, or broad deployment stability.
  • The screenshots prove staged interface behavior, not live classroom use.
  • Safeguarding language and substantive translations remain subject to qualified human review.

Methods surfaced

Staged Class Hub teacher portal showing day-of-class summaries, closeout actions, and four synthetic class cards.
Teacher day-of-class dashboard Shows educator-facing pacing, support, and closeout surfaces; all classes, accounts, and codes are synthetic.
Staged Class Hub student page showing one highlighted Scratch lesson, quick check-in choices, session links, upload access, and account controls.
Student standard view Shows a learner-facing module path, help signals, and self-service data controls using synthetic records.
Staged Class Hub data lifespan dashboard showing retention status, seven-day trends, export links, and a local curriculum-only index boundary.
Data lifespan dashboard Shows an operator-facing retention and export surface; zero-row values are staged evidence, not production metrics.
  • Syllabus A curriculum/archive companion that supplies prompts, policies, and teaching lineage.
  • seedBox Shows what portable kits look like when they need a practical course doorway.
  • repair-studio Keeps the maintenance and care side of self-hosted teaching systems visible.

Source trail

The Atlas is the relationship layer. Use the repository for current project-specific truth, and use studio-notes when methods, decisions, or teaching material need to travel across the fleet.

Where to go next

  • Open Syllabus — See the archive layer that can feed this delivery system.
  • Open machine-docs — See the documentation culture that keeps this kind of system maintainable.