Course routes — qualification

Record status

Record ID

field-guide:course-routes

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 — 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.

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 route explains the purpose, audience, inputs, outputs, record owners, lifecycle label, and held effects.
• Each documentation route has a distinct title, question, procedure, example shape, failure state, and acceptance check; no route is a keyword-only doorway page.
• The guide is labelled proposed and does not claim deployment, provider connection, database authority, customer indexing, publication, or qualification.
• A reviewer can trace each source comparison to a source-labelled note or file reference with a locator or an explicit missing-locator state.
• A lesson pathway cannot be marked complete without an objective, prerequisite decision, source link or documented source gap, practice activity, and completion condition.
• A study record identifies the learner action, date, related lesson or question, artifact or file reference when applicable, open question, next action, and owner.
• Uncertain claims expose evidence, limitations, alternative interpretations, and a Needs review or Held state.
• Deadline workback produces concrete to-dos with due dates and does not perform external writes.
• Agent logs preserve the proposal, authority boundary, current state, and receipt for Socrates work.
• Forms are keyboard operable, use visible labels, preserve focus and errors, expose status text programmatically, and do not rely on color alone.
• Search results distinguish the field guide, jobs, notes, sources, lesson pathways, study records, and uncertainty records by type and visibility.
• Related-job pages link back to the guide and add job-specific content rather than duplicating the overview.

Negative and held-state tests

• Confusing a proposed documentation route with a live course, connected provider, or published customer experience.
• Treating Socrates as qualified or authoritative merely because it is named as an owner agent.
• Presenting source summaries as verified facts when provenance, context, or comparison is incomplete.
• Turning lesson lists or due dates into hidden automation or external calendar writes.
• Allowing unsupported conclusions to pass from notes into a lesson brief without an uncertainty state.
• Using educational instruments for medical, legal, financial, safety-critical, or individualized decisions.
• Creating duplicate notes or conflicting lesson versions without canonical IDs, provenance, revisions, and visible lifecycle.
• Exposing private study records through a public documentation route or search index.
• Accessibility failure in long procedures, forms, status labels, keyboard navigation, or error recovery.

Qualification claim boundary

Potentially allowed only after the stated evidence

• This is a proposed field-guide design for course routes.
• The supplied source record associates Course routes with Guided inquiry, Source comparison, Lesson pathways, Study records, and Uncertainty marking.
• Observed native surfaces include Notebook Field Guides, Notes, Files, Lists, To-dos, Agenda, Paper, Search, Agent Logs, and PointGuard.
• The allowed directory contains educational instruments with the exact slugs listed in this proposal.

Still held

• That any documentation URL is deployed or crawlable in production.
• That Guth has a connected course provider, customer database, publication system, or external calendar.
• That Socrates or any agent has completed, reviewed, or qualified a course route.
• That a source comparison establishes truth, authority, accreditation, or learning outcomes.
• That any study record is customer-indexed or publicly visible.
• That an instrument result is professional advice, a verified lesson answer, or sufficient evidence for a consequential decision.

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

• source_record:field-guide:course-routes
• agents/index.html#socrates
• field-guide:course-routes
• 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/files/
• /app/notebook/lists/
• /app/notebook/to-dos/
• /app/notebook/agenda/
• /app/notebook/paper/
• /app/notebook/search/
• /app/notebook/agent-logs/
• /app/pointguard/
• ALLOWED_INSTRUMENTS:scientific-calculator
• ALLOWED_INSTRUMENTS:statistics-suite-descriptive-stats
• ALLOWED_INSTRUMENTS:unit-dimensional-analysis-converter