Public Trust Surface

Editorial Standards for Public Prism Content

Prism publishes marketing pages, product documentation, blog posts, and machine-readable summaries. This page explains the standards we use to keep those surfaces useful, current, and internally consistent.

Core standards

  • Pages should make the intended audience clear: seller, agency, or mixed operator audience.
  • Commercial claims should stay aligned with the live product positioning, pricing page, and public documentation.
  • Tactical guidance should prefer direct, operational language over vague marketing language.
  • Public content should explain tradeoffs and limits, not only benefits.
  • Updates should preserve consistency across docs, blog posts, landing pages, and machine-readable summaries such as llms.txt.

What we check before or during updates

Positioning consistency

We review whether a page matches current Prism positioning, including transparent AI, guided workflow, and approval-first control.

Operational usefulness

We prefer content that helps a reader decide what to do next, not just what to believe. That includes use cases, constraints, and practical examples when available.

Freshness and revision

Pages are updated when positioning, workflows, pricing, or product behavior changes enough to make older descriptions misleading.

Machine-readable alignment

Public summaries, route metadata, and trust pages should stay synchronized so search engines and answer engines retrieve the same core story.