Atlas node · Learning · curriculum archive

Syllabus

Curriculum archive tying course families, shared policies, prompts, and teaching infrastructure into one public repository.

Repository →

What teaching leaves reusable

Syllabus treats curriculum as accumulated practice instead of disposable paperwork. Prompts, policies, pathways, and course language become materials that can be revised, carried, and questioned.

A course disappears quickly when its structure lives only inside a semester. The archive keeps teaching from restarting at zero while still making room for each workshop, class, and cohort to change the path.

The public repository already shows the archive and pathway logic. A redacted lesson trace would make the movement from archive to live teaching more visible.

The page should claim structure and transfer, not student outcomes or institutional adoption without public evidence.

What it is

Syllabus is the archive and pathway layer for courses, policies, prompts, and teaching structures. It matters publicly because it shows how classroom language and delivery practices stay cumulative instead of restarting from zero.

What it lets people do

It lets teaching structures travel across courses, workshops, and related systems while keeping policy, prompt, and pathway logic inspectable.

What is public now

  • Project repo Current public source for curriculum organization and shared teaching language.
  • Source evidence already surfaced README- and pathway-level evidence already support careful archive claims.

Evidence status

Status: curriculum archive. The repo already supports the archive and pathway framing, but the public page still needs one redacted curriculum-to-workshop trace before stronger reuse language belongs here.

Next proof object: One redacted pathway or lesson trace that clearly connects the archive to a workshop, course module, or delivery system.

What remains unresolved

  • The page should not imply student outcomes or institutional adoption without public evidence.
  • A stronger visible bridge to Class Hub or a public workshop artifact would clarify how the archive moves outward.

Methods surfaced

Proof objects

  • Project repo documentation Status: public. README- and pathway-level evidence already support careful curriculum-archive claims.
  • Redacted pathway or lesson trace Status: needed. Still needed before the page should imply stronger reuse beyond the archive structure itself.
  • Class Hub A delivery doorway for the courses, prompts, and policies housed here.
  • machine-docs A neighboring documentation framework for keeping teaching artifacts legible.
  • Human-Buffer One of the clearest examples of how these policies and teaching methods become runnable systems.

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 Class Hub — See the delivery system that can turn archived curriculum into a usable doorway.
  • Open machine-docs — See the documentation layer that shares the same transfer logic.