Learning course — field guides

Record status

Record ID

project:learning-course

Parent lifecycle

candidate

Page lane

app_features

Lane lifecycle

proposed

Owner

Not separately recorded

Owner role

Not separately recorded

Owner status

Not separately recorded

Qualification result

NOT RUN · held for evidence and human review

Working browser surface: Project templates & workflows — overview — Create a local project from this template and validate its forms. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

Related field-guide records

• /app/notebook/field-guides/

Source-proposed guide paths are references, not proof that those paths resolve.

Operating sequence

1. Create the project record with canonical ID, origin, source references, provenance, revision, lifecycle, tags, links, and visibility.
2. Complete intake and identify source-bound learning outcomes, audience, accessibility needs, and explicit exclusions.
3. Approve scope before drafting lessons or committing milestone deadlines.
4. Create milestones, owners, dependencies, acceptance criteria, and dueAt-backed todo records.
5. Build the workback from the final target date, reserving review, evidence, and accessibility buffers.
6. Draft lessons using source locators and uncertainty markers; link only verified tools, guides, and exact allowed instrument slugs.
7. Collect local evidence and receipts through Notebook records or file references; preserve revisions and limitations.
8. Review milestone completion and evidence sufficiency; route disputed or high-impact decisions to Approvals.
9. Record risks, blockers, stale sources, and failure states; pause affected work when a prerequisite or source cannot be verified.
10. Run closure review, document incomplete work and held effects, obtain closure approval, and set a maintenance review date.

Handoff boundary

• Treating a prototype or indexed route as proof of a connected web feature.
• Inventing course authority, accreditation, learner qualification, publication, or completion claims from local records.
• Using stale, unverifiable, or weakly attributed sources without an uncertainty marker.
• Overwriting revisions or deadline changes and losing provenance or prior decisions.
• Allowing a milestone to appear complete when required dependencies, evidence, accessibility review, or approvals are missing.
• Creating doorway documentation routes with duplicate or non-useful content.
• Hidden upload, provider writes, external messaging, credential operations, customer indexing, or publication effects.
• Making medical, financial, legal, safety, or other high-impact instructional claims without appropriate review and limitations.
• Inaccessible forms, unclear validation, color-only statuses, missing focus management, or loss of user-entered data on failure.

Sources and evidence

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

• source_record:project:learning-course
• NotebookCollectionKind.project
• NotebookTodoPayload.dueAt
• Notebook records preserve canonical IDs, provenance, source SHA-256, revisions, lifecycle, tags, links, attachments, and record revisions
• Notebook Agenda deadlines/workbacks
• /app/notebook/projects/
• /app/notebook/to-dos/
• /app/notebook/agenda/
• /app/notebook/field-guides/
• /app/notebook/approvals/
• /app/notebook/notes/
• /app/notebook/files/
• /app/notebook/agent-logs/
• /app/pointguard/
• Notebook records canonical IDs, provenance, revisions, links, and attachments
• PointGuard persistent cross-app context surface
• APP_ROUTES:/app/notebook/projects/
• APP_ROUTES:/app/notebook/today/
• APP_ROUTES:/app/notebook/notes/
• APP_ROUTES:/app/notebook/to-dos/
• APP_ROUTES:/app/notebook/agenda/
• APP_ROUTES:/app/notebook/field-guides/
• APP_ROUTES:/app/notebook/search/
• APP_ROUTES:/app/notebook/approvals/
• APP_ROUTES:/app/notebook/agent-logs/
• APP_ROUTES:/app/pointguard/