Source: https://guthlabs.ai/docs/project-templates/operations-migration/deadlines/ project template / candidate # Operations migration โ€” deadlines The distinct deadlines record for Operations migration. This page is proposal-only. Status: **proposed**Lifecycle: **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. ## Deadline and workback rules - Every milestone and dependency must have an owner and a due date or an explicit held-date reason. - The workback must include target completion, cutover, approval, evidence, reconciliation, rollback-decision, communication, and handoff dates. - A date change requires a reason, affected milestones, owner confirmation, and a new revision. - A missed blocking deadline changes the relevant milestone or project state to Held until reviewed. - No cutover approval is valid without the required evidence set and recorded reconciliation method. - Rollback readiness must be reviewed before cutover and again at the stated rollback decision deadline. - Recurring deadlines are only candidates until a human confirms recurrence. - External calendar, message-send, provider, credential, database, customer, publication, and production effects remain held. - Migration deadline is required before approval submission. - Freeze deadline must be on or before the migration deadline. - Reconciliation deadline must precede the rollback decision deadline. - Every workback task must have an owner, due date, and completion state. - Overdue tasks are flagged locally and do not trigger notifications or external changes. - A missing or ambiguous deadline produces a blocking validation state. - Changing a deadline creates a revision and preserves the previous value. - Conflicting workback dates are shown in Agenda for human resolution. ## Workback sequence - Create a local project record and assign a migration owner. - Define the source and target system labels, scope, success criteria, and explicit non-goals. - Attach or link source-labelled and target-labelled evidence using local file references; do not upload or fetch protected data. - Record baseline counts, fields, states, and known gaps for each side. - Set the migration, freeze, reconciliation, and rollback decision deadlines. - Generate a workback of preparation, dry-run, reconciliation, review, and rollback-readiness tasks. - Run a locally staged comparison against manually entered or locally referenced evidence. - Classify every difference as accepted, resolved, unresolved, or requires review. - Record rollback triggers, steps, owner, and evidence requirements before approval. - Submit the migration proposal to local Approvals with a receipt and revision history. - Project phase, deadline health, unresolved discrepancies, and held effects into PointGuard. - Keep any provider, credential, database, customer, publication, or production change held for human action. ## Scheduling records - milestone records - deadline and workback to-dos - dependency records - owner assignments - migration workback todo records ## 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/`