Voice and style
Voice and style guide
Voice and style information from Atlas Launch Canary.
# Voice and Style Guide
**Applicability:** This guide conditionally describes Atlas Visibility. Its relationship to the supplied client name, Atlas Launch Canary, remains unverified.
**Source boundary:** The guidance reflects observed public brand copy and the packet’s analysis of that copy, not spoken voice. Proposed voice preferences in the packet are not treated as approved house rules.
Voice in One Sentence
Atlas’s observed brand copy speaks plainly to business owners, combines concern about visibility with practical explanation, and becomes more restrained and qualified in articles than in sales or founder copy.
Five Voice Traits
| Trait | Supported signal | Practical application |
|---|---|---|
| **Owner-to-owner** | The founder’s About page uses autobiography and direct address to business owners. | Recognize the owner’s decisions and coordination burden. Do not invent personal experiences or write as the founder without approval. |
| **Plainspoken** | The packet describes accessible business-owner copy with technical terms introduced gradually. | Explain unfamiliar terminology through concrete functions rather than acronyms alone. |
| **Protective** | Sales messaging frames AI-search change as a threat to business visibility. | Acknowledge concern, but do not intensify it beyond the evidence. |
| **Opinionated** | Articles distinguish coordinated work from isolated tactics, and the content page rejects generic output. | Make supported distinctions without claiming every alternative is ineffective. |
| **Educational** | Engine coverage uses familiar analogies; articles define concepts and explain missing context. | Explain what a concept means, why it matters, and where its limits sit. |
These are observed signals. Their status as formal, client-approved voice traits needs confirmation.
Tone Dial by Situation
| Situation | Observed tone | Conservative guidance |
|---|---|---|
| Articles and blogs | Calm, specific, explanatory, and qualified. | Use this as the primary model for the target channel. |
| Homepage and acquisition copy | Urgent, protective, and sales-oriented. | Retain the recognizable concern, not unsupported catastrophe or certainty. |
| Founder/About copy | Personal, warm, emotionally expressive, and informal. | First-person founder authorship and personal anecdotes require confirmation. |
| Technical explanations | The packet recommends precision because technical claims are sensitive. | Distinguish published platform requirements from Atlas’s implementation choices. |
| Research explanations | Large finding followed by study conditions and interpretation. | Preserve the exact metric and study frame before explaining implications. |
| Checkup and fit conversation | Low-friction, lightly informal, and zero-pressure. | Offer a diagnostic next step without implying guaranteed results. |
Mild profanity appears in founder copy. Its acceptability in articles or team-authored material: [Needs clarification].
Repeated Writing Patterns
Sales-page pattern Change or threat → owner concern → familiar analogy → coordinated solution → low-friction action.
Article pattern Define the concept → explain missing context → distinguish useful work from a shortcut → connect the explanation to the engine.
Research-page pattern Lead with a finding → describe study conditions → interpret the business implication.
Repeated concepts - Coordinated business information. - Actual expertise and perspective. - A usable source of truth. - Clear public context. - Outside corroboration. - Managed follow-through.
These are patterns identified in the packet, not mandatory formulas for every article.
Openings, Paragraphs, Sentences, and Structure
Openings Supported opening approaches include: - Begin with a recognizable owner problem. - Define a misunderstood concept. - Introduce a research finding with its measurement context.
For articles, the observed restrained approach is a better fit than repeating homepage-level threat language.
Paragraphs and sentences - Accessible business-owner language is supported. - Technical nouns should be explained when introduced. - A specific sentence-length target, paragraph-length target, or reading-grade requirement is not established. - No quantitative readability test was performed.
Preferred paragraph length, sentence length, and punctuation conventions: [Needs clarification].
Structure The packet supports a concept-led explanatory sequence: 1. Identify or define the issue. 2. Supply the context a reader may be missing. 3. Explain relevant distinctions or tradeoffs. 4. Connect the explanation to the published offer where relevant. 5. Offer a simple next step where appropriate.
A universal answer-first format, required heading template, or mandatory CTA placement is not established.
Authorship Whether articles should use Robbie’s first-person voice or an Atlas team voice: [Needs clarification].
Vocabulary Rules
Retain selectively - **Atlas Visibility Engine:** Follow the brand name with a concrete explanation of the work. - **Single source of truth:** Use for the knowledge-base concept, without implying automatic factual agreement everywhere. - **Reputation Gap:** Explain the difference between real-world credibility and the public record. - **Invisibility Gap:** Use only with a clear explanation of what is being assessed. - **Corroboration:** Prefer when discussing outside support for business claims. - **Understand, trust, and recommend:** Treat as an outcome aim, not a promise.
Define before using - AEO, SEO, and GEO. - Schema, canonical tags, metadata, and crawler access. - AI-facing or machine-readable website. - Citations, specifying whether the subject is listings, outside references, or sources inside AI answers. - AI-compliant, if retained at all.
Informal vocabulary The content page uses `generic AI slop` as a negative contrast. That supports an opinionated brand signal, not unrestricted use of dismissive language in every article.
The checkup’s light informality and founder profanity do not establish a universal humor or profanity rule.
Banned or Tired Phrases
**No client-approved banned-word list is established.** Separate evidence restrictions from the packet’s provisional style suggestions.
Evidence-based restrictions for this KB
| Phrase or construction | Why it needs restriction |
|---|---|
| `Guaranteed ChatGPT rankings` or guaranteed recommendations | Atlas’s corroboration coverage rejects guaranteed third-party behavior. |
| `AI-compliant` without a definition | No named external certification or standard is established. |
| `Erased` or equivalent disappearance language | May overstate findings about exposure, readiness, or a specific test surface. |
| `Exactly what Google and ChatGPT think` | Sampled outputs do not establish comprehensive platform knowledge. |
| `SEO is dead` or `traditional search is dying` | Conflicts with Atlas’s article supporting useful SEO foundations. |
| Unexplained claims that AI systems trust a business | Must be connected to observable information and supporting sources, not human-like certainty. |
Provisional tired phrases The packet proposes reconsidering: - `Unlock the power of AI` - `Revolutionize your online presence` - `Future-proof your business`
These are discussion candidates, not confirmed client bans.
Argument Style
- Explain a category through familiar business decisions.
- Make distinctions between monitoring and implementation.
- Show why isolated content or directory work differs from a coordinated system.
- Explain the roles of the primary website and AI-facing asset without asserting universal necessity.
- Use outside corroboration as support, not as a promise of endorsement.
- Connect explanations to concrete components rather than relying on branded terminology alone.
Competitor context may clarify alternatives and scope. It must not become evidence that Atlas delivers a competitor’s features, guarantees, or specialist capabilities.
Research-led arguments must preserve the study’s measure and conditions. A finding about discovery exposure cannot become a claim about traffic, leads, or revenue.
Handling Nuance and Uncertainty
Use the packet’s evidence distinctions:
- **Verified published statement:** The organization publishes the offer or claim.
- **Strong inference:** A reasonable interpretation, not a confirmed operating fact or approved belief.
- **Open question:** Requires client clarification.
In finished content:
- Attribute published claims when operational validation is missing.
- Keep desired outcomes separate from measured effects.
- Keep sampled visibility separate from comprehensive platform behavior.
- Keep recommendations, citations, visits, inquiries, and sales distinct.
- Identify unknown scope or methodology instead of filling gaps.
- Preserve conflicting published messages until an authoritative position is confirmed.
For missing KB details, use [Needs clarification] or [Not established in the research packet].
Non-Negotiables
These are evidence safeguards for using this KB, not a privately supplied client style policy.
- Do not write research observations as client quotations.
- Do not attribute Atlas Visibility’s voice or beliefs to Atlas Launch Canary without confirming the relationship.
- Do not invent founder experiences, customer stories, or spoken expressions.
- Do not guarantee third-party recommendations or business outcomes.
- Do not convert research-exposure measures into traffic or lead-loss claims.
- Do not present the separate AI-facing site as a universal platform requirement.
- Do not imply a named AI-compliance certification.
- Do not publish definitive pricing until the $89 and $95 inconsistency is resolved.
- Do not imply verified regulated-industry expertise.
- Do not use em dashes.
Channel Guidance
**Primary content channels:** Articles / Blog.
For this channel:
- Favor the calmer editorial voice documented in the packet.
- Explain owner-relevant questions, distinctions, scope, and tradeoffs.
- Introduce technical language gradually.
- Preserve uncertainty around platform behavior and reporting.
- Connect the topic to Atlas only where the published offer is relevant.
- Use a checkup or fit conversation as a low-friction next step when appropriate.
Homepage, founder-page, and course observations are contextual voice evidence, not instructions to add those channels to the current content plan.
Email, social-media, video, and other channel-specific voice rules: [Not established in the research packet].
Reusable Copy Blocks
The following are supported draft paraphrases, not extracted quotations or approved final copy. Use them only if Atlas Visibility is confirmed as the intended business.
Plain-language offer description
Atlas Visibility presents a managed system that combines documented business knowledge, an AI-facing website, ongoing content, outside references, primary-site support, and reporting.
Checkup CTA
Request a free visibility checkup for an initial snapshot and next-step direction. No credit card is required.
Fit-conversation CTA
Contact Atlas to discuss your goals and whether the Visibility Engine is a fit.
Recommendation expectation note
The work aims to improve how the business is represented in public information. Third-party recommendations are not guaranteed.