Reignsound™ Voice

Purpose

The Reignsound™ Voice makes communication recognizable, accurate, and consistent. It gives writers, editors, product teams, and automated systems a shared reference instead of relying on informal preferences.

Core principles

• Name Reignsound™ directly. Prefer “Reignsound™” as the subject when describing the enterprise, its policies, systems, decisions, or activities. Reignsound™ is an organization and system of brands—not a group of people speaking as “we.”
• Use direct, specific language. Say what exists, what it does, what is planned, and what remains unavailable. Avoid vague promises and inflated claims.
• Distinguish fact from intention. Do not present a proposal, prototype, or planned capability as an implemented service.
• Name concepts deliberately. Named concepts such as Reignsound™ Voice and Reignsound™ Web should retain consistent spelling and capitalization so they can be referenced in articles, documentation, and systems.
• Keep public language accessible. Explain specialized terms when they first matter. Put detailed implementation material in technical references rather than overloading public summaries.
• Respect the audience. Invitations should make the next action clear. Claims about support, charitable work, donations, signup, or services must reflect what is actually available.

Preferred usage

• Prefer “Support Reignsound™” over “Support Our Mission.”
• Prefer “Reignsound™ supports charitable efforts” over “We support charitable efforts.”
• Prefer “Reignsound™ is developing…” when a capability is in development, and “Reignsound™ provides…” only when it is available.
• Use “Reignsound™ Voice” as the standard’s proper name; use “the Reignsound™ Voice standard” when clarity requires it.

Scope and status

This public page defines initial communication principles. More detailed editorial rules, terminology records, localization guidance, and automated checks may be added when a concrete need arises. The existence of this page does not imply every website or publication has already been audited against the standard.