Page actions
field guide / candidate
Teaching protocols — related jobs
The distinct related jobs record for Teaching protocols. This page is proposal-only.
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.
Related Agent job handoffs
Handoff record requirements
The guide may supply evidence, checkpoints, and failure context to a job. The receiving job retains ownership and must record its own decision, approval, and receipt.
- 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.
- source-labelled notes
- lesson pathway project record
- study record
- to-do records with due dates and review state
- approval record for contested or held conclusions
- agent log receipt
Ownership boundary
The guide supports these jobs without importing their package descriptions, becoming the job owner, or gaining independent authority.
- 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-protocolsagents/index.html#socratesObserved native contract: project_and_field_guide_collectionsObserved native contract: deadlinesObserved native contract: recordsObserved native contract: pointguard/app/notebook/field-guides//app/notebook/notes//app/notebook/to-dos//app/notebook/approvals//app/notebook/agent-logs/field-guide:teaching-protocolsOBSERVED_NATIVE_CONTRACTAPP_ROUTESALLOWED_INSTRUMENTS