Teacher notes and student materials can belong to the same lesson without belonging on the same screen. Keep their intended audience explicit through editing, generation, presentation, export, and help features.
Hiding a notes panel is not enough if an answer key remains in the projected view or private context enters a student-facing generated response.
Classify content by audience and purpose
Separate approved student explanations, questions, answer keys, private teaching prompts, planning notes, and any sensitive information. Define which parts may enter generation context and which are available to each display or export path.
Avoid using a single free-text lesson field for everything and relying on the model to infer what should remain private. The application should enforce the audience boundary before processing or rendering.
Test a fictional discussion lesson
Suppose a teacher writes a private note about where learners may struggle and prepares a quiz with answers. The student presentation should show the question without the answer, while the teacher view retains guidance.
Use harmless canary text in private notes and test presentation, print or export, fullscreen transitions, student help, search, and copied content. Confirm the canary does not appear on student-facing surfaces or enter contexts that should exclude it.
Test editing while presenting, reopening the pack, switching lessons, and an error screen during projection. A failure message should not dump private source objects or expose notes merely because the normal view failed.
Preserve review state and deliberate sharing
If the teacher chooses to promote a private note into student material, make that an explicit edit or sharing action. Do not silently copy all notes into the lesson because generation needs more context.
Keep logs and support exports within the same policy. A teacher-only note can still leak through diagnostic payloads even when the classroom interface behaves correctly.
The tradeoff is convenient combined editing versus clear audience control. One workspace can support both roles if the content model and rendering paths remain explicit. Excessive duplication creates version drift, while unstructured mixing creates exposure risk.
Use ordinary role and surface language in the interface so teachers understand what will be shown. Internal implementation detail should not be required to make a safe presentation decision.
The ChalkLens case study documents teaching notes, quizzes, Present mode, and contextual help. This separation matrix is proposed guidance and does not claim a privacy audit or describe its internal content schema.
Questions about teacher-only content
Is collapsing the notes panel enough?
No. Check exports, help context, copied content, errors, and projection transitions as separate surfaces.
Should student details appear in generation prompts?
Only under an explicit authorised design and appropriate policy. Many lesson-preparation tasks can work from curriculum material without identifiable student information.
What should be tested first?
Place a harmless private marker in notes, then exercise every student-facing path. Bring unexpected appearances to an education data-boundary review.