Skip to content

Integrate Valkey/Redis fact-sheet guidance into product messaging#186

Open
brianamarie wants to merge 6 commits into
mainfrom
docs/valkey-redis-fact-sheet-messaging
Open

Integrate Valkey/Redis fact-sheet guidance into product messaging#186
brianamarie wants to merge 6 commits into
mainfrom
docs/valkey-redis-fact-sheet-messaging

Conversation

@brianamarie

@brianamarie brianamarie commented Jun 9, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Integrates internal Valkey/Redis 5W1H fact-sheet guidance into products/valkey-redis/messaging.md within the existing four-pillar structure.
  • Reframes the opener for platform, SRE, and DevOps buyers; notes that DBAs rarely own these clusters unlike other Percona engines.
  • Adds TCO and performance bullets for memory-driven infrastructure cost, caching as operational infrastructure, and primary-database load relief.
  • Extends operational tuning and Future freedom copy for interchangeability, adoption paths, and consulting scope (architecture and design, migration, health assessments).
  • Adds sales enablement with conversation starters and public resources only.

Out of scope

  • Value-pillar propagation (use-cases-value-pillars/*)
  • Framework-branch Valkey edits (Valkey 9.0 security bullet, enterprise-controls reword, PMM hedging cleanup)
  • Launch/availability framing ("available yesterday")

Made with Cursor

@brianamarie
brianamarie force-pushed the docs/valkey-redis-fact-sheet-messaging branch from ff7eb7c to 71a19a6 Compare June 9, 2026 09:55
@github-actions

github-actions Bot commented Jun 9, 2026 •
edited
Loading

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

github-actions Bot commented Jun 9, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

{
"all": true,
"paths": [],
"reset_paths": []
}

@github-actions

github-actions Bot commented Jun 9, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Messaging Smart Suggestions

File Why impacted Claim Confidence
reference/canonical-naming.md License and open source positioning changes are cross-cutting. cost 0.95
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.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.

@brianamarie brianamarie added Content & messaging Canonical copy, products, use cases, case studies, and narrative. Needs: product or GTM Product, marketing, or GTM should confirm scope, naming, or positioning. Area: Valkey/Redis Valkey and Redis ecosystem messaging (products/valkey-redis/). labels Jun 11, 2026
@brianamarie
brianamarie requested a review from stockholmux June 11, 2026 11:39
brianamarie and others added 2 commits June 30, 2026 13:30
@brianamarie @cursoragent
Integrate Valkey/Redis fact-sheet positioning into product messaging.
9e54c39 
Fold internal 5W1H guidance into the existing pillar structure: platform/SRE ownership, caching as production infrastructure, memory-cost pressure, primary-database offload, and sales conversation starters.

Co-authored-by: Cursor <cursoragent@cursor.com>
@brianamarie @cursoragent
Propagate Valkey/Redis fact-sheet scenarios into value pillars.
3877d36 
Add in-memory cache infrastructure spend and production cache tier operations use cases so cross-portfolio pillar copy reflects the product messaging updates.

Co-authored-by: Cursor <cursoragent@cursor.com>
@brianamarie
brianamarie force-pushed the docs/valkey-redis-fact-sheet-messaging branch from c37cb0e to 3877d36 Compare June 30, 2026 11:31
@brianamarie

brianamarie commented Jul 2, 2026

Copy link
Copy Markdown
Collaborator Author

/impact-ok all

@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

🤖 Recorded /impact-ok all. Re-running Impact Check with updated waivers.

@github-actions

github-actions Bot commented Jul 2, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Messaging Impact Check

  • Changed files: 4

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

License and open source positioning changes are cross-cutting.

Required review files:

  • reference/canonical-naming.md (waived — /impact-ok)
  • reference/banned-terms.md (waived — /impact-ok)
  • framework/core-positioning.md (waived — /impact-ok)
  • framework/why-percona.md (waived — /impact-ok)
  • offerings/expert-support/messaging.md (waived — /impact-ok)
  • offerings/expertops/messaging.md (waived — /impact-ok)
  • offerings/expert-consulting/messaging.md (waived — /impact-ok)

Suggested additional scan:

  • use-cases-value-pillars/*.md
  • products/**/messaging.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 (waived — /impact-ok)
  • framework/why-percona.md (waived — /impact-ok)

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.

thefactremains
thefactremains previously approved these changes Jul 4, 2026
View reviewed changes

@thefactremains thefactremains left a comment •
edited
Loading

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@brianamarie brianamarie added the MISSING TIMELINE No concrete target date, release gate, or explicit no-hard-date decision in the body. label Jul 7, 2026
@brianamarie brianamarie added the Roadmap: soon High confidence next; right after or alongside launch prep. label Jul 21, 2026
@brianamarie brianamarie mentioned this pull request Jul 21, 2026
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@thefactremains thefactremains thefactremains left review comments
@stockholmux stockholmux Awaiting requested review from stockholmux
@Cinneely Cinneely Awaiting requested review from Cinneely
@obiyduhata obiyduhata Awaiting requested review from obiyduhata
@DavePoole30 DavePoole30 Awaiting requested review from DavePoole30
@tichomir tichomir Awaiting requested review from tichomir

At least 1 approving review is required to merge this pull request.

Assignees

@stockholmux stockholmux

Labels

Area: Valkey/Redis Valkey and Redis ecosystem messaging (products/valkey-redis/). Content & messaging Canonical copy, products, use cases, case studies, and narrative. MISSING TIMELINE No concrete target date, release gate, or explicit no-hard-date decision in the body. Needs: product or GTM Product, marketing, or GTM should confirm scope, naming, or positioning. Roadmap: soon High confidence next; right after or alongside launch prep.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@brianamarie @thefactremains @stockholmux