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

project template / candidate

# Learning course — deadlines

The distinct deadlines 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**: 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](<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.

## Deadline and workback rules

- Every milestone must have an owner, acceptance criteria, and dueAt before it is marked planned.

- The final target date must be later than or equal to all required milestone dueAt values and must include explicit review buffer.

- A blocked dependency must create or link a risk and must not be silently treated as complete.

- Overdue work remains open until a human records a revised dueAt, completion state, or held reason.

- Agenda entries are proposals only; external calendar writes remain held.

- Approval deadlines must precede content freeze and closure review dates.

- If source freshness, provenance, or evidence is missing, the affected milestone remains Needs review or Held.

- Closure cannot be approved while critical risks, missing required evidence, or unresolved scope decisions remain undocumented.

- A target completion date is optional, but a workback cannot be generated without one.

- Every generated task must have a due date no later than the target date and retain its originating lesson ID.

- Workback generation must use explicit available study days, weekly capacity, and buffer days; missing values produce a validation error rather than guessed dates.

- If capacity is insufficient for the target date, show an Unsatisfied capacity warning and offer revision of scope, capacity, or target date without silently changing records.

- Tasks with due dates before the current local date are marked overdue, not deleted or auto-completed.

- A completed lesson requires either configured evidence or an explicit human approval record; study minutes alone do not qualify.

- Schedule conflicts are displayed for review; no external calendar event is created or modified.

- Recurring review candidates remain drafts until a human confirms recurrence.

## Workback sequence

- Create or open the learning-course project in Notebook Projects.

- State the learning objective, learner, owner, dates, visibility, and local-only boundary.

- Add source-linked lessons and assign a deterministic order.

- Record prerequisites and flag cycles or missing prerequisite records.

- Estimate lesson effort and create a draft workback from the target completion date.

- Review generated to-dos, adjust dates or capacity, and save them as local Notebook records.

- Open a lesson to capture study sessions, notes, evidence links, confidence, and open questions.

- Mark lesson progress only when the configured completion evidence is present; otherwise retain Needs review.

- Inspect uncertainty markers and route unresolved items to Notebook Approvals or a reviewer.

- Use PointGuard to keep the current lesson, next action, deadline, and held effects visible across app surfaces.

- Search and filter the project by lesson state, due date, uncertainty, source, owner, and evidence state.

- Archive or revise the project while preserving canonical IDs, provenance, revisions, and source hashes.

## Scheduling records

- milestone records

- dependency records

- owner assignments

- workback record

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