Halo CompassBrand system
Index

05 / Voice & tone

Precise, calm and useful.

Write as an expert guide who makes the work easier to understand. Prefer concrete verbs, observable outcomes and short explanations over inflated claims.

01

Guidance set

Editorial Rules

must

Label non-current capability as NEXT or FUTURE DIRECTION wherever it appears.

Readiness language prevents planned capability from being represented as available.

Examples
Use

Future direction: compare repeat observations to surface changes for review.

Avoid

Halo will detect every change.

halo.claims.readiness-label

02

Guidance set

Banned Language

must-not

Avoid "AI-powered". Name VSI or the exact model-assisted action.

Imported from the General section of the Halo guidance.

halo.content.banned-language.ai-powered
must-not

Avoid "Authentic vehicle image". Image with recorded capture and transformation context.

Imported from the General section of the Halo guidance.

halo.content.banned-language.authentic-vehicle-image
must-not

Avoid "Cutting-edge / next-gen". Name the technology or readiness.

Imported from the General section of the Halo guidance.

halo.content.banned-language.cutting-edge-next-gen
must-not

Avoid "Effortless". Guided, shorter, or fewer handoffs—when measured.

Imported from the General section of the Halo guidance.

halo.content.banned-language.effortless
must-not

Avoid "Fraud-proof / eliminates fraud". Supports review; surfaces anomaly signals.

Imported from the General section of the Halo guidance.

halo.content.banned-language.fraud-proof-eliminates-fraud
must-not

Avoid "Guaranteed accurate". Verified against defined coverage requirements.

Imported from the General section of the Halo guidance.

halo.content.banned-language.guaranteed-accurate
must-not

Avoid "Leverage". Use, apply, connect, route, or measure.

Imported from the General section of the Halo guidance.

halo.content.banned-language.leverage
must-not

Avoid "Real time". Use only with a measured latency definition.

Imported from the General section of the Halo guidance.

halo.content.banned-language.real-time
must-not

Avoid "Revolutionary / game-changing". Name the operating change.

Imported from the General section of the Halo guidance.

halo.content.banned-language.revolutionary-game-changing
must-not

Avoid "Seamless". Describe the handoff or integration.

Imported from the General section of the Halo guidance.

halo.content.banned-language.seamless
must-not

Avoid "Single source of truth". Source of record for the defined workflow.

Imported from the General section of the Halo guidance.

halo.content.banned-language.single-source-of-truth
must-not

Avoid "World-class / best-in-class". Provide evidence or omit.

Imported from the General section of the Halo guidance.

halo.content.banned-language.world-class-best-in-class

03

Guidance set

CTA System

should

Company: Talk with Halo.

Imported from the Primary actions section of the Halo guidance.

halo.content.cta-system.company-talk-with-halo
should

Global header: APPLY FOR POC.

Imported from the Primary actions section of the Halo guidance.

halo.content.cta-system.global-header-apply-for-poc
should

Home: Apply for POC.

Imported from the Primary actions section of the Halo guidance.

halo.content.cta-system.home-apply-for-poc
should

Platform: Start a technical conversation.

Imported from the Primary actions section of the Halo guidance.

halo.content.cta-system.platform-start-a-technical-conversation
should

Product: Review the founding POC.

Imported from the Primary actions section of the Halo guidance.

halo.content.cta-system.product-review-the-founding-poc
should

Solutions: Discuss a workflow.

Imported from the Primary actions section of the Halo guidance.

halo.content.cta-system.solutions-discuss-a-workflow
should

Technology: See how Halo integrates.

Imported from the Primary actions section of the Halo guidance.

halo.content.cta-system.technology-see-how-halo-integrates

04

Guidance set

Terminology

must

Use "Anomaly signal" only to mean: A signal that may prioritize review.. Do not use it as: Fraud verdict..

Imported from the General section of the Halo guidance.

halo.content.terminology.anomaly-signal
must

Use "Confidence" only to mean: A bounded system measure tied to a specific observation or result.. Do not use it as: Certainty..

Imported from the General section of the Halo guidance.

halo.content.terminology.confidence
must

Use "Coverage" only to mean: Whether required observations/views were captured to the defined standard.. Do not use it as: Vehicle-condition accuracy..

Imported from the General section of the Halo guidance.

halo.content.terminology.coverage
must

Use "Evidence request" only to mean: A structured request describing what must be observed.. Do not use it as: A legal demand..

Imported from the General section of the Halo guidance.

halo.content.terminology.evidence-request
must

Use "Guided Capture" only to mean: The field experience that guides a person beside the vehicle.. Do not use it as: A photo filter..

Imported from the General section of the Halo guidance.

halo.content.terminology.guided-capture
must

Use "Halo Visual Passport" only to mean: Portable selected evidence with context and permissions.. Do not use it as: A government passport or ownership title..

Imported from the General section of the Halo guidance.

halo.content.terminology.halo-visual-passport
must

Use "Provenance" only to mean: Recorded origin and change history of a digital asset.. Do not use it as: Proof that the depicted event is true..

Imported from the General section of the Halo guidance.

halo.content.terminology.provenance
must

Use "Secure session" only to mean: The authorized link-based observation session.. Do not use it as: Proof of participant identity unless verified..

Imported from the General section of the Halo guidance.

halo.content.terminology.secure-session
must

Use "Trusted Vehicle Observation Infrastructure" only to mean: Category for remote, guided, verified observation and evidence handling.. Do not use it as: A guarantee that observations are true..

Imported from the General section of the Halo guidance.

halo.content.terminology.trusted-vehicle-observation-infrastructure
must

Use "Vehicle Evidence Graph" only to mean: Relationships among requests, sessions, media, transformations, actors, and uses.. Do not use it as: The Visual Passport..

Imported from the General section of the Halo guidance.

halo.content.terminology.vehicle-evidence-graph
must

Use "Vehicle record" only to mean: VIN-linked operational record of session and outputs.. Do not use it as: Title, inspection certificate, or immutable truth..

Imported from the General section of the Halo guidance.

halo.content.terminology.vehicle-record
must

Use "Vehicle Spatial Intelligence" only to mean: Halo's core technology for understanding vehicle geometry, guidance, and coverage.. Do not use it as: Generic AI vision..

Imported from the General section of the Halo guidance.

halo.content.terminology.vehicle-spatial-intelligence

05

Guidance set

Voice And Tone

should

For Candidate audiences, use a Ambitious and honest tone. Emphasize Hard problem, field work, craft.. Avoid Culture clichés..

Imported from the Tone by audience section of the Halo guidance.

halo.content.voice-and-tone.candidate
should

For Dealer audiences, use a Practical and measured tone. Emphasize Handoffs, time, consistency, POC decision.. Avoid Platform abstraction before value..

Imported from the Tone by audience section of the Halo guidance.

halo.content.voice-and-tone.dealer
should

For Investor audiences, use a Expansive but grounded tone. Emphasize Owned primitive and compounding record.. Avoid TAM theatre and autonomous hype..

Imported from the Tone by audience section of the Halo guidance.

halo.content.voice-and-tone.investor
must

Lead with a concrete subject and verb: “Halo guides the capture.” Not “Capture is seamlessly optimized.”

Imported from the Voice rules section of the Halo guidance.

halo.content.voice-and-tone.lead-with-a-concrete-subject-and-verb-halo-guides-the-capture-not-captur
must

Let one sharp sentence stand alone when the idea needs weight.

Imported from the Voice rules section of the Halo guidance.

halo.content.voice-and-tone.let-one-sharp-sentence-stand-alone-when-the-idea-needs-weight
must

Name the physical vehicle, person, request, view, record, or system.

Imported from the Voice rules section of the Halo guidance.

halo.content.voice-and-tone.name-the-physical-vehicle-person-request-view-record-or-system
should

For Partner audiences, use a Collaborative tone. Emphasize Integration, selective evidence, shared value.. Avoid Implied commitments..

Imported from the Tone by audience section of the Halo guidance.

halo.content.voice-and-tone.partner
must

Prefer short declarative sentences, then one longer sentence for mechanism.

Imported from the Voice rules section of the Halo guidance.

halo.content.voice-and-tone.prefer-short-declarative-sentences-then-one-longer-sentence-for-mechanis
should

For Technical audiences, use a Exact and bounded tone. Emphasize Objects, states, failures, permissions.. Avoid Architecture adjectives without detail..

Imported from the Tone by audience section of the Halo guidance.

halo.content.voice-and-tone.technical
must

Use confidence language carefully: verified coverage is not verified condition.

Imported from the Voice rules section of the Halo guidance.

halo.content.voice-and-tone.use-confidence-language-carefully-verified-coverage-is-not-verified-cond
must

Lead with a concrete subject and verb, then explain the mechanism in bounded language.

Halo sounds calm and confident when it names what changes and how it works.

Examples
Use

Halo guides the capture.

Avoid

Capture is seamlessly optimized.

halo.voice.direct-mechanism

Halo Compass brand system

One governed source for people and agents.