# BELA65 — Voice & Tone ### How BELA65 sounds — in every word we ever publish > Inherits from `00_messaging-house.md`. Where the messaging house says *what* we say, this says *how* it sounds. Every writer reads this before writing a single line. --- ## Executive Summary BELA65's voice is **calm, clear, and confident** — the voice of a brilliant senior engineer who has stopped trying to impress you and simply explains things so well that you feel smart. We earn trust through *clarity*, not volume. We never hype, never patronize, never hide behind jargon. If a sentence needs a technical term, the very next breath explains it in plain words. The test for every sentence: **Would a thoughtful 15-year-old understand it, and would a CTO still respect it?** If both, ship it. --- ## The Voice in one line > **The calm confidence of an expert who explains everything so simply you feel smarter for having listened.** --- ## Our Five Voice Principles ### 1. Clarity is the feature The hardest thing in tech is making complex things simple. That *is* our brand. Short sentences. One idea at a time. The plain word over the impressive word, always. ### 2. Show, don't hype We never say "revolutionary." We show the specific thing that's different and let the reader feel the wow themselves. Excitement is a *result* of understanding, not a word we type. ### 3. Honest to a fault We say what's true today and clearly mark what's coming (see `03_claims-ledger.md`). Honesty is more persuasive than perfection. We'd rather under-promise and be trusted. ### 4. Respect the reader Never talk down ("simply," "just," "obviously"). Never talk over ("leveraging synergistic paradigms"). We assume the reader is intelligent but busy — so we do the work of being clear *for* them. ### 5. Warm, not corporate We're an engineering system, but we're not cold. We use "you" and "your business." We tell small human stories. A little warmth makes precision feel kind rather than clinical. --- ## Tone — how the voice flexes by context The *voice* never changes. The *tone* adapts to the moment. | Context | Tone dial | Example opening | |--------|-----------|-----------------| | Landing page hero | Bold + spacious | "Before it writes a line of code, BELA understands your business." | | Documentation | Precise + reassuring | "Here's exactly what happens at each step, and what you'll see." | | Investor deck | Confident + grounded | "A new category: the Autonomous Engineering Operating System." | | Video voice-over | Warm + unhurried | "Imagine describing what your business needs — in your own words." | | Error / limitation | Honest + helpful | "This part isn't available yet. Here's what is, and what's coming." | | Social post | Curious + human | "Most tools start by writing code. What if the first step was listening?" | --- ## Simple Explanation (for a 15-year-old) BELA talks like the best teacher you ever had — the one who made hard things feel easy and never made you feel dumb for asking. Calm, clear, honest, kind. No showing off. No confusing words. --- ## Business Explanation (for a business owner) You'll never need a translator to understand BELA's marketing. We write the way a trusted advisor speaks: plainly, honestly, and with respect for your time. When we use a technical word, we explain it immediately. When something isn't ready yet, we tell you. That honesty is deliberate — it's how we earn the trust that software decisions require. --- ## Technical Explanation (for a CTO / engineer) Voice is enforced as a style contract, not a vibe. Concrete rules: active voice; average sentence length under ~18 words; target reading level around Grade 8–9 for customer-facing copy (CTO layer may go higher); every technical term paired with its glossary translation on first use; no unverifiable superlatives; claims bounded by `03_claims-ledger.md`. These are reviewable and testable, which is the point — our tone is auditable. --- ## The Sentence Rules (checklist for every writer) - ✅ **Plain word beats fancy word.** "Understand," not "comprehend." "Build," not "instantiate." - ✅ **One idea per sentence.** If there's an "and" doing heavy lifting, split it. - ✅ **Define on first use.** Technical term → immediately the italic glossary line. - ✅ **Active voice.** "BELA designs the software," not "the software is designed." - ✅ **Cut the throat-clearing.** Delete "In today's fast-paced world," "It's important to note that." - ✅ **Numbers only if sourced.** No figure without a home in the claims ledger. - ✅ **Read it aloud.** If you run out of breath or stumble, rewrite it. - ❌ **No banned words** (see glossary): revolutionary, game-changing, magical, seamless-as-filler, cutting-edge, 10x-unsourced. --- ## Before / After (our voice in action) > **Before:** "BELA65 leverages cutting-edge autonomous AI to revolutionize the software development lifecycle with seamless end-to-end orchestration." > > **After:** "BELA65 understands your business, designs the software, builds it, and checks its own work — then explains every decision. It's not a faster way to write code. It's a complete way to build software you can trust." > **Before:** "Utilizing our proprietary BRM technology, requirements are ingested and semantically modeled." > > **After:** "First, BELA builds a **Business Reality Model** — think of it as a blueprint of your business, drawn before any software is built." --- ## Accessibility & Global-Readiness Standard Because this is a global launch, voice includes reach: - **Reading level:** aim Grade 8–9 for customer copy; keep sentences translatable (avoid idioms that won't localize). - **Captions & subtitles:** every video ships a subtitle file; captions match the VO exactly. - **No culture-locked references** in core copy (sports metaphors, local idioms) unless a regional variant calls for them. - **Plain-language first** also serves non-native English readers and screen-reader users. --- ## Key Messages (about the voice itself) 1. **Clarity is our brand. We win by being understood.** 2. **We show the wow; we never shout it.** 3. **Honesty over hype — always.** 4. **A 15-year-old understands it; a CTO respects it.** --- ## Visual Suggestions - Typography and layout should feel like the voice: generous whitespace, calm rhythm, one idea per screen. - Pair plain-language lines with restrained motion — the *words* carry the wow, not the effects. --- ## Future Improvements - Build per-language tone guides during localization. - Create a one-page "voice cheat sheet" (front-and-back printable) for external agencies and freelancers. - Add a lightweight automated readability + banned-word linter for all copy. --- ## Version History | Version | Date | Change | Author | |--------|------|--------|--------| | 1.0 | 2026-07-02 | Initial Founder-Ready voice & tone: five principles, tone matrix, sentence rules, accessibility standard. | Launch Studio |