Prompt 18 — Migration, content coherence, demo data, SEO, and release readiness

Required context

• All previous prompts
• Current production/deployment constraints
• Route migration and data migration plans
• External/internal wiki, pricing, entitlements, and release notes

Prompt

Prepare the enterprise uplift for controlled release. Do not add unrelated features.

1. Route and UI migration

• Implement redirects or compatibility routes.
• Preserve secure invite links and return URLs.
• Remove or gate deprecated prototype pages only after replacement acceptance.
• Remove raw JSON and development-only controls from production.
• Add deprecation notices and dates where external consumers are affected.

2. Data/schema migration

For every schema change:

• Forward migration
• Backfill plan
• Verification query/check
• Compatibility period
• Rollback or restore strategy
• Tenant-by-tenant impact
• Job observability
• Runbook

Test on production-like synthetic volume. Do not run destructive migrations without explicit approval.

3. Content coherence pass

Verify one glossary and one truth across:

• Marketing
• Pricing
• Documentation
• UI labels/help
• Emails/notifications
• API docs
• Release notes
• Internal specs

Remove implementation jargon such as console, wrapped survey, reseal envelope, and raw state names from normal user-facing copy unless intentionally documented.

Check feature status and plan claims against the live entitlement configuration.

4. Demo and sales environment

Create deterministic synthetic tenants representing:

• Free individual
• Team engineering organization
• Enterprise multi-unit organization
• Tenant with SSO/SCIM/integrations fixtures
• Imported Thomas report
• Active campaign with varied completion states
• Released result and active PDP

Use clearly fictitious people, domains, clients, and comments. Provide reset/reseed tooling. Do not use customer data.

Create role-specific demo sign-in or fixture instructions that cannot exist in production.

5. Marketing SEO and product links

• Validate titles, descriptions, canonical, sitemap, robots, social metadata
• Validate docs search index and contextual help links
• Check all CTAs and sign-in/upgrade handoffs
• Verify status/security/contact links
• Verify 404/403/500 and maintenance pages
• Check print/PDF/static export assets

6. Release notes and customer communication

Publish:

• Release summary by audience
• New navigation/workspaces
• Authentication/recovery changes
• Data/privacy changes
• Migration actions
• Deprecated routes/features
• Known limitations
• Support/contact path

Do not describe beta/planned work as generally available.

7. Operational readiness

• Deployment and rollback runbook
• Database migration runbook
• Tenant provisioning/offboarding runbook
• Authentication lockout runbook
• Notification/import/job failure runbooks
• Incident and support-access process
• Monitoring and alert ownership
• Support and escalation matrix

8. Final release review

Create a release checklist with owners and evidence for:

• Product acceptance
• Entitlements/pricing
• Security/privacy
• Accessibility
• Reliability/performance
• Documentation/content
• Billing/integrations
• Migration/rollback
• Support/operations
• Legal/marketing approval where required

Acceptance gates

• No dead routes, broken docs links, or unstyled exports.
• All public claims match live behavior and entitlements.
• Production contains no demo credentials, token-login UI, or synthetic fixture leakage.
• Migration and rollback have been rehearsed in a safe environment.
• Both wikis, traceability, ADRs, and release notes are current.