Operations migration — field guides

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.

Related field-guide records

No separate guide route is admitted for this project or job.

Source-proposed guide paths are references, not proof that those paths resolve.

Operating sequence

1. Create the project intake as a proposed local record with canonical ID, provenance, revision, lifecycle, and source references.
2. Name the project owner, operations owner, system owners, reviewers, approvers, backups, and record ownership boundaries.
3. Complete scope and record explicit exclusions, assumptions, cutover boundaries, reconciliation requirements, and rollback requirements.
4. Create milestones with deliverables, acceptance conditions, owners, predecessors, evidence requirements, and approval gates.
5. Set the target completion date and derive a dated workback for cutover, approvals, evidence, reconciliation, communications, and rollback decisions.
6. Register dependencies and assign each a required-by date, fallback, escalation owner, and blocking status.
7. Declare the observed Notebook, Agenda, To-dos, Files, Notes, Approvals, Projects, Field Guides, Agent Logs, and PointGuard surfaces used for local coordination.
8. Draft preparation, migration, reconciliation, rollback-test, and handoff procedures from available source-backed guides or mark the guide requirement held.
9. Create evidence requests before execution; require source labels, provenance, timestamps, conditions, expected results, observed results, and reviewer status.
10. Run a readiness review: scope approved, owners assigned, dependencies satisfied or accepted, deadlines scheduled, evidence plan complete, and rollback criteria explicit.
11. Hold cutover for human approval; do not treat an indexed or prototype app route as proof of provider, credential, database, customer, publication, or production connectivity.
12. Record migration and reconciliation evidence, including counts, samples or comparison method, discrepancies, disposition, and reviewer receipt.
13. Evaluate rollback triggers by the stated deadline; record a human decision to proceed, pause, roll back, or hold.
14. Complete handoff, close or reschedule unresolved deadlines, preserve revisions and receipts, and obtain final closure approval.

Handoff boundary

• Treating a named prototype or indexed route as a connected execution surface.
• Migrating incomplete or incorrectly scoped records without a reconciliation baseline.
• Unowned dependencies or deadline changes causing an unsafe cutover.
• Confusing local file references with uploaded or protected assets.
• Approving cutover without reproducible evidence, discrepancy disposition, or rollback criteria.
• Allowing an Agent or PointGuard context surface to override specialist-app canonical ownership.
• Publishing operational or customer claims from proposal-only records.
• Accessibility failures in long multi-section forms, date controls, status indicators, or error handling.

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
• Observed native contract: project_and_field_guide_collections
• Observed native contract: deadlines
• Observed native contract: records
• Observed native contract: pointguard
• Observed native contract: web_boundary
• App route: /app/notebook/projects/
• App route: /app/notebook/to-dos/
• App route: /app/notebook/agenda/
• App route: /app/notebook/approvals/
• App route: /app/notebook/files/
• App route: /app/notebook/notes/
• App route: /app/notebook/field-guides/
• App route: /app/notebook/agent-logs/
• App route: /app/pointguard/
• 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/