# voice.md

## Communication Style

### Overall Tone and Personality
Heeler's voice is **authoritative, confident, and urgent**, yet remains **precise and solution-oriented**. It projects the image of a knowledgeable expert and a decisive problem-solver in a rapidly evolving, high-stakes domain. There's a pragmatic efficiency to the language, emphasizing speed, automation, and deterministic outcomes, with a touch of bold, almost dramatic framing when articulating the challenges of AI security.

### Key Stylistic Elements and Patterns
*   **Direct and Concise:** Uses short, impactful sentences and phrases to convey complex ideas quickly.
    *   *Example:* "Prevent. Fix. Operate." "Machine-speed security for AI-written code."
*   **Problem-Solution Framing:** Consistently identifies a pressing security challenge (e.g., AI destroying constraints, attackers weaponizing flaws) before positioning Heeler as the definitive, efficient solution.
*   **Emphasis on Speed & Automation:** Frequent use of terms like "machine speed," "live in a day," "deterministically," "automatically," and "burns down the backlog."
*   **Strong, Active Verbs:** Employs powerful verbs that convey action, control, and efficacy (e.g., prevents, fixes, audits, weaponize, connects, unifies, acts, embeds, enforces, steers).
*   **Repetition for Reinforcement:** Key messages and calls-to-action are repeated strategically to ensure they resonate (e.g., "Book a demo / See AppSec at machine speed," "No sensors. No tagging. No build modification.").
*   **Technical Precision with Clear Benefits:** Incorporates industry-specific terminology (AI SDLC, SCA, SAST, CVE, MCP) but always ties it back to clear, tangible benefits for the user.
*   **Structured Information Delivery:** Utilizes bullet points, numbered lists, and clear headings to break down information into digestible segments.

### Vocabulary Preferences and Word Choices
*   **High-Tech & Security:** AI, SDLC, AppSec, agentic, SCA, SAST, CVE, MCP, CLI, Context Engine, Supply Chain Security, Compliance.
*   **Action-Oriented:** Prevent, Fix, Operate, Secure, Eliminate, Run, Govern, Connects, Unifies, Acts, Embeds, Enforce, Steer, Burns down, Responds, Delivers.
*   **Benefit-Driven:** Machine-speed, validated, continuously verifies, secure, eliminate, scale, audit-readiness, automatic, precise, magic, continuous, deterministic.
*   **Impactful Adjectives/Adverbs:** Deterministically, automatically, precise, continuous, secure, safe, verified, critical.

## Content Patterns

### Common Themes and Topics
*   **The AI-Generated Code Security Crisis:** The core narrative revolves around the new risks introduced by AI-written code and AI agents.
*   **Heeler's Comprehensive Solution:** Positioning Heeler as the all-encompassing platform that prevents, fixes, and audits across the entire AI SDLC.
*   **Speed, Efficiency, and Automation:** Highlighting Heeler's ability to operate at "machine speed" and automate complex security tasks.
*   **Context as a Differentiator:** Emphasizing how Heeler's "Context Engine" provides the intelligence for precise and effective security actions.
*   **Integration and Ease of Use:** Stressing "No sensors. No tagging. No build modification. Live in a day."

### Structural Approaches to Content
*   **Problem-First, Solution-Second:** Content often begins by vividly describing the security challenges before introducing Heeler's capabilities.
*   **Layered Explanation:** Features are often grouped into logical "layers" or categories (e.g., Prevent, Fix, Operate) to demonstrate comprehensive coverage.
*   **Feature-Benefit Pairing:** Each product feature or capability is clearly linked to a direct benefit for the user or organization.
*   **Concrete Examples/Scenarios:** Uses specific, short scenarios (e.g., "Claude Code · payments-api" package review) to illustrate how Heeler works in practice.

### Call-to-Action Styles and Patterns
*   **Direct and Clear:** "Book a demo," "See how it works," "Sign In," "Contact Us."
*   **Benefit-Oriented:** CTAs often include a benefit statement, such as "See AppSec at machine speed" or "In 30 minutes, see how Heeler secures AI-generated code..."
*   **Prominent and Repetitive:** Key CTAs are strategically placed throughout the content, often repeated in header, footer, and within sections to maximize visibility.

## Audience Interaction

### How the Brand Addresses its Audience
Heeler addresses its audience implicitly, speaking to their pain points and aspirations as "AI-forward teams." While not always using "you" explicitly, the content is clearly tailored to professionals grappling with modern AppSec challenges. It positions the audience as intelligent, understanding the need for advanced solutions.

### Level of Formality and Relationship Style
The relationship is that of a **trusted expert advisor**. The language is professional and authoritative, but not overly formal or academic. It's direct, confident, and helpful, aiming to empower the audience by solving their most pressing security problems with cutting-edge technology.

### Engagement and Conversation Patterns
Engagement is primarily **informative and problem-driven**. The brand engages by clearly articulating the audience's challenges and then presenting Heeler as the definitive, efficient solution. The primary conversational pattern is a one-way communication of expertise and value, leading to direct calls-to-action for further interaction (e.g., demos).

## Guidelines & Examples

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

**DO:**
*   **Be Direct and Concise:** Get straight to the point, avoiding jargon where simpler terms suffice, but embracing technical terms when necessary for precision.
*   **Emphasize Speed and Automation:** Highlight how Heeler saves time, accelerates processes, and delivers immediate value.
*   **Focus on Deterministic Outcomes:** Stress reliability, precision, and the elimination of guesswork.
*   **Frame as Problem-Solution:** Always connect Heeler's capabilities to a clear pain point or challenge the audience faces.
*   **Use Strong, Active Verbs:** Convey confidence, control, and decisive action.
*   **Provide Concrete Examples:** Illustrate how Heeler works in real-world scenarios.

**DON'T:**
*   **Be Vague or Ambiguous:** Avoid generalizations; be specific about capabilities and benefits.
*   **Use Overly Casual or Colloquial Language:** Maintain a professional, expert tone.
*   **Sound Passive or Hesitant:** Heeler is a leader and a solution, not a suggestion.
*   **Overuse Jargon Without Context:** If a technical term is used, ensure its benefit or role is clear.
*   **Overwhelm with Information:** Use clear structure (lists, headings) to make content scannable.

### Example Phrases and Expressions that are "On-Brand"
*   "Machine-speed security for AI-written code."
*   "Agents write the code. AI attackers weaponize the flaws."
*   "Heeler prevents, fixes, and audits every layer of the AI SDLC — deterministically, at machine speed."
*   "No sensors. No tagging. No build modification. Live in a day."
*   "Context, turned into action."
*   "Heeler burns down the backlog and responds the moment new CVE research is published."
*   "Guide Claude Code, Cursor, and Copilot to secure patterns at generation."
*   "Three layers. One continuous system."

### Content Types and Formats the Brand Uses
*   Website Marketing Copy (product pages, feature descriptions, use cases)
*   Blog Posts & Press Releases
*   Webinar & Event Promotions
*   Solution Briefs & Whitepapers
*   Comparison Guides
*   FAQs
*   Demo Calls-to-Action