# Sonar Brand Voice

> Authoritative, technical, and rigorous, positioning itself as the essential "trust layer" for the era of AI-generated code.

## Positioning
Sonar is the global leader in code verification, providing a neutral and independent platform for developers and enterprises to govern technical debt and security. It serves as the single source of truth for code quality in the "agentic era," ensuring that both human and AI-generated code meet rigorous standards.

## Voice principles
*   **Authoritative:** Uses definitive language and industry-standard validation (Gartner, Fortune 100) to establish market leadership.
*   **Rigorous:** Focuses on precision, technical depth, and "zero trust" verification rather than vague promises of "better" code.
*   **Forward-looking:** Frames the conversation around the "agentic era" and "Agent Centric Development," positioning the brand as the solution to modern AI-driven challenges.
*   **Objective:** Maintains a neutral, independent stance that prioritizes "clear paper trails" and "audit-ready" compliance.

## Tone by context
| Context | Tone |
|---|---|
| Marketing Hero | High-level, strategic, and urgent (e.g., "The age of agentic development is here"). |
| Product Features | Functional and benefit-oriented (e.g., "Prevent risk before it compounds"). |
| Technical Resources | Educational and granular (e.g., "How SonarQube traces a SQL injection"). |
| Social Proof | Validating and scale-focused (e.g., "Trusted by over 7M developers"). |

## Lexicon
- **Use:** Agentic era, code verification, trust layer, zero trust, multilayered review, single source of truth, technical debt, agent-centric development, neutral, rigorous.
- **Avoid:** Not evident from captured copy (though the brand avoids flowery, non-technical adjectives).

## Messaging do's and don'ts
*   **Do:** Use specific data points and percentages to prove value (e.g., "44% lower AI outage risk").
*   **Do:** Connect code quality directly to security and compliance (e.g., "audit-ready," "SAST," "SCA").
*   **Do:** Position AI as a risk that requires a "verification layer" to be used safely.
*   **Don't:** Use passive language; use active verbs like "Adopt," "Prevent," "Standardize," and "Stay."
*   **Don't:** Focus solely on human developers; always include the role of AI agents in the modern workflow.

## Evidence
*   "Code verification tuned for the agentic era"
*   "An independent trust layer for AI code"
*   "Sonar provides a neutral, rigorous verification platform"
*   "Governing technical debt when the author is an AI"
*   "The Agent Centric Development Cycle (AC/DC)"