Skip to content

Update messaging for Migrations and Modernization and detail of engagement#247

Open
brianamarie wants to merge 3 commits into
mainfrom
revise/pace-michal-feedback
Open

Update messaging for Migrations and Modernization and detail of engagement#247
brianamarie wants to merge 3 commits into
mainfrom
revise/pace-michal-feedback

Conversation

@brianamarie

Copy link
Copy Markdown
Collaborator

Summary

  • Reframe public Migration and Modernization as a Percona + HexaCluster combined offer (outcomes: migration expertise, PM, follow-on support); no delivery RACI; no HexaRocket.
  • Lock contracting: customer contracts with Percona; migration software license is part of the engagement.
  • Keep PACE as in-program methodology only; durable public frame is Migration and Modernization (sidebar + page).
  • Apply Michal technical accuracy: assessment = feasibility/scope/cost; package list includes app layer, CDC, training, hypercare, and 24×7 Expert Support; broader targets including MongoDB; EOL/ELS split from PACE in consulting; remove downtime-as-assessment claim on PostgreSQL; tighten ELS cost copy.

…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>
@brianamarie
brianamarie requested a review from Cinneely as a code owner July 23, 2026 10:06
@github-actions

Copy link
Copy Markdown
Contributor

New File Governance Check

No added markdown files detected.

Doc Coverage Check

No new markdown docs detected.

Manual waiver commands (maintainers)

  • /governance-ok all or /governance-all
  • /governance-ok new-file, /governance-ok doc-coverage
  • /governance-reset all or /governance-reset with the same token

Waiver JSON is stored in a hidden PR comment (messaging-governance-waiver-data:v1), same pattern as Impact Check.


Triggered by pull_request. Workflow content-governance-checks.yml. Docs: AUTOMATION.md, automation/README.md.

@github-actions

Copy link
Copy Markdown
Contributor

Messaging Smart Suggestions

File Why impacted Claim Confidence
use-cases-value-pillars/cost-optimization.md PostgreSQL cost/TCO claims usually impact shared value proof messaging. cost 0.65
framework/core-positioning.md PostgreSQL cost/TCO claims usually impact shared value proof messaging. cost 0.95
products/postgresql/messaging.md PostgreSQL cost/TCO claims usually impact shared value proof messaging. cost 0.65
reference/canonical-naming.md License and open source positioning changes are cross-cutting. cost 0.65
reference/banned-terms.md License and open source positioning changes are cross-cutting. cost 0.95
framework/core-positioning.md License and open source positioning changes are cross-cutting. cost 0.95
framework/why-percona.md License and open source positioning changes are cross-cutting. cost 0.95
offerings/expert-support/messaging.md License and open source positioning changes are cross-cutting. cost 0.95
offerings/expertops/messaging.md License and open source positioning changes are cross-cutting. cost 0.95
offerings/expert-consulting/messaging.md License and open source positioning changes are cross-cutting. cost 0.65
offerings/expert-support/messaging.md Offering naming updates should stay aligned across offering pages. cost 0.95
offerings/expertops/messaging.md Offering naming updates should stay aligned across offering pages. cost 0.95
offerings/expert-consulting/messaging.md Offering naming updates should stay aligned across offering pages. cost 0.65
reference/canonical-naming.md Offering naming updates should stay aligned across offering pages. cost 0.65
framework/core-positioning.md Offering naming updates should stay aligned across offering pages. cost 0.95
framework/core-positioning.md Product messaging modules often need checks against company framing and shared pillars or offerings. cost 0.95
framework/why-percona.md Product messaging modules often need checks against company framing and shared pillars or offerings. cost 0.95

Only auto-apply suggestions at high confidence with reviewer approval.


Triggered by pull_request. Workflow smart-suggestions.yml. Docs: AUTOMATION.md, automation/README.md.

@github-actions

Copy link
Copy Markdown
Contributor

Messaging Impact Check

  • Changed files: 7

postgres-cost-claim (BLOCKING)

PostgreSQL cost/TCO claims usually impact shared value proof messaging.

Required review files:

  • use-cases-value-pillars/cost-optimization.md
  • framework/core-positioning.md
  • products/postgresql/messaging.md

Suggested additional scan:

  • use-cases-value-pillars/*.md

licensing-or-open-source-claims (BLOCKING)

License and open source positioning changes are cross-cutting.

Required review files:

  • reference/canonical-naming.md
  • reference/banned-terms.md
  • framework/core-positioning.md
  • framework/why-percona.md
  • offerings/expert-support/messaging.md
  • offerings/expertops/messaging.md
  • offerings/expert-consulting/messaging.md

Suggested additional scan:

  • use-cases-value-pillars/*.md
  • products/**/messaging.md

offering-name-or-tier-change (WARN)

Offering naming updates should stay aligned across offering pages.

Required review files:

  • offerings/expert-support/messaging.md
  • offerings/expertops/messaging.md
  • offerings/expert-consulting/messaging.md
  • reference/canonical-naming.md
  • framework/core-positioning.md

Suggested additional scan:

  • products/**/messaging.md
  • use-cases-value-pillars/*.md

product-messaging-module-touch (WARN)

Product messaging modules often need checks against company framing and shared pillars or offerings.

Required review files:

  • framework/core-positioning.md
  • framework/why-percona.md

Suggested additional scan:

  • use-cases-value-pillars/*.md
  • offerings/*.md

Manual waiver commands (maintainers):

  • /impact-ok all (optional same-line note after all is ignored)
  • /impact-all (same as /impact-ok all)
  • /impact-ok <exact missing path>
  • /impact-reset all
  • /impact-reset <exact missing path>

Waiver state is stored in <!-- messaging-impact-waiver-data:v1 -->.


Triggered by pull_request. Workflow impact-check.yml. Docs: AUTOMATION.md, automation/README.md.

brianamarie and others added 2 commits July 23, 2026 12:20
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant