Elevate no charge on runtime in company and cost messaging

[brianamarie]

Summary

• Add no charge on runtime language to company framing (framework/why-percona.md, core-positioning.md, executive-summary.md) as a factual contrast with per-core and consumption-based proprietary/DBaaS licensing, without elevating it as an objective "core differentiator" label.
• Expand the cost optimization pillar with a dedicated runtime-licensing solution bullet and sharper problem/use-case wording around license drag at runtime.
• Separate software economics (no runtime license fees) from services economics (Expert Support and ExpertOps scale with deployment scope, without per-core database licensing or license gates on the software).

Scope and non-goals

• PF-approved company descriptor in core-positioning.md is unchanged.
• No product-level (products/*/messaging.md) or reference/canonical-naming.md updates in this PR.

Made with Cursor

[github-actions]

Messaging Smart Suggestions

File	Why impacted	Claim	Confidence
framework/core-positioning.md	Core framework story files usually need mutual consistency and may warrant aligned product or offering language.	cost	0.65
framework/why-percona.md	Core framework story files usually need mutual consistency and may warrant aligned product or offering language.	cost	0.65
framework/executive-summary.md	Core framework story files usually need mutual consistency and may warrant aligned product or offering language.	cost	0.65

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]

New File Governance Check

No added markdown files detected.

Doc Coverage Check

No new markdown docs detected.

Duplicate Detector

• Changed markdown docs: 4

No significant overlap detected.

Manual waiver commands (maintainers)

• /governance-ok all or /governance-all
• /governance-ok new-file, /governance-ok doc-coverage, /governance-ok duplicate
• /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]

Messaging Impact Check

• Changed files: 4

framework-story-touch (WARN)

Core framework story files usually need mutual consistency and may warrant aligned product or offering language.

Required review files:

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

Suggested additional scan:

• offerings/*.md
• use-cases-value-pillars/*.md
• products/**/messaging.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.}