Source: https://guthlabs.ai/docs/project-templates/research-study/deadlines/

project template / candidate

# Research study — deadlines

The distinct deadlines record for Research study. This page is proposal-only.

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

## Record status

**Record ID**: project:research-study

**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

- A final decision date is required before the workback can be approved.

- Every milestone must have one owner, one due date, and acceptance criteria.

- Every dependency must have a needed-by date no later than the dependent milestone due date.

- Internal review and evidence freeze must precede final closure.

- Overdue blocking dependencies set affected milestones to Needs review or Held; they do not silently move deadlines.

- A deadline change requires a recorded reason, revised workback, affected-owner acknowledgement, and approval when it changes the final decision date.

- No recurrence is created unless a human explicitly marks recurrenceCandidate and approves the schedule.

- A closure request is blocked when required evidence, citations, approvals, or unresolved contradiction decisions are missing.

- Final deadline is required before a workback can be generated.

- Milestones must not occur after the final deadline.

- A task with a dependency cannot be scheduled before its dependency unless explicitly marked as an exception for review.

- The workback must include collection, contradiction review, citation review, synthesis, and approval milestones.

- Buffer days are shown separately and cannot silently reduce task durations.

- Overdue incomplete tasks are marked overdue locally and remain visible in Today and the project view.

- Changing the final deadline preserves the prior schedule revision and requires explicit workback regeneration.

- Agenda conflicts are warnings; no external calendar write is performed.

- Missing timezone labels produce a review warning rather than an assumed timezone.

## Workback sequence

- Create the project record and assign a canonical project ID.

- Enter the research question, scope boundaries, evidence rules, and contradiction rule.

- Set the final deadline and generate a workback of collection, comparison, synthesis, citation review, and approval tasks.

- Add source-labelled references and local file references; preserve source locators, SHA-256 values when supplied, provenance, and revisions.

- Create evidence notes linked to individual source references, distinguishing observation, interpretation, and unresolved claim.

- Record each material disagreement as a contradiction with affected claims, supporting source IDs, status, and required follow-up.

- Use filters to view records by lifecycle, source type, claim status, contradiction status, owner, tag, due date, and approval state.

- Review the PointGuard project room for current work, linked Notebook records, open loops, and held actions.

- Draft a conclusion with citations and limitations; run completeness checks for unsupported claims and unresolved contradictions.

- Submit the draft to local approval; preserve the decision and receipt without publishing or sending externally.

- Close or hold the project while retaining revisions, provenance, deadlines, and unresolved items.

## Scheduling records

- to-dos with due dates

- milestone records

- dependency records

- agenda workback records

## Sources and evidence

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

- `source_record:project:research-study`

- `project:research-study`

- `NotebookCollectionKind.project`

- `NotebookTodoPayload.dueAt`

- `Notebook Agenda deadlines/workbacks`

- `Observed native contract: records provenance and revision fields`

- `Observed native contract: PointGuard cross-app context surface`

- `Observed app route: /app/notebook/projects/`

- `Observed app route: /app/notebook/to-dos/`

- `Observed app route: /app/notebook/agenda/`

- `Observed app route: /app/notebook/approvals/`

- `Observed app route: /app/notebook/field-guides/`

- `Observed app route: /app/notebook/agent-logs/`

- `Observed app route: /app/notebook/notes/`

- `Observed app route: /app/notebook/files/`

- `Observed app route: /app/pointguard/`

- `Notebook records provenance and revisions`

- `PointGuard persistent cross-app context surface`

- `APP_ROUTES:/app/notebook/projects/`

- `APP_ROUTES:/app/notebook/notes/`

- `APP_ROUTES:/app/notebook/files/`

- `APP_ROUTES:/app/notebook/to-dos/`

- `APP_ROUTES:/app/notebook/agenda/`

- `APP_ROUTES:/app/notebook/approvals/`

- `APP_ROUTES:/app/notebook/search/`

- `APP_ROUTES:/app/pointguard/`
