Glossary · 23 terms

Domain language

Source: CONTEXT.md. Updated with each grilling session that resolves new terms. Every term here has a precise definition — use the exact word, not the aliases column.

Core entities

6 terms

Cohort

avoid: classroom, class

A teacher's group of students moving through curriculum together.

Learning content

avoid: lesson (too narrow), material

A unit of curriculum stored markdown-native in learning_content.content_md.

Teacher

avoid: instructor, user (too generic)

The authenticated educator who owns cohorts and authors/curates content.

Student

avoid: pupil, user (too generic)

A learner within a cohort consuming content + the AI tutor.

Workspace

avoid: spike-workspace, session folder

The per-course git repo (Supabase-Storage-backed under V2) holding one Teacher's authoring state — intake, drafts, comments, gates, level summaries. Source of truth before publish.

Knowledge Base (KB)

avoid: knowledge graph, RAG corpus

Per-Teacher git repo following Karpathy's LLM Wiki pattern — raw sources, mutable wiki pages, schema file. Compounds across courses.

Build / pipeline

7 terms

Vertical slice

avoid: horizontal slice, layer

A thin cut through every layer a feature touches; one issue = one slice.

Wave

avoid: sprint, batch

A scheduled batch of ≤3 parallel slices landed together via wave:integrate.

Milestone (M1–M4)

avoid: phase (means something else)

Pipeline stages: M1 Course Outline · M2 Structure · M3 Unit Content · M4 Lessons & Assignments.

Gate

avoid: check (too generic)

A validator on a milestone/phase transition (crossing vs intra-alignment).

Pipeline tier (T0/T1/T2)

avoid: level, stage

KB-retrieval escalation tiers in the agentic pipeline.

Collapsed architecture

avoid: "V1" (ambiguous), pipeline-v2

The 8-agent system in library-course-generation.yaml (5 LLM + 3 KB agents) that V2 originally used as its migration baseline.

V1-original

avoid: "V1" (used to mean this)

The pre-collapsed 42-agent / 12-HITL system in library.yaml + docs/pipeline/overview.md. Already migrated to Collapsed; not V2's baseline.

V2 patterns (new 2026-05-27)

10 terms

Prompts-as-agents

avoid: agent classes, handlers

V2's architectural pattern: behavior lives in markdown prompts and product skills. Tool-using workers run through ToolLoopAgent sessions; invokeSubAgent remains the bounded structured-output path.

Pipelined-sequential dispatch

avoid: parallel fan-out, strict sequential

Within-parent sibling sub-agents dispatch in dependency order, threshold = APPROVED. Maximum human-time overlap, low token risk.

Parent-gated cascade

avoid: parent dispatch

A finalized parent artifact auto-triggers dispatch of its declared children's sub-agents.

APPROVED threshold

avoid: finalized trigger

Trigger state at which the next sequential sub-agent dispatches: teacher endorsed but not yet finalized.

Edit vs Review duality

avoid: (don't conflate these surfaces)

Edit = direct commit, no cascade. Review = markdown proposal record, explicit cascade after accepted apply.

Pure-workspace projection

avoid: hybrid projection, shadow rows

V2 invariant: all pre-publish state lives in workspace markdown + git; Supabase only holds published rows.

Quality report

avoid: semantic readiness report

Report-only Strategy, Structure, and Substance evidence used for teacher review and readiness surfaces.

LLM Wiki

avoid: RAG, embeddings-only

Karpathy's 2026-04 pattern: per-teacher KB repo with raw sources / wiki core / schema file + Ingest/Query/Lint/File-back verbs. V2's kb/ follows this exactly.

Targeted re-eval

avoid: cascade regen, downstream sweep

LLM-judge flow on finalize-after-edit; emits {verdict, reason, diff_proposal?} per affected child; proposals land on the same git branch as the upstream edit.

Per-sub-agent-completion commit

avoid: per-file commit, per-action commit

Git commit granularity in V2: each sub-agent's full output is one commit, authored as agent:<role>.

Back to design index