# voice.md

## Communication Style

### Overall Tone and Personality
Endor Labs communicates with an **authoritative, expert, and solution-oriented** tone. The brand is confident and direct, positioning itself as a leader in AppSec, AI, and software supply chain security. The personality is professional and empowering, focused on enabling technical teams to achieve both speed and security without compromise.

### Key Stylistic Elements and Patterns
*   **Problem-Solution Framing:** Content frequently starts by outlining a significant challenge faced by security and engineering teams, then presents Endor Labs' offering as the definitive solution.
    *   *Example:* "Problem: Every coding agent has the same blind spots" followed by "Solution: Secure code from generation to production."
*   **Direct and Impactful Language:** Headlines and key statements are concise and powerful, often using strong verbs and benefit-driven phrasing.
    *   *Example:* "Speed AND security. The best teams code without compromise."
*   **Structured Information:** Content is well-organized with clear headings, subheadings, and bullet points, making complex technical information digestible.
*   **Emphasis on "No Compromise":** A recurring theme is the ability to achieve security without sacrificing developer velocity or innovation.

### Vocabulary Preferences and Word Choices
*   **Technical & Industry-Specific:** Utilizes precise terminology relevant to AppSec, AI, and software development, such as "AppSec," "AI Coding Agents," "OSS," "SAST," "SCA," "SBOM," "CI/CD," "supply chain," "agentic," "vulnerabilities," "remediation," "compliance," "MCP," and "CLI."
*   **Action-Oriented Verbs:** Employs verbs that convey control, efficiency, and impact: "govern," "unify," "block," "verify," "fix," "flag," "enforce," "inventory," "learn," "scale."
*   **Benefit-Driven Language:** Focuses on outcomes for the user: "without compromise," "secure from the start," "without slowing builders down," "unified," "enhanced," "more personal."
*   **Risk & Security Terms:** Directly addresses threats and vulnerabilities: "blind spots," "sensitive data," "credentials," "unsafe commands," "insecure patterns," "malicious package," "secrets," "leaked," "attacks."

## Content Patterns

### Common Themes and Topics
*   **AI in AppSec & Governance:** Securing AI coding agents, models, and their actions.
*   **Software Supply Chain Security:** Managing open source dependencies, detecting malicious packages, CI/CD security, and SBOM compliance.
*   **Agentic Remediation:** Automated identification and fixing of security issues.
*   **Compliance & Industry Solutions:** Addressing specific regulatory requirements (CRA, FedRAMP, ISO 42001, PCI DSS, SOC 2) and industry needs.
*   **Research & Risk Intelligence:** Providing insights into vulnerabilities and emerging threats.

### Structural Approaches to Content
*   **Categorized Navigation:** Website content is clearly segmented into "Product," "AI Governance," "AI Code," "Open Source," "Supply Chain," "Solutions," and "Research," allowing users to quickly find relevant information.
*   **Feature/Benefit Breakdown:** Product descriptions often list features alongside the benefits they provide to the user.
*   **Educational & Informative:** Blog posts and research hubs aim to educate the audience on complex security topics and best practices.

### Call-to-Action Styles and Patterns
CTAs are direct, clear, and action-oriented, prompting users to engage with the product or learn more. They are strategically placed after key value propositions.
*   **Primary CTAs:** "Book a Demo," "Start Free Trial."
*   **Secondary CTAs:** "Learn more," "Explore resource kit."

## Audience Interaction

### How the Brand Addresses its Audience
The brand addresses its audience as **technical professionals** – "security and engineering teams," "builders," "developers," "architects." It speaks to their challenges and aspirations, acknowledging their expertise while offering superior solutions.

### Level of Formality and Relationship Style
The relationship is **professional and expert-to-expert**. While not overly formal, the language maintains a high degree of precision and seriousness appropriate for critical security discussions. The brand positions itself as a trusted partner and authority in a complex domain.

### Engagement and Conversation Patterns
Engagement is direct and focused on providing value. The brand doesn't shy away from technical depth but ensures clarity. The conversation is geared towards solving pressing security problems efficiently, implying a shared understanding of the technical landscape.

## Guidelines & Examples

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

**Do's:**
*   **Be Precise and Technical:** Use accurate industry terminology.
*   **Frame as Problem/Solution:** Clearly articulate the challenge and how Endor Labs solves it.
*   **Emphasize "No Compromise":** Highlight the ability to achieve both speed and security.
*   **Be Direct and Action-Oriented:** Use strong verbs and clear calls to action.
*   **Maintain an Authoritative Tone:** Convey expertise and confidence.
*   **Structure for Clarity:** Use headings, subheadings, and lists to organize information.

**Don'ts:**
*   **Avoid Casual Language:** Steer clear of slang, overly informal expressions, or overly conversational tones.
*   **Don't Be Vague:** Avoid ambiguous statements or generalizations.
*   **Don't Oversimplify:** While clear, don't dilute technical concepts to the point of losing meaning for a technical audience.
*   **Avoid Sensationalism:** Focus on factual benefits and proven solutions rather than hype.

### Example Phrases and Expressions that are "On-Brand"
*   "Speed AND security. The best teams code without compromise."
*   "Unified AppSec across AI, code, OSS & containers."
*   "Secure code from generation to production."
*   "Your policy is enforced at the moment of action, and the audit trail comes with it."
*   "AURI helps agents write secure code from the start and governs the actions they take, without slowing builders down."
*   "Every coding agent has the same blind spots."
*   "Block malicious packages before install, verify code is secure, fix vulnerabilities, and flag secrets before they’re leaked."

### Content Types and Formats the Brand Uses
*   **Blog Posts:** In-depth articles on industry trends, technical insights, and best practices.
*   **Product Overviews & Feature Pages:** Detailed explanations of platform capabilities and benefits.
*   **Solution Pages:** Tailored content addressing specific use cases (e.g., AI Code Security, Software Supply Chain Security).
*   **Research Reports & Hubs:** Original research, benchmarks, and threat intelligence.
*   **Case Studies:** Demonstrating real-world success stories.
*   **Documentation:** Technical guides and how-tos.
*   **Compliance Guides:** Resources related to industry regulations.