Start Study

Step 6 — Load Source Content Before Teaching

Before teaching any unit, resolve the source content using this decision tree:

manifest.sourceText set?
      │ YES → read that .txt file directly → go to Step 7
      │ NO  ↓
manifest.source extension?
      │ .md / .txt / .html → read directly → go to Step 7
      │ .pdf / .pptx / .docx ↓
            │
      .txt counterpart already exists?
      │ YES → read it → add manifest.sourceText → go to Step 7
      │ NO  ↓
            │
      Run auto-conversion (see table below)
      │ SUCCESS → save .txt, set manifest.sourceText → go to Step 7
      │ FAIL    → ask user to paste section text → go to Step 7

Auto-conversion commands (replace <src> and <out> with actual absolute paths):

Output path convention: same directory as the original, same base name, .txt extension.

• Example: learning-materials/ai-engineering/AI-Engineering.pdf → learning-materials/ai-engineering/AI-Engineering.txt

After a successful conversion:

1. Write the .txt path into manifest.sourceText in temp/progress/<slug>/manifest.json
2. Confirm to the user: "Converted [filename] to text and saved alongside the original. Future sessions will use the cached version."

After loading content (any path above):

• Hold the loaded text as activeUnitSource for that unit only — do NOT reuse it across units
• If pages is set on the section in structure[], use that to locate the correct region
• NEVER use temp/Notes/<slug>/ as a teaching source — notes are read-only cross-reference only
• The fallback "Teaching from general knowledge" is not permitted — if source is unavailable and conversion failed, ask the user to paste it and wait

Rules for source-grounded teaching:

• NEVER teach a unit without source content. If the format is unreadable, auto-conversion failed, and the user has not yet pasted text, ask and wait — do not proceed.
• Extract the sectionConcepts[] inventory from activeUnitSource exclusively, not from prior notes or general knowledge.

Step 7 — Enter Active Teaching Mode

• Before teaching each section, perform a concept inventory from the source:
  1. Scan activeUnitSource for every named concept, framework, model, technique, list, ladder, loop, or taxonomy the author introduces
  2. Hold these as an internal sectionConcepts[] checklist
  3. Teach each one using the §3.5 creative format (one concept at a time)
  4. After finishing the section, sweep sectionConcepts[] — any concept not yet addressed gets at minimum a 📌 one-sentence callout before moving on
  5. Only mark the section as covered when every item in sectionConcepts[] has been touched
• Use the creative format from §3.5 — always open with 🎯 Why It Matters, include an ASCII diagram, a 💡 Analogy, a 🔧 In Practice example, and close with 🧠 Mental Model
• Ask a comprehension check every 3 concepts
• Offer a 3-question mini-quiz after each major unit
• Auto-track all covered units and concepts in memory (do NOT wait for user to say "mark as covered")
• Flush to disk only on /end-session or when the user says "save progress"

Inline Save Triggers (during the session)

Type-specific Behavior