Teaching protocols — tools

Canonical tools-page assignments

• Notebook Field Guides (interface · required) — Use as the proposal destination for prerequisites, ordered procedures, related records, and bounded instrument links; do not treat its indexed route as proof of publication or connected web behavior.
• Notebook Notes (interface · required) — Use for source-labelled claims, learner observations, and uncertainty notes with provenance and revisions; do not use as an unlabelled source repository.
• Notebook Projects (interface · required) — Use to group a lesson pathway, study records, notes, and review items while preserving record ownership; do not infer an active project backend.
• Notebook To-dos (interface · required) — Use for explicit workback actions, due dates, priority, completion state, tags, and human-review signals; do not imply automated reminders or external calendar writes.
• Notebook Approvals (interface · required) — Use to hold contested interpretations and record local approval decisions with receipts; do not treat local approval as institutional or publication approval.
• Notebook Search (interface · required) — Use to find local indexed notes, guides, and study records while respecting visibility; do not claim customer indexing, universal search, or provider-backed retrieval.
• PointGuard (interface · required) — Use as a contextual room for the current inquiry and linked Notebook records; do not treat it as the canonical owner of specialist records.
• Source comparison (skill · required) — Use to separate source claims, conflicts, provenance, and unknowns before forming a lesson conclusion.
• Uncertainty marking (skill · required) — Use explicit labels such as supported, contested, assumption, and unknown; never collapse uncertainty into confidence by omission.
• Lesson pathway design (skill · required) — Use to order prerequisites, activities, checks, artifacts, and fallback routes into an implementable learning sequence.
• Study records (record · required) — Use to preserve learner responses, facilitator observations, revisions, and next actions as owned records with revision history.
• Agent Logs (record · required) — Use to inspect Socrates' authority boundary, current work, and receipts; do not infer work completion from an absent or unverified receipt.

Canonical tools-page assignments