architecture

Summary

How the Learning Platform is built, in four small diagrams and one overview, opened from the architecture chip in the bar.

Raw wireframes

• .context/designs/web/architecture/<overview|who-uses|how-it-works|backend|relies-on>.html — the screens
• .context/designs/architecture/<name>.json — each diagram's source; <name>.html is drawn from it by Archify

Why it is drawn this way

• One question per diagram: who uses it, how the website is built, what the server does, what it relies on.
• The server diagram shows the repo clones beside Postgres because lesson content is never stored in the database (course-as-code).
• The Postgres host is drawn as "Supabase or Neon": the runbooks name both and the repo does not say which holds production.
• The diagrams are generated assets: edit the .json, then run archify finalize architecture <name>.json <name>.html --quality showcase inside designs/architecture/.
• The overview is architecture and cost only: the stack with versions and the monthly cost. Why each choice was made is in CLAUDE.md and 2026-05-01-host-on-vercel.

Related

• course-as-code · 2026-05-01-host-on-vercel

Sources

• CLAUDE.md, package.json files, .claude/rules/50-content-model.md, .context/ops/runbooks/deployment.md