Source: https://guthlabs.ai/docs/field-guides/teaching-protocols/qualification/

field guide / candidate

# Teaching protocols — qualification

The distinct qualification 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**: docs_urls

**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](<https://guthlabs.ai/docs/field-guides/>) — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

## Qualification status

**Result**: NOT RUN

**Disposition**: HELD

**Reviewer**: Not recorded

**Receipt**: Not recorded

This page defines proposed acceptance criteria for the docs_urls lane. It does not execute tests, establish compliance, qualify the subject, or authorize an effect.

### Lane-specific instrument aids

No verified instrument is assigned to this qualification lane.

## Outcome definitions

**Verified**: All stated evidence and acceptance requirements passed for the exact reviewed revision; this still does not authorize deployment or an external effect.

**Failed**: One or more deterministic acceptance requirements failed with an inspectable reason.

**Needs review**: Evidence or interpretation is incomplete, conflicting, or awaits an identified human reviewer.

**Held**: Authority, required evidence, safe execution conditions, or a principal gate is absent.

The current record remains NOT RUN / HELD. These definitions describe candidate outcomes only.

## Proposed deterministic acceptance tests

Route-resolution and distinct-content checks apply only to the admitted canonical routes in this record. Held source-proposed extensions are non-resolving proposals and are excluded.

- The overview explains the guide's purpose, audience, owner agent, related jobs, and proposed lifecycle.

- Every listed documentation route has content distinct from the overview and a useful search intent.

- The steps page contains an ordered protocol with a clear start condition, checkpoints, completion condition, and held failure states.

- The tools page names only observed native surfaces or the supplied guide record and describes authority boundaries.

- The forms page uses implementable fields for intent, sources, pathway, uncertainty, and receipts.

- The examples page includes at least one guided-inquiry example, one source-comparison example, and one uncertainty-marking example without inventing source facts.

- The qualification page tests source provenance, question scope, pathway completeness, uncertainty marking, accessibility, and review ownership.

- Each related-job page has a distinct purpose, route, inputs, outputs, failure states, and links back to the guide.

- Records preserve canonical IDs, provenance, source locators, revisions, lifecycle, links, and review receipts where applicable.

- The guide labels itself proposed and does not claim deployment, provider connection, database authority, customer indexing, publication, or qualification.

## Negative and held-state tests

- Guided inquiry can become leading instruction if questions presuppose unsupported answers.

- Source comparison can create false equivalence when sources differ in scope, evidence, or context.

- Lesson pathways can imply mastery from completion alone; require a learner artifact or review checkpoint.

- Uncertainty labels can be vague unless attached to a specific claim, step, or source conflict.

- Study records may expose private learner information; keep visibility and ownership explicit.

- A named native surface does not prove a connected web feature; keep app behavior prototype, indexed, or held as observed.

- Deadlines and scheduled views must not be treated as external reminders or provider writes.

- Medical, financial, legal, safety, and other high-consequence topics require additional qualified review; this guide does not qualify them.

## Qualification claim boundary

### Potentially allowed only after the stated evidence

- A proposed teaching-protocol structure can organize guided inquiry, source comparison, lesson pathways, study records, and uncertainty marking.

- The guide can specify fields, checkpoints, provenance requirements, review states, and held effects.

- The supplied record names Socrates as owner agent and lists the five related jobs.

### Still held

- Deployment or production availability.

- Connected web teaching workflows.

- Provider, credential, database, or customer effects.

- Publication, customer indexing, or public qualification.

- Claims that Socrates or any learner is qualified, certified, or educationally successful.

- Claims that any source is authoritative without recorded provenance and review.

## 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`

- `field-guide:teaching-protocols`

- `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/projects/`

- `/app/notebook/search/`

- `/app/notebook/agent-logs/`

- `/app/pointguard/`