Incident response — tools

The distinct tools record for Incident response. This page is proposal-only.

Status: proposedLifecycle: candidate

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.

Authoritative app_features lane tools and interfaces

Canonical tools-page assignments

Notebook Projects (interface · required) — Owns local project grouping, state, links, and evidence inspection.
Notebook To-dos (interface · required) — Owns due dates, priorities, completion state, tags, and review signals.
Notebook Agenda (interface · required) — Provides source-bound deadlines, workbacks, and conflict review while external calendar writes remain held.
Notebook Files (interface · required) — Keeps source-labelled file references beside the incident without implying upload or protected storage.
Notebook Messages (interface · required) — Prepares communications with recipients and source context while final send remains human-held.
Notebook Approvals (interface · required) — Separates proposed decisions from approved or held decisions and preserves receipts.
PointGuard (interface · required) — Projects current incident context across linked Notebook surfaces without taking canonical-record ownership.
Notebook Agent Logs (interface · required) — Makes bounded assistance, authority, receipts, and current state inspectable.

Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved.

Authoritative lane instrument assignments

Canonical tools-page assignments

No verified instrument is assigned to this tools lane.

An instrument listed only for another lane does not become a tools-page assignment.

Use boundary

Treating a proposed assessment as a confirmed incident fact.
Overwriting evidence, timeline notes, or task history instead of preserving revisions.
Assigning or displaying sensitive incident material to the wrong local visibility scope.
Calculating deadlines in the wrong timezone or silently changing confirmed dates.
Allowing an unresolved dependency or missing evidence to appear complete.
Confusing a draft message, agenda change, or approval with an external action.
Projecting stale data in PointGuard without showing its revision or last-updated state.
Using color alone to communicate severity, overdue state, or approval state.
Implying provider connection, database authority, customer indexing, publication, or production qualification.
Using an Agent proposal as an autonomous containment, recovery, communication, or deletion action.

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 provenance and revision contract
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/messages/
APP_ROUTES:/app/notebook/approvals/
APP_ROUTES:/app/pointguard/