Source: https://guthlabs.ai/docs/project-templates/learning-course/forms/

project template / candidate

# Learning course — forms

The distinct forms record for Learning course. This page is proposal-only.

Status: **proposed**Lifecycle: **candidate**

## Record status

**Record ID**: project:learning-course

**Parent lifecycle**: candidate

**Page lane**: forms

**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](<https://guthlabs.ai/labs.html#templates-workflows>) — 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.

## Proposed form sections

Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth.

### Intake

Capture the learning request, intended learner, source boundary, and initial feasibility without implying publication or provider access.

- request title

- requester record ID

- course owner record ID

- intended learner or audience

- learning problem

- desired learner outcome

- source records and locators

- source SHA-256 when available

- source freshness or revision note

- known uncertainty markers

- requested start date

- target completion date

- priority

- intake status

- accessibility needs

- out-of-scope requests

### Scope and success criteria

Define what the course includes, excludes, and must demonstrate.

- course objective

- included topics

- excluded topics

- lesson count target

- lesson duration target

- prerequisites

- required learner outputs

- success criteria

- quality bar

- evidence standard

- privacy and visibility classification

- assumptions

- scope approval status

### Milestones and deliverables

Turn the course into ordered, reviewable deliverables.

- milestone ID

- milestone title

- description

- deliverable type

- sequence number

- owner record ID

- reviewer record ID

- planned start

- dueAt

- completion state

- acceptance criteria

- required predecessors

- evidence required

- revision limit

- status note

### Deadlines and workback

Represent deadlines as explicit todo and agenda candidates while keeping external calendar writes held.

- final target date

- learner launch date if applicable

- workback anchor

- milestone dueAt values

- review buffer

- content freeze date

- evidence freeze date

- approval deadline

- closure review date

- todo priority

- recurrence candidate

- conflict review result

- schedule change rationale

- external write status

### Dependencies and owners

Make blocking relationships and accountability visible.

- dependency ID

- blocked milestone

- blocking record or milestone

- dependency type

- dependency owner record ID

- request date

- needed-by date

- status

- fallback plan

- escalation owner

- resolution evidence

- dependency risk level

### Tools and field guides

Declare only verified instruments, local interfaces, skills, guides, records, or providers needed for the course.

- tool or guide name

- kind

- exact instrument slug if applicable

- purpose

- lesson or milestone association

- input requirements

- output to preserve

- verification status

- human review required

- failure fallback

- held capability note

### Lesson design

Provide a repeatable lesson form linked to sources, activities, uncertainty, and evidence.

- lesson ID

- lesson title

- learning objective

- source references

- key concepts

- instructional steps

- practice activity

- learner submission

- estimated duration

- required tool or guide

- uncertainty marker

- accessibility accommodations

- completion evidence

- review status

- revision notes

### Evidence and receipts

Preserve source-bound proof of work without asserting qualification or external publication.

- evidence ID

- associated lesson or milestone

- evidence type

- record ID or local file reference

- source locator

- source SHA-256 when available

- created by

- created at

- revision

- what the evidence demonstrates

- limitations

- visibility

- review status

- receipt or approval reference

### Approvals

Require human review for scope, content readiness, evidence sufficiency, and closure.

- approval ID

- approval stage

- proposal summary

- approver record ID

- requested at

- decision

- decision date

- conditions

- held reason

- receipt reference

- affected revision

- re-review dueAt

### Risks and failure states

Track uncertainty, blocked work, stale sources, accessibility gaps, and unsupported claims.

- risk ID

- risk statement

- category

- affected milestone

- likelihood

- impact

- owner record ID

- trigger

- mitigation

- fallback

- review dueAt

- status

- residual uncertainty

- escalation path

### Closure

Confirm completion, unresolved work, retained evidence, and future review without claiming qualification or publication.

- closure owner record ID

- completion summary

- completed milestones

- incomplete milestones

- open risks

- unresolved uncertainty

- evidence inventory

- final revision

- learner feedback reference

- maintenance owner

- next review dueAt

- archival or retention instruction

- closure approval

- publication status

- external effects held

### Accessible state contract

- Every field requires a visible and programmatic label.

- Required and optional fields must be stated in text.

- Invalid entries require an actionable message linked to the field.

- Blocked and Held states remain visible without relying on color alone.

## Supporting documentation fields

These fields come from the app_features lane and remain separate from the primary operating form.

### Course basics

Define the learning objective and local project boundary.

- course title

- short description

- learning objective

- learner

- owner

- start date

- target completion date

- status

- visibility

- tags

### Learning path

Create ordered lessons and define prerequisites.

- lesson title

- lesson description

- sequence number

- estimated minutes

- prerequisite lesson IDs

- source record IDs

- required or optional

- lesson status

- uncertainty level

### Study record

Capture what was attempted and what evidence supports completion.

- lesson ID

- session date and time

- minutes studied

- activity type

- notes

- evidence links

- confidence rating

- open questions

- next action

### Deadlines and workback

Translate a target completion date into reviewable local tasks.

- target date

- available study days

- weekly capacity in minutes

- buffer days

- milestone dates

- task owner

- priority

- due date

- recurrence candidate

### Review and uncertainty

Make gaps, assumptions, and decisions visible before progression.

- uncertainty statement

- affected lesson IDs

- severity

- source needed

- reviewer

- review state

- resolution note

- receipt or approval link

## Required or proposed record references

No record existence is asserted by this documentation page.

- project record

- source note or source locator

- course scope record

- milestone records

- todo records with dueAt

- dependency records

- owner assignments

- workback record

- tool and guide links

- evidence records

- approval records

- risk records

- closure record

- project record owned by Notebook Projects

- ordered lesson records with source locators and provenance

- study session records

- uncertainty markers

- Notebook to-dos with dueAt, priority, completion state, tags, and revisions

- source-labelled notes

- linked file references

- approval records for proposed course decisions

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