Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

field guide / candidate

Teaching protocols — forms

The distinct forms record for Teaching protocols. This page is proposal-only.

Status: proposedLifecycle: 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.

Proposed form sections

Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth.

Scope and ownership

Define the bounded teaching task and preserve record ownership.

  • protocol title
  • learning objective
  • learner audience
  • owner agent
  • related job
  • in-scope questions
  • out-of-scope questions
  • source record IDs
  • visibility

Source and evidence register

Record what supports each teaching claim without implying unsupported authority.

  • source locator
  • source SHA-256
  • provenance note
  • source revision
  • claim or proposition
  • evidence excerpt or note
  • evidence status
  • conflicting source note
  • uncertainty label

Lesson pathway

Specify an ordered, reviewable route from prerequisites to learner output.

  • prerequisites
  • ordered activity
  • learner action
  • facilitator prompt
  • checkpoint question
  • expected evidence
  • failure branch
  • recovery action
  • completion signal

Study and follow-up records

Capture learner progress and unresolved work as durable records.

  • study record ID
  • learner question
  • response or attempt
  • evidence linked
  • confidence or uncertainty marker
  • open loop
  • next action
  • assigned owner
  • dueAt
  • priority

Review and release boundary

Separate local approval from unsupported publication or external effect.

  • reviewer
  • decision state
  • decision rationale
  • receipts
  • accessibility review
  • privacy review
  • public claim candidate
  • held claim
  • release status

Accessible state contract

  • Every field requires a visible and programmatic label.
  • Required and optional fields must be stated in text.
  • Invalid entries require an actionable message linked to the field.
  • Blocked and Held states remain visible without relying on color alone.

Supporting documentation fields

These fields come from the tools lane and remain separate from the primary operating form.

Inquiry scope

Define the learning question and boundaries before selecting material.

  • inquiry question
  • learner or cohort
  • prior knowledge
  • desired outcome
  • scope exclusions
  • owner
  • source locator

Evidence and source comparison

Capture source-labelled claims and distinguish agreement, conflict, and missing evidence.

  • source title
  • source locator
  • source SHA-256 when available
  • claim summary
  • supporting passage or observation
  • contradictory passage or observation
  • confidence label
  • open question

Lesson pathway

Turn the inquiry into ordered, reviewable learning steps.

  • step title
  • learning objective
  • prompt or activity
  • required prerequisite
  • expected learner artifact
  • check-for-understanding
  • estimated duration
  • dependency
  • failure or fallback path

Study record and review

Preserve what was attempted, what changed, and what remains uncertain.

  • study session date
  • learner response
  • facilitator observation
  • revision note
  • uncertainty marker
  • next action
  • review owner
  • due date
  • approval state

Required or proposed record references

No record existence is asserted by this documentation page.

  • 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

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/
  • field-guide:teaching-protocols
  • OBSERVED_NATIVE_CONTRACT
  • APP_ROUTES
  • ALLOWED_INSTRUMENTS