Teaching protocols — prerequisites

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.

Entry evidence and required records

Before the procedure starts, an operator must identify the source, owner, scope, and required records below. Missing evidence holds the guide.

• Canonical field-guide record with owner Socrates, lifecycle, source locator, source SHA-256, provenance, revision, tags, links, and attachments.
• Teaching-protocol brief defining the learning objective, audience, scope, and intended pathway.
• Source note records for each supplied source, including source locator, source SHA-256, provenance, revision, and claim status.
• Lesson-pathway record containing ordered activities, checkpoints, prerequisites, and fallback branches.
• Study record containing learner questions, responses, evidence reviewed, uncertainty markers, and next steps.
• To-do records for preparation, review, and follow-up with dueAt, priority, completion state, tags, and revision history.
• Approval record for any proposed lesson pathway or public-facing communication; final publication and external send remain held.
• Agent log recording Socrates work, authority boundaries, receipts, and current state.

Intended operators and ownership

• Socrates
• educators
• learners
• reviewers
• Guth Hub workspace operators

Being listed as an intended operator does not grant execution or publication authority.

Conditions that hold the guide before entry

• 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/