Teaching protocols — examples

The distinct examples 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.

Hypothetical scenarios

A reviewer opens the Teaching protocols guide for bounded local rehearsals. Every fixture uses invented placeholders, performs no provider or external action, and remains held until source evidence and human review are recorded.

1. Guided inquiry fixture

A reviewer records a bounded question, links only supplied source references, and marks every unanswered point Needs review.

Fixture ID: teaching-protocols-example-001
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

2. Source comparison fixture

A reviewer compares two hypothetical source locators, preserves disagreement, and holds any conclusion until provenance is supplied.

Fixture ID: teaching-protocols-example-002
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

3. Uncertainty and pathway fixture

A reviewer constructs a local procedure or study pathway with checkpoints while labelling uncertainty and leaving external effects Held.

Fixture ID: teaching-protocols-example-003
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

4. Potentially allowed claim fixture

A hypothetical claim may advance only when its exact evidence locator, scope, reviewer, and decision rationale are recorded; this fixture asserts no fact.

Fixture ID: teaching-protocols-example-004
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

5. Held claim fixture

A hypothetical unsupported claim remains Held with missing evidence and human-review rationale visible; it is not published or indexed.

Fixture ID: teaching-protocols-example-005
Evidence: Hypothetical source placeholders only
Decision: HELD · human review required
External effects: None

Filled example fields

Scope and ownership fixture

Define the bounded teaching task and preserve record ownership.

protocol title: Example value to be supplied and reviewed
learning objective: Example value to be supplied and reviewed
learner audience: Example value to be supplied and reviewed
owner agent: Named human or Agent owner required
related job: Example value to be supplied and reviewed
in-scope questions: Example value to be supplied and reviewed

Source and evidence register fixture

Record what supports each teaching claim without implying unsupported authority.

source locator: fixture-source-001 (hypothetical; no external claim)
source SHA-256: fixture-source-001 (hypothetical; no external claim)
provenance note: Example value to be supplied and reviewed
source revision: fixture-source-001 (hypothetical; no external claim)
claim or proposition: Example value to be supplied and reviewed
evidence excerpt or note: fixture-source-001 (hypothetical; no external claim)

Lesson pathway fixture

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

prerequisites: Example value to be supplied and reviewed
ordered activity: Example value to be supplied and reviewed
learner action: Example value to be supplied and reviewed
facilitator prompt: Example value to be supplied and reviewed
checkpoint question: Example value to be supplied and reviewed
expected evidence: fixture-source-001 (hypothetical; no external claim)

Review questions

A new guide record identifies Socrates as owner and links the supplied source reference agents/index.html#socrates.
The inquiry form cannot be considered complete without a bounded question, learner context, owner, and scope exclusions.
Each source claim stores a source label and locator; conflicting claims are represented separately from consensus claims.
Each pathway step includes an objective, prompt or activity, prerequisite, learner artifact, check-for-understanding, duration, and fallback path.
Instrument use records an exact allowed slug, inputs, assumptions, output, and a statement of educational scope.
Uncertainty is visible through text labels and is not conveyed by color alone; all controls have usable labels and keyboard access.
A due item shows owner, due date, priority, completion state, and review state; no test expects an external reminder or calendar write.
A disputed conclusion can be placed in Needs review or Held without deletion, preserving its provenance and revision history.

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