Source: https://guthlabs.ai/docs/field-guides/teaching-protocols/steps/ field guide / candidate # Teaching protocols โ€” steps The distinct steps record for Teaching protocols. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: field-guide:teaching-protocols **Parent lifecycle**: candidate **Page lane**: plan **Lane lifecycle**: proposed **Owner**: Socrates **Owner role**: Not separately recorded **Owner status**: Not separately recorded **Qualification result**: NOT RUN ยท held for evidence and human review **Working browser surface:** [Field guides โ€” documentation]() โ€” Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held. ## Ordered procedure - Confirm that the canonical guide is owned by Socrates and that the source record is available at agents/index.html#socrates; do not add unsupplied sources or infer production state. - Create or update the field-guide record with lifecycle proposed, provenance, source locator, source SHA-256, revision, tags, links, and visibility. - Write the protocol brief: choose one learning objective, identify the learner audience, list in-scope and out-of-scope questions, and name the related job: Guided inquiry, Source comparison, Lesson pathways, Study records, or Uncertainty marking. - Create a source note for every source actually used. Preserve the locator, hash, provenance, revision, and a concise statement of what the source does and does not establish. - Draft prerequisites using only known context. If a prerequisite is unknown, mark it as an open question rather than assuming learner knowledge. - Arrange the lesson pathway as small ordered activities: question framing, source inspection, comparison or inquiry, learner attempt, evidence check, uncertainty marking, and next-step capture. - For each activity, add a checkpoint with an observable response or record. Do not treat a page visit, named surface, or draft as evidence of a completed lesson. - Define failure branches before review: missing source metadata, conflicting evidence, learner cannot state the question, unsupported claim, inaccessible instruction, missed deadline, or proposed external communication. - Create study records for learner questions, attempts, linked evidence, uncertainty, and next actions. Keep canonical study records in the responsible specialist surface; PointGuard may carry context but does not become the canonical owner. - Create preparation and review to-dos. Use dueAt and priority; keep completion human-controlled and retain revisions. Use Today for current work and Agenda only for source-bound schedule drafts. - Review the pathway in Field Guides and inspect source-labelled notes, linked files, to-dos, and study records. Use Search only for local indexed records and respect visibility partitions. - Submit the proposed pathway and any public claim candidates to Approvals. Mark unsupported or externally consequential claims Held; do not publish, send, connect providers, or alter customer or production state. - Record Socrates work, authority boundaries, evidence receipts, unresolved questions, and current lifecycle in Agent Logs. - Close only when all completion criteria and deterministic acceptance tests pass; otherwise retain lifecycle proposed and create a recovery to-do. ## Deadline and chronology rules - Set a preparation dueAt before the first learner-facing review; if no date is supplied, leave dueAt unset and mark scheduling as an open loop rather than inventing a date. - Set the review dueAt after the pathway draft and before any proposed communication; use priority to distinguish blocking review from optional refinement. - Create follow-up dueAt from the agreed learner next action; never infer a learner deadline. - If a dueAt is missed, mark the to-do overdue or held, preserve its revision history, and create a recovery action before proceeding. - Do not represent Agenda drafts, reminders, approvals, or to-do completion as external execution. ## Failure branches during execution - Confusing a named native route with a connected web feature. - Treating Socrates ownership or the supplied source reference as proof of production availability. - Inventing learner prerequisites, dates, evidence, sources, or outcomes. - Collapsing source evidence, facilitator interpretation, learner response, and uncertainty into one unsupported claim. - Using a calculator or other instrument when the teaching task does not require one, or presenting an educational result as authoritative advice. - Allowing a draft message, schedule, approval, or export to create an external effect. - Publishing doorway or keyword-spam documentation instead of distinct useful content. - Failing to preserve provenance, hashes, revisions, visibility, or canonical record ownership. - Using color alone to communicate uncertainty or review state. - Treating incomplete, inaccessible, conflicting, or missing evidence as qualification or completion. ## Sources and evidence These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment. - `source_record:field-guide:teaching-protocols` - `agents/index.html#socrates` - `Observed native contract: project_and_field_guide_collections` - `Observed native contract: deadlines` - `Observed native contract: records` - `Observed native contract: pointguard` - `/app/notebook/field-guides/` - `/app/notebook/notes/` - `/app/notebook/to-dos/` - `/app/notebook/approvals/` - `/app/notebook/agent-logs/`