Atlas node · Learning / Systems · prototype / public-safe excerpt

Class Hub

Workshop-oriented learning infrastructure for educator-operated modules, classroom pacing, and privacy-forward teaching workflows.

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.

The source trail and stack diagram make the workflow legible while keeping deployment detail and classroom data out of public view.

The public claim is about privacy-forward teaching infrastructure, not institutional adoption or a universal LMS replacement.

What it is

Class Hub is a self-hosted learning doorway where access, pacing, links, assignments, and operational visibility stay in the hands of the educator or maintainer. Publicly, it should be read as a privacy-forward infrastructure prototype rather than as a generalized LMS replacement.

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: prototype / public-safe excerpt. Public source and diagrammatic evidence exist, but the page should stay cautious until redacted screenshots and a clearer public data-retention note are surfaced.

Next proof object: Redacted course-home screenshot paired with a short data-retention and access-control note.

Boundary note

This node is intentionally public-safe. It discusses architecture, workflow, and privacy posture without exposing classroom data, institutional details, or live deployment specifics.

What remains unresolved

  • The page should not imply institutional adoption, student outcomes, or broad deployment stability.
  • A redacted screenshot set would make the workflow claims easier to verify publicly.
  • The retention and deletion story should be surfaced more directly if this page grows.

Methods surfaced

  • 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

  • Project repo — Implementation truth.
  • Last reviewed: 2026-05-15

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.