Course routes — steps

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.

Ordered procedure

1. 1. Open the proposed course-routes field-guide record in Notebook Field Guides and verify that the source record is field-guide:course-routes:plan, owned by Socrates, with related jobs Guided inquiry, Source comparison, Lesson pathways, Study records, and Uncertainty marking.
2. 2. Create or link a local project record in Notebook Projects for the route; set lifecycle to proposed and link the five related job records. Do not represent the project as an active backend or production project.
3. 3. Capture the inquiry question, audience, prerequisites, and desired review date in the Route identity and Schedule sections. If any of these are unknown, record the gap explicitly rather than filling it with an assumption.
4. 4. Add each available source as a source-labelled note or file reference. Preserve origin, locator, SHA-256 when supplied, provenance, revision, lifecycle, tags, links, and attachments; do not treat an unverified reference as authoritative.
5. 5. For each lesson pathway step, record a learning purpose, prerequisite, prompt, dependency, expected study record, and completion evidence. Keep the sequence bounded and manually reviewable.
6. 6. Compare sources claim by claim. Record source locators, points of agreement, points of difference, confidence, and unresolved uncertainty. Do not collapse disagreement into a single fact.
7. 7. Create study-record notes linked to the relevant lesson step and source. Record learner work, date, revision, and attachment references; keep private or held material partitioned from public documentation.
8. 8. Create local to-dos for preparation, source comparison, pathway drafting, study-record review, and final human review. Use dueAt, priority, completion state, tags, revisions, and scheduled or deadline views where supported.
9. 9. At each checkpoint, inspect Notes, Files, Projects, To-dos, Search, and Agent Logs for missing links, stale revisions, unsupported claims, and visibility errors. Use PointGuard only as a contextual surface; specialist apps remain execution and canonical-record owners.
10. 10. Submit the proposed route to Notebook Approvals with status Needs review. A human reviewer may mark it Approved or Held locally; neither status constitutes publication, provider action, customer indexing, or production qualification.
11. 11. Close only the local route work when completion criteria pass, all receipts and records are linked, and held questions are documented. Keep the lifecycle proposed unless a separately verified lifecycle transition is available.

Deadline and chronology rules

• Set a target human-review date before drafting the pathway; if absent, mark the route blocked for scheduling.
• Create preparation and source-capture deadlines at least one checkpoint before pathway approval.
• Create a source-comparison checkpoint before any lesson pathway is submitted for approval.
• Create a study-record review checkpoint after each bounded lesson step or declared study session.
• Use explicit dueAt values and local deadline views; recurring items remain proposals until a human confirms them.
• If a deadline passes, mark the to-do overdue or held, preserve the revision, and reschedule explicitly rather than silently shifting it.
• Do not send messages, write to external calendars, publish documentation, connect providers, or affect customers.

Failure branches during execution

• 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-routes
• 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_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/