Source: https://guthlabs.ai/docs/project-templates/field-guide-build/deadlines/ project template / candidate # Field guide build โ€” deadlines The distinct deadlines record for Field guide build. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: project:field-guide-build **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. ## Deadline and workback rules - A final deadline is required before the project can leave intake. - Every milestone must have an owner, planned finish date, acceptance criteria, and review status. - Workback dates must include a separate evidence-review window and approval window before the final deadline. - A milestone cannot be marked complete without linked evidence or an explicit accepted exception. - If a dependency is blocking and its required-by date passes, the affected milestone becomes At risk and requires owner review. - Any changed deadline requires a reason, revised workback, revision owner, and approval if the final deadline changes. - Dates must include a time zone; ambiguous or invalid dates block submission. - Overdue items remain visible in Today, To-dos, and Agenda views; no hidden automation or external calendar write is assumed. - Closure is blocked while required approvals are Needs review, required evidence is missing, or open blocking risks lack disposition. - Target dates require an explicit date and timezone label; absent dates remain unscheduled. - A milestone dueAt cannot be earlier than its dependency dueAt unless the user confirms an exception note. - Generate workback tasks by subtracting declared duration and buffer from the milestone dueAt; do not infer durations. - Flag overdue, due today, due soon, blocked, and conflict states with text labels in addition to color. - Completed tasks retain completion time, actor label, revision, and prior dueAt. - Recurrence is only a candidate until a human confirms it; no automatic recurring external action is created. - Changing a milestone recalculates only local draft workback items and shows a change summary before save. - Agenda provider synchronization and external calendar writes remain held. ## Workback sequence - Create a local project record with canonical ID, origin, provenance, lifecycle, and source references. - Define the field guide scope, audience, prerequisites, exclusions, and uncertainty notes. - Attach source-labelled notes and file references; preserve locators, hashes, revisions, and custody state. - Add bounded guide steps and link each step to its supporting record or instrument reference. - Set the target review date and generate a workback from milestone duration, dependencies, and buffer days. - Review the workback in Projects, To-dos, and Agenda; show conflicts and overdue items without writing to an external provider. - Run designated educational instruments with explicit assumptions and save outputs as local receipts. - Open the project in PointGuard to show current step, next deadline, open loops, review state, and linked records. - Submit the guide for local approval; preserve Needs review, Approved, or Held state and reviewer receipt. - Revise the guide after feedback, increment the revision, and retain prior versions. - Show all unsupported publication, provider, credential, database, customer, and qualification effects as held. ## Scheduling records - milestone to-dos - deadline and workback entries - dependency records - agenda workback blocks ## Sources and evidence These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment. - `source_record:project:field-guide-build` - `project:field-guide-build` - `NotebookCollectionKind.project` - `NotebookTodoPayload.dueAt` - `Notebook records preserve canonical IDs, origin, source locators, source SHA-256, provenance, revision, lifecycle, tags, links, attachments, and record revisions.` - `Notebook Agenda deadlines/workbacks` - `/app/notebook/projects/` - `/app/notebook/field-guides/` - `/app/notebook/to-dos/` - `/app/notebook/agenda/` - `/app/notebook/files/` - `/app/notebook/approvals/` - `Notebook records canonical IDs, provenance, source locators, source SHA-256, revisions, lifecycle, tags, links, and attachments` - `PointGuard persistent cross-app context surface` - `APP_ROUTES:/app/notebook/projects/` - `APP_ROUTES:/app/notebook/field-guides/` - `APP_ROUTES:/app/notebook/to-dos/` - `APP_ROUTES:/app/notebook/agenda/` - `APP_ROUTES:/app/notebook/approvals/` - `APP_ROUTES:/app/pointguard/` - `ALLOWED_INSTRUMENTS:date-duration-calculator` - `ALLOWED_INSTRUMENTS:countdown-days-until-timer`