Operations migration — tools

The distinct tools record for Operations migration. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID: project:operations-migration
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 the local project grouping, lifecycle, links, and evidence view.
Notebook Agenda (interface · required) — Displays deadlines, conflicts, and drafted workback schedule changes without provider writes.
Notebook To-dos (interface · required) — Stores due dates, priority, completion state, tags, revisions, and deadline views.
Notebook Files (interface · required) — Stores local file references and metadata beside evidence without hidden upload.
Notebook Approvals (interface · required) — Provides explicit Needs review, Approved, and Held states with receipts.
Notebook Agent Logs (interface · required) — Makes Agent authority, current work, and receipts inspectable.
PointGuard (interface · required) — Carries the current migration context and projection across the app family.
Checksum Verifier (provider · optional) — May verify a manually supplied evidence checksum locally; it must not imply source-system access.

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

checksum-verifieroptional · Verify manually supplied evidence file checksums and preserve the result as a local receipt.date-duration-calculatorrequired · Calculate explicit intervals between migration, freeze, reconciliation, and rollback decision deadlines.

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

Use boundary

Manual evidence may be incomplete, stale, duplicated, or mislabelled.
A local comparison can be mistaken for a live system reconciliation.
Deadline projections can create false confidence when dependencies or estimates are missing.
Rollback evidence may be insufficient even when the checklist is marked complete.
Checksum verification does not establish provenance or production authority.
Sensitive operational details may be exposed through local files, links, or PointGuard context.
Browser storage can be cleared, unavailable, or inconsistent across devices.
Agents or users may mistake staged approvals for permission to execute external effects.
A migration can proceed with unresolved discrepancies if review gates are bypassed.

Sources and evidence

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

source_record:project:operations-migration
NotebookCollectionKind.project
NotebookTodoPayload.dueAt
Notebook Agenda deadlines/workbacks
Notebook records canonical IDs, provenance, revisions, links, and attachments
PointGuard persistent cross-app context surface
APP_ROUTES /app/notebook/projects/
APP_ROUTES /app/notebook/agenda/
APP_ROUTES /app/notebook/to-dos/
APP_ROUTES /app/notebook/approvals/
APP_ROUTES /app/notebook/files/
APP_ROUTES /app/notebook/agent-logs/
APP_ROUTES /app/pointguard/