Voice

Origin speaks like a visionary engineer. We are experts in the technical “internals” of computing, but we communicate our findings with the clarity required for executive decision-making.

We operate at the frontier of agentic computing and endpoint security. Our voice reflects this position — technically grounded, forward-looking, and always focused on enabling productivity rather than restricting it.

Voice Traits

Intelligent & Investigative: We don’t just see data; we see intent. Our tone reflects a deep understanding of computer use agents and the “Semantic Era”.

• Do: Use precise technical terminology (e.g., “Runtime Memory Protection,” “Semantic Protocol Confusion”).
• Don’t: Use generic marketing “buzzwords” that lack technical substance.

Direct & Decisive: In a crisis or an “Atypical” event, clarity is the greatest asset. We use short, punchy sentences to convey high-priority information.

• Do: State facts plainly: “Origin is developing a new generation of endpoint capabilities.”
• Don’t: Use passive voice or hedge your statements with “we think” or “perhaps.”

Enabling (Not Obstructionist): Traditional security says “No.” Origin says “Yes, safely.” Our voice should always highlight the productivity gains that our security makes possible.

• Do: “Safely give AI agents the permissions they need.”
• Don’t: Focus solely on the “rising tide” of threats without offering the solution.

Tone by Context

Default

Product communications, research publications, and executive briefings.

The default tone is visionary and precise. We speak with the authority of deep technical research while making complex concepts accessible to decision-makers.

Example: “Origin provides runtime visibility into agent behavior across every endpoint in your fleet.”

Avoid: “Our cutting-edge AI-powered solution leverages next-gen technology to protect your business.”

Errors and Support

Atypical behavior alerts, blocked actions, and system notifications.

The tone shifts to Clear and Investigative. We describe what happened with forensic precision and guide users toward resolution. Every alert should convey what, why, and what to do next.

Example: “Atypical behavior detected: Agent ‘Claude’ attempting out-of-context registry modification. Action blocked. Review session activity for context.”

Avoid: “Something suspicious happened. You might want to look into it.” (Too vague for high-stakes decisions).

Success and Celebration

Secured environments, validated configurations, and productivity milestones.

The tone is Confident and Enabling. We reinforce that security and productivity coexist. Success means the user can move faster, not just that threats are blocked.

Example: “Fleet secured. 1,798 active sessions operating within policy. Zero atypical events in the last 24 hours.”

Avoid: “Great news! Everything looks safe for now!” (Undermines the precision our users expect).

Voice in Action

Scenario	Legacy Security Voice	Origin Brand Voice
New Threat	”Warning: Unknown malware detected on workstation."	"Atypical behavior detected: Agent ‘Claude’ attempting out-of-context registry modification.”
Product Value	”Our software blocks 99% of all cyber attacks."	"Secure the productivity you demand in the Semantic Era of computing.”
Data Report	”System logs show 16,000 events recorded."	"16,248 prompts analyzed across 1,798 active sessions.”

Writing Style Rules

• Case Usage: Use UPPERCASE for high-level display headers and functional UI labels (e.g., “ENDPOINT CAPABILITIES,” “ACTIVITY”).
• Perspective: Speak as “We” (the collective expertise of Origin) to the user’s “You” (the enterprise leader).
• Formatting: Use lists and bold emphasis to make technical research “scannable” for busy CISOs.
• Terminology: Favor Origin-specific language (Semantic Era, Atypical, computer use agents) to reinforce our unique position.

The “One-Question” Test

When writing for Origin, always ask: “Does this sentence help the user feel more confident about enabling AI agents securely?” If the answer is “maybe” or “no,” the copy needs to be sharper.