Teach-back sessions

In a session you explain a confirmed concept without notes. Kizuki plays a curious student: it asks about what does not match your material, what you left out, and vague words you used. Every question about the material quotes it.

The steps

1. On a concept's page you write your explanation. startSessionAction calls startSession, which refuses a concept you have not confirmed and an empty explanation, and records session.started.
2. The teachSession workflow starts. For up to MAX_ROUNDS rounds it chooses questions (runRound) and pauses for your answers (recordAnswers). It stops early when a round has no questions, or when you press "Send and finish".
3. Kizuki proposes what you may have missed (proposeMisses) and pauses until you tick the ones you missed.
4. endSession ends the session. It is clean only if you confirmed no misses and never answered "the material is right" to a "Does this fit?" question. Clean or not decides the next review date (see Spaced review).

The session page shows where the session is with SessionStatus: thinking, answering, reviewing, ended, or failed. While Kizuki is thinking, the page reloads itself. If a session stays in thinking for more than two minutes, the page offers "Restart it", which starts a new run that skips finished steps. On the concept page, "Stop it and start over" marks an open session as stopped.

What the model sees

For each round, Kizuki gathers:

• the passages the concept was confirmed with, then passages that search finds for your explanation and answers, up to MAX_SESSION_PASSAGES (Passages and sentences);
• every sentence of those passages, labeled S1, S2, and so on;
• under each passage, your corrections ("Your correction: “…” should be “…”") and your answers to "what does this mean?" questions;
• what you wrote so far, and the questions already asked.

TEACH_SYSTEM tells the model to compare the details you wrote with the material first (places, numbers, names, directions, causes, and results), then look for missing ideas, then vague words, and to ask at most MAX_QUESTIONS questions.

The three kinds of question

The model replies in the shape teachReplySchema: for each question a kind, a sentence label, and words copied from what you wrote. It never writes the question. renderQuestion writes it from a fixed template:

validateTeachReply is the guard. A contradiction or gap question survives only if its label points at a real sentence that passes the quote check. An unclear question survives only if its words appear word for word in your own explanation and answers, in at most 6 words. An unclear question that points at a sentence but not at your words becomes a gap question. It drops questions that repeat an earlier one and questions that quote text you corrected, and keeps at most MAX_QUESTIONS. The page says how many questions were dropped.

If search found nothing for what you wrote and no question survived, the round says "Not in your material" and Kizuki asks nothing. With no passages at all, askQuestions returns that answer without asking the model.

Your answers

For each question you can write an answer. A "Does this fit?" question also needs one of three choices:

• The material is right. I got this wrong. Counts as a miss, so the session is not clean.
• The material is wrong. You write the correct version, and it becomes a correction that wins from then on. See When you and the material disagree.
• Neither: Kizuki misread what I wrote. No miss and no correction.

What you missed

askMisses builds the list in two parts, using only the concept's own passages, so points from other topics never appear:

1. Plain code first: every sentence whose meaningful words you barely used, meaning less than MISS_COVERAGE of them appear in what you wrote (coverage), least covered first.
2. Then any sentences the model lists in the shape missesReplySchema.

validateMisses keeps only real sentences that pass the quote check, drops repeats and sentences you corrected, and keeps at most MAX_MISSES. You tick the ones you missed; only those count.

After an unclean session, the page names the concepts this one needs first that have no clean session yet (weakPrerequisites), as the likely reason. You can also record a catch, something Kizuki caught that you would have gotten wrong on an exam (recordCatch). The Today and History pages count catches per week, against a goal of one a week.