Update messaging for Migrations and Modernization and detail of engagement#247
Update messaging for Migrations and Modernization and detail of engagement#247brianamarie wants to merge 3 commits into
Conversation
…offer. Locks contracting (Percona wraps, license in engagement), keeps PACE as methodology only, and folds Michal assessment/package accuracy plus hypercare into the capability page. Co-authored-by: Cursor <cursoragent@cursor.com>
New File Governance CheckNo added markdown files detected. Doc Coverage CheckNo new markdown docs detected. Manual waiver commands (maintainers)
Waiver JSON is stored in a hidden PR comment ( Triggered by |
Messaging Smart Suggestions
Only auto-apply suggestions at high confidence with reviewer approval. Triggered by |
Messaging Impact Check
postgres-cost-claim (BLOCKING)PostgreSQL cost/TCO claims usually impact shared value proof messaging. Required review files:
Suggested additional scan:
licensing-or-open-source-claims (BLOCKING)License and open source positioning changes are cross-cutting. Required review files:
Suggested additional scan:
offering-name-or-tier-change (WARN)Offering naming updates should stay aligned across offering pages. Required review files:
Suggested additional scan:
product-messaging-module-touch (WARN)Product messaging modules often need checks against company framing and shared pillars or offerings. Required review files:
Suggested additional scan:
Manual waiver commands (maintainers):
Waiver state is stored in Triggered by |
Scope HexaCluster to proprietary exits (Oracle lead), add Percona accountability through hypercare, soften license wording, and cut false path-split / dual-vendor phrasing. Co-authored-by: Cursor <cursoragent@cursor.com>
Keep same-engine and MongoDB as Percona consulting unless assessment says otherwise, and align tooling copy with non-automated work scoped in assessment. Co-authored-by: Cursor <cursoragent@cursor.com>
Summary