Source: https://guthlabs.ai/docs/project-templates/instrument-qualification/deadlines/ project template / candidate # Instrument qualification โ€” deadlines The distinct deadlines record for Instrument qualification. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: project:instrument-qualification **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 - Target completion date is required before the project can leave intake. - Every milestone must have an owner, planned finish, and exit criteria. - Every workback task must have an owner and dueAt; overdue tasks require a status update or revised due date with a reason. - Dependent work cannot be marked complete while a blocking dependency is unresolved unless an approved exception is linked. - Approval deadlines must precede closure by at least one review step. - Date changes preserve prior revisions and must not silently overwrite the original plan. - Provider, credential, database, customer, publication, and production effects remain Held unless separately verified and approved. - A review target date is optional at creation but required before a workback can be marked ready. - A task with a due date must show due, overdue, completed, or blocked state using the local clock and stored timestamp. - A workback must calculate dates deterministically from the review target, task duration or interval, dependencies, and declared buffer. - Conflicting or impossible milestone dates must produce an actionable warning and prevent readiness projection from treating the workback as complete. - Recurring tasks remain a proposal field only; no external recurrence is created. - Agenda changes are drafts until a human reviews them; no provider calendar write is performed. ## Workback sequence - Create the project record with a clear owner, scope, visibility, and review target. - Bind one or more instruments using exact verified directory slugs; reject unknown, disposed, or ambiguous slugs. - Record intended use, assumptions, limitations, and source references for every binding. - Create reproducible tests covering normal inputs, boundary inputs, invalid inputs, persistence, keyboard operation, and visible failure states. - Attach local file references or source locators as evidence without silently uploading or moving protected assets. - Convert failed or unresolved tests into owned hardening tasks with priorities, dependencies, due dates, and review signals. - Build a deadline workback from the review target and surface overdue, blocked, conflicting, and unscheduled work. - Review the PointGuard projection as a local readiness summary, clearly separating passed evidence, open risks, and unverified claims. - Submit the local decision for human approval; preserve revisions and receipts while holding publication, provider, credential, database, customer, and production effects. ## Scheduling records - milestone records - deadline and workback to-dos - dependency records - owner assignments - hardening task records - deadline and 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:instrument-qualification` - `project:instrument-qualification` - `NotebookCollectionKind.project` - `NotebookTodoPayload.dueAt` - `Notebook Agenda deadlines/workbacks` - `Observed native contract: records, PointGuard, web boundary` - `/app/notebook/projects/` - `/app/notebook/to-dos/` - `/app/notebook/agenda/` - `/app/notebook/approvals/` - `/app/notebook/files/` - `/app/notebook/field-guides/` - `/app/notebook/agent-logs/` - `Notebook records canonical IDs, origin, source locators, source SHA-256, provenance, revisions, lifecycle, tags, links, and attachments` - `PointGuard persistent cross-app context surface` - `/app/pointguard/`