Incident response — deadlines

Record status

Record ID

project:incident-response

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

• Every deadline must include dueAt and timezone, owner, priority, completion state, and linked milestone or task.
• A workback must include an anchor, ordered tasks, latest starts, buffers, and a replan trigger.
• Overdue items remain visible in Today and To-dos until completed, explicitly waived, or superseded with a revision receipt.
• A recurrenceCandidate may be recorded only as a review signal; no recurring external action is implied.
• A deadline conflict blocks approval of the affected workback until an owner records a resolution or accepted risk.
• Closure cannot be proposed while any critical blocker, unreviewed approval, missing recovery evidence, or overdue required follow-up remains.
• Every response task must have an explicit dueAt or be marked no-deadline with a reason.
• The project must show the earliest open due item, overdue count, and next human action.
• A workback must be calculated from the declared recovery or review deadline; intermediate dates remain drafts until confirmed.
• Dependencies must block downstream tasks from appearing complete when a prerequisite is open.
• Conflicting or missing deadlines must produce a visible review state rather than silent rescheduling.
• Recurring tasks are proposal-only and require human confirmation before recurrenceCandidate is accepted.
• Agenda changes, reminders, provider writes, and external notifications remain held.

Workback sequence

1. Create the incident project and assign an owner; leave lifecycle and status visibly editable.
2. Record the detection signal, affected scope, confidence, and source links without converting assumptions into facts.
3. Choose the current response phase and add ordered tasks for assessment, containment, evidence preservation, recovery, and retrospective work.
4. Set explicit task owners, priorities, dependencies, dueAt values, and review-required flags.
5. Link notes, file references, messages, approvals, and Agent logs to the project using canonical record IDs.
6. Open the project in PointGuard to project current phase, overdue work, pending approvals, unresolved questions, and next action.
7. Draft communications or schedule changes for human review; keep send, provider writes, publication, and customer-facing effects held.
8. Mark work complete only with a completion note or linked evidence; preserve revisions rather than overwriting prior state.
9. Close or hold the project after recovery review and create the retrospective record with follow-up deadlines.

Scheduling records

• milestone records
• deadline and workback to-dos
• dependency records
• owner assignments
• project record with canonical ID, lifecycle, owner, severity, status, timestamps, links, and revision history

Sources and evidence

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

• source_record:project:incident-response
• project:incident-response
• NotebookCollectionKind.project
• NotebookTodoPayload.dueAt
• Notebook Agenda deadlines/workbacks
• Notebook records canonical IDs, origin, source locators, source SHA-256, provenance, revision, lifecycle, tags, links, attachments, and record revisions
• PointGuard persistent cross-app context surface
• APP_ROUTES:/app/notebook/projects/
• APP_ROUTES:/app/notebook/to-dos/
• APP_ROUTES:/app/notebook/agenda/
• APP_ROUTES:/app/notebook/files/
• APP_ROUTES:/app/notebook/approvals/
• APP_ROUTES:/app/notebook/messages/
• APP_ROUTES:/app/notebook/agent-logs/
• APP_ROUTES:/app/pointguard/
• Notebook records provenance and revision contract