Page actions
field guide / candidate
Course routes — prerequisites
The distinct prerequisites record for Course routes. This page is proposal-only.
Status: proposedLifecycle: candidate
Record status
- Record ID
- field-guide:course-routes
- 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.
Entry evidence and required records
Before the procedure starts, an operator must identify the source, owner, scope, and required records below. Missing evidence holds the guide.
- source-bound field-guide record for course-routes
- job record for Guided inquiry
- job record for Source comparison
- job record for Lesson pathways
- job record for Study records
- job record for Uncertainty marking
- one project record grouping the route and study records
- source-labelled notes for each source or claim
- to-do records for route steps and review deadlines
- approval record for any proposed route marked Needs review, Approved, or Held
- agent-log record preserving Socrates authority, work state, and receipts
Intended operators and ownership
- Socrates
- learners
- human reviewers
- study-record owners
Being listed as an intended operator does not grant execution or publication authority.
Conditions that hold the guide before entry
- A named Socrates owner does not prove an active agent connection or execution authority.
- Indexed or prototype routes do not prove a connected web feature, provider effect, database authority, or production state.
- Source comparison may create false equivalence; preserve each source's wording, locator, revision, and uncertainty.
- Missing or stale source metadata can make a lesson pathway untraceable; hold the affected step.
- Unknown prerequisites can make a route inaccessible; record the unknown and request human review.
- Attachments may be unavailable or protected; use file references and hold upload or protected-storage assumptions.
- An approval status is a local proposal receipt, not publication or qualification.
- Deadline calculations are planning aids, not external calendar writes or reminders.
- Medical, financial, legal, safety, or other consequential course content requires domain review beyond this source-bound guide.
- Public documentation must contain useful, distinct route content; do not create doorway pages or keyword-spam pages.
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-routesagents/index.html#socratesobserved_native_contract.project_and_field_guide_collectionsobserved_native_contract.deadlinesobserved_native_contract.recordsobserved_native_contract.pointguardapp_route:/app/notebook/field-guides/app_route:/app/notebook/notes/app_route:/app/notebook/files/app_route:/app/notebook/projects/app_route:/app/notebook/to-dos/app_route:/app/notebook/approvals/app_route:/app/notebook/agent-logs/app_route:/app/pointguard/