# Voice.md - Chainguard

This document outlines Chainguard's brand communication style, tone, and patterns to ensure consistent and effective messaging across all platforms.

## Communication Style

### Overall Tone and Personality
Chainguard's voice is **Authoritative, Expert, and Forward-Thinking**. We are **Problem-Solvers** for complex security challenges, offering **Empowering** solutions to developers and security professionals. Our tone is professional yet direct, confident in our leadership in software supply chain and AI security.

### Key Stylistic Elements and Patterns
*   **Direct and Benefit-Oriented:** We clearly state problems and immediately follow with how Chainguard solves them, emphasizing outcomes.
*   **Data-Driven Credibility:** We frequently use quantifiable data, statistics, and SLAs to support our claims and demonstrate impact (e.g., "97.6% fewer CVEs," "1-Day KEV SLA").
*   **Strong, Action-Oriented Verbs:** We use verbs that convey decisive action and positive change ("Eliminate," "Prevent," "Secure," "Shrink," "Innovate," "Build").
*   **Clear and Concise Language:** We avoid unnecessary jargon where simpler terms suffice, but embrace precise technical vocabulary when appropriate for our audience.
*   **Structured Information:** We utilize headings, subheadings, bullet points, and numbered lists to break down complex topics into digestible content.
*   **Emphasis through Bold Text:** Key phrases, product names, and critical benefits are often bolded for immediate impact.

### Vocabulary Preferences and Word Choices
*   **Technical & Industry-Specific:** "CVEs," "CI/CD," "artifacts," "dependencies," "agent skills," "zero-days," "exploit gap," "remediation," "SLAs," "KEV," "supply chain security."
*   **Security-Focused:** "Malware," "vulnerability," "risk," "attack surface," "threat protection," "hardened," "resilient," "trusted."
*   **Solution-Oriented:** "Eliminate," "prevent," "protect," "secure," "build," "ship," "innovate."
*   **Positive & Assuring:** "Trusted," "safe," "secure," "resilient," "best-in-class."

## Content Patterns

### Common Themes and Topics
*   Software supply chain security (core focus).
*   AI security and emerging threats (e.g., "AI Exploit Gap").
*   Vulnerability management and CVE remediation.
*   Malware prevention and threat mitigation.
*   Open source security and trusted artifacts.
*   Developer efficiency and empowerment.
*   Compliance standards (FedRAMP, PCI DSS, CMMC, SOC 2).
*   Product announcements, innovations, and research.
*   Customer success stories and use cases.

### Structural Approaches to Content
*   **Problem-Solution Narrative:** Content typically identifies a significant industry challenge (e.g., "CVE remediation treadmill") and positions Chainguard as the definitive solution.
*   **Categorization:** Products and solutions are logically grouped (e.g., "Code safely with agents," "Build with trusted artifacts," "Ship through trusted CI").
*   **Modular Sections:** Content is divided into distinct, scannable sections with clear, benefit-driven headings.
*   **Evidence-Based:** Claims are frequently backed by customer testimonials, case studies, or statistical data.

### Call-to-Action Styles and Patterns
CTAs are direct, clear, and varied, encouraging different levels of engagement:
*   **Direct Action:** "Talk to an expert," "Start for free," "Browse all images."
*   **Informational:** "Read the story," "Learn more," "Download the report."
*   **Engagement:** "Contact us," "Log in," "Subscribe to our newsletter," "See open positions."
CTAs are strategically placed at the end of sections, within content, or prominently displayed on pages.

## Audience Interaction

### How the Brand Addresses Its Audience
We address our audience directly using "you" and "your" to create a personal connection, acknowledging their pain points and aspirations ("so your developers can just ship," "keeps your credentials out of attackers’ hands"). We assume a baseline understanding of technical concepts but strive for clarity.

### Level of Formality and Relationship Style
The relationship is that of a **Trusted Advisor and Expert Partner**. We maintain a professional, respectful, and serious tone appropriate for B2B enterprise security. We aim to instill confidence and reliability, empowering our audience to overcome security challenges.

### Engagement and Conversation Patterns
Our content is primarily informative and educational, designed to answer critical questions and provide solutions. We foster engagement through:
*   **Educational Resources:** Blog posts, "101" guides, courses, documentation.
*   **Community:** References to a "Slack Community" for direct interaction.
*   **Events:** Webinars and conferences to share insights and product updates.

## Guidelines & Examples

### Do's and Don'ts for Brand Communication

**Do's:**
*   **Be Authoritative:** Speak with confidence and expertise in security.
*   **Focus on Benefits:** Always connect features to tangible advantages for the user.
*   **Use Data:** Support claims with statistics, case studies, and quantifiable results.
*   **Be Direct & Clear:** Get straight to the point, avoiding ambiguity.
*   **Empower the Audience:** Frame solutions as enabling developers and teams.
*   **Maintain Consistency:** Use key terms like "trusted," "secure," "supply chain," "AI," "open source" consistently.

**Don'ts:**
*   **Avoid Overly Casual Language:** Maintain a professional and expert tone.
*   **Don't Be Vague:** Be specific about problems and solutions.
*   **Avoid Hype without Substance:** Back all claims with evidence or clear reasoning.
*   **Don't Over-simplify Technical Concepts:** Respect the intelligence of our technical audience while striving for clarity.

### Example Phrases and Expressions that are "On-Brand"
*   "Eliminate malware and vulnerability risk across your containers, dependencies, CI/CD actions, and AI agent skills so your developers can just ship."
*   "Chainguard lets you step off the CVE remediation treadmill to focus on building."
*   "Secure every application with container images that are rebuilt from source daily and sport best-in-class SLAs."
*   "Protect your open source infrastructure. Stop firefighting vulnerabilities and malware, and build a resilient supply chain with Chainguard."
*   "Access a trusted catalog of Python, Java, JavaScript, Go, and .NET packages so you can turn off live access to public registries."

### Content Types and Formats the Brand Uses
*   **Blog Posts:** Technical deep dives, product announcements, research reports, industry news.
*   **Marketing Copy:** Landing pages, solution overviews, benefit-driven narratives.
*   **Product Descriptions:** Features, benefits, use cases, technical specifications.
*   **Customer Stories/Case Studies:** Demonstrating real-world impact.
*   **Educational Resources:** "101" guides, online courses, documentation.
*   **Event Summaries & Announcements:** Highlighting key takeaways and upcoming engagements.
*   **Reports & Whitepapers:** In-depth analyses (e.g., Gartner Magic Quadrant, AI Exploit Gap report).