Halo Brand System

Guidance set

Applications

should

Booth: architectural-scale proof with quiet technical orientation.

Imported from the Approved patterns section of the Halo guidance.

halo.visual.applications.booth-architectural-scale-proof-with-quiet-technical-orientation

must

Business cards and letterhead use a quiet measurement rail, generous margins, and versioned contact or document metadata rather than decorative texture.

Imported from the Rules section of the Halo guidance.

halo.visual.applications.business-cards-and-letterhead-use-a-quiet-measurement-rail-generous-marg

must-not

Do not create channel-specific colours, icons, cards, or type scales outside the canonical system.

Imported from the Red lines section of the Halo guidance.

halo.visual.applications.do-not-create-channel-specific-colours-icons-cards-or-type-scales-outsid

must-not

Do not paste untracked assets into decks, documents, social files, or event graphics.

Imported from the Red lines section of the Halo guidance.

halo.visual.applications.do-not-paste-untracked-assets-into-decks-documents-social-files-or-event

must-not

Do not reduce type or spacing below the system minimum to make overcrowded content fit.

Imported from the Red lines section of the Halo guidance.

halo.visual.applications.do-not-reduce-type-or-spacing-below-the-system-minimum-to-make-overcrowd

must

Documentation teaches by example first, then explanation, with the canonical token, asset path, component, or rule ID attached.

Imported from the Rules section of the Halo guidance.

halo.visual.applications.documentation-teaches-by-example-first-then-explanation-with-the-canonic

must

Email signatures use name, role, Halo, and literal contact details without quotes, banners, badges, or unapproved icons.

Imported from the Rules section of the Halo guidance.

halo.visual.applications.email-signatures-use-name-role-halo-and-literal-contact-details-without-

must

Every application must pass the recognition tests at its actual size, distance, format, and access mode.

Imported from the Rules section of the Halo guidance.

halo.visual.applications.every-application-must-pass-the-recognition-tests-at-its-actual-size-dis

must

Investor and sales presentations attach a source, sample, timeframe, and interpretation to every metric that asks for belief.

Imported from the Rules section of the Halo guidance.

halo.visual.applications.investor-and-sales-presentations-attach-a-source-sample-timeframe-and-in

must

Merchandise uses the mark, wordmark, Motion Signature, or monochrome target with equipment-like restraint; slogans, gradients, and oversized Magenta fields are prohibited.

Imported from the Rules section of the Halo guidance.

halo.visual.applications.merchandise-uses-the-mark-wordmark-motion-signature-or-monochrome-target

must

Paid and lifecycle media must preserve the same evidence, accessibility, claim, and asset-provenance requirements as owned channels.

Imported from the Rules section of the Halo guidance.

halo.visual.applications.paid-and-lifecycle-media-must-preserve-the-same-evidence-accessibility-c

should

PDF: cover statement, evidence body, full source appendix.

Imported from the Approved patterns section of the Halo guidance.

halo.visual.applications.pdf-cover-statement-evidence-body-full-source-appendix

must

Presentation cards are reserved for evidence, assets, workflow objects, sourceable metrics, product records, or catalog comparisons; narrative slides remain editorial.

Imported from the Rules section of the Halo guidance.

halo.visual.applications.presentation-cards-are-reserved-for-evidence-assets-workflow-objects-sou

should

Presentation: one thought, one focal point, one supporting sentence, and no more than three supporting points.

Imported from the Approved patterns section of the Halo guidance.

halo.visual.applications.presentation-one-thought-one-focal-point-one-supporting-sentence-and-no-

must

Print uses high contrast, generous margins, sharp type, evidence-led layouts, print-safe colour, and readable body copy.

Imported from the Rules section of the Halo guidance.

halo.visual.applications.print-uses-high-contrast-generous-margins-sharp-type-evidence-led-layout

should

Product: target, align, capture, confirm the record.

Imported from the Approved patterns section of the Halo guidance.

halo.visual.applications.product-target-align-capture-confirm-the-record

must

Product UI behaves like field equipment: show the current state, the reason, the next action, remaining positions, confidence, and source metadata without marketing language.

Imported from the Rules section of the Halo guidance.

halo.visual.applications.product-ui-behaves-like-field-equipment-show-the-current-state-the-reaso

must

Reports use one evidence statement on the cover, governed evidence and metric components inside, and a complete source trail in the appendix.

Imported from the Rules section of the Halo guidance.

halo.visual.applications.reports-use-one-evidence-statement-on-the-cover-governed-evidence-and-me

must

Social assets use one claim, one real image or product artifact, and a source caption; they must not become motivational posters, generic AI art, or trend templates.

Imported from the Rules section of the Halo guidance.

halo.visual.applications.social-assets-use-one-claim-one-real-image-or-product-artifact-and-a-sou

should

Social: real work, one claim, source in caption.

Imported from the Approved patterns section of the Halo guidance.

halo.visual.applications.social-real-work-one-claim-source-in-caption

must

Trade-show environments use one sentence visible at distance, one large proof visual, up to three supporting metrics, and restrained screen motion.

Imported from the Rules section of the Halo guidance.

halo.visual.applications.trade-show-environments-use-one-sentence-visible-at-distance-one-large-p

should

Website: claim left, evidence right, source and confidence attached.

Imported from the Approved patterns section of the Halo guidance.

halo.visual.applications.website-claim-left-evidence-right-source-and-confidence-attached

must

Website heroes lead with one evidence statement, an inspectable vehicle or product record, a concise source rail, and one Magenta signal event.

Imported from the Rules section of the Halo guidance.

halo.visual.applications.website-heroes-lead-with-one-evidence-statement-an-inspectable-vehicle-o

Guidance set

Components

must

A component variant must solve a recurring semantic need across surfaces rather than a single layout preference.

Imported from the Rules section of the Halo guidance.

halo.visual.components.a-component-variant-must-solve-a-recurring-semantic-need-across-surfaces

must

Catalog cards are reserved for official assets, icons, components, photography, diagrams, motion, and presentation specimens.

Imported from the Rules section of the Halo guidance.

halo.visual.components.catalog-cards-are-reserved-for-official-assets-icons-components-photogra

must-not

Do not add a component without keyboard, screen-reader, reduced-motion, and responsive behaviour where applicable.

Imported from the Red lines section of the Halo guidance.

halo.visual.components.do-not-add-a-component-without-keyboard-screen-reader-reduced-motion-and

must-not

Do not fork a canonical component for one deck, page, campaign, or document.

Imported from the Red lines section of the Halo guidance.

halo.visual.components.do-not-fork-a-canonical-component-for-one-deck-page-campaign-or-document

must-not

Do not place ordinary paragraphs in cards merely to create visual rhythm.

Imported from the Red lines section of the Halo guidance.

halo.visual.components.do-not-place-ordinary-paragraphs-in-cards-merely-to-create-visual-rhythm

must

Empty and loading states communicate system work without decoration, false certainty, or celebratory motion.

Imported from the Rules section of the Halo guidance.

halo.visual.components.empty-and-loading-states-communicate-system-work-without-decoration-fals

must

Every component specification includes purpose, usage, variants, spacing, accessibility, approved examples, rejected examples, and source ownership.

Imported from the Rules section of the Halo guidance.

halo.visual.components.every-component-specification-includes-purpose-usage-variants-spacing-ac

must

Evidence cards show the artifact directly and keep provenance close enough to preserve trust.

Imported from the Rules section of the Halo guidance.

halo.visual.components.evidence-cards-show-the-artifact-directly-and-keep-provenance-close-enou

must

Forms name the current state, the reason, the next action, and any evidence or privacy consequence.

Imported from the Rules section of the Halo guidance.

halo.visual.components.forms-name-the-current-state-the-reason-the-next-action-and-any-evidence

must

Metric cards use one primary number with unit, timeframe, source, and plain-language interpretation.

Imported from the Rules section of the Halo guidance.

halo.visual.components.metric-cards-use-one-primary-number-with-unit-timeframe-source-and-plain

must

Navigation keeps literal labels, stable placement, clear active state, keyboard access, and predictable disclosure.

Imported from the Rules section of the Halo guidance.

halo.visual.components.navigation-keeps-literal-labels-stable-placement-clear-active-state-keyb

must

Section dividers reset attention with short labels, quiet numbering, and measured rules rather than chapter art.

Imported from the Rules section of the Halo guidance.

halo.visual.components.section-dividers-reset-attention-with-short-labels-quiet-numbering-and-m

must

Workflow components use numbered steps, equal geometry, state labels, and explicit inputs and outputs.

Imported from the Rules section of the Halo guidance.

halo.visual.components.workflow-components-use-numbered-steps-equal-geometry-state-labels-and-e

Guidance set

Recognition

must

Attach proof to every claim that asks for belief.

Imported from the Rules section of the Halo guidance.

halo.visual.recognition.attach-proof-to-every-claim-that-asks-for-belief

must

Count the Magenta moments and keep one dominant active proof, capture, source, or decision event.

Imported from the Rules section of the Halo guidance.

halo.visual.recognition.count-the-magenta-moments-and-keep-one-dominant-active-proof-capture-sou

must-not

Do not approve an artifact that becomes generic SaaS, generic automotive, or generic AI when the logo is removed.

Imported from the Red lines section of the Halo guidance.

halo.visual.recognition.do-not-approve-an-artifact-that-becomes-generic-saas-generic-automotive-

must-not

Do not approve an artifact with competing focal points, unsupported evidence, unreadable density, decorative Magenta, or untracked assets.

Imported from the Red lines section of the Halo guidance.

halo.visual.recognition.do-not-approve-an-artifact-with-competing-focal-points-unsupported-evide

must-not

Do not treat visual similarity alone as proof of compliance.

Imported from the Red lines section of the Halo guidance.

halo.visual.recognition.do-not-treat-visual-similarity-alone-as-proof-of-compliance

must

Establish one unmistakable first read: headline, proof visual, then source caption.

Imported from the Rules section of the Halo guidance.

halo.visual.recognition.establish-one-unmistakable-first-read-headline-proof-visual-then-source-

must

Keep captions, metadata, source labels, footers, and navigation readable without zooming.

Imported from the Rules section of the Halo guidance.

halo.visual.recognition.keep-captions-metadata-source-labels-footers-and-navigation-readable-wit

must

Preserve hierarchy, spacing, and proof when translating the artifact into a slide, webpage, mobile screen, PDF, poster, or booth wall.

Imported from the Rules section of the Halo guidance.

halo.visual.recognition.preserve-hierarchy-spacing-and-proof-when-translating-the-artifact-into-

must

Remove the logo and confirm the artifact still feels like Halo through exact alignment, a neutral field, restrained Magenta, evidence geometry, source labels, and calm mechanical behaviour.

Imported from the Rules section of the Halo guidance.

halo.visual.recognition.remove-the-logo-and-confirm-the-artifact-still-feels-like-halo-through-e

must

Test density at the intended viewing distance; shorten, split, or reflow content instead of shrinking it.

Imported from the Rules section of the Halo guidance.

halo.visual.recognition.test-density-at-the-intended-viewing-distance-shorten-split-or-reflow-co

must

Trace every reusable visual back to the Source Library and its rights record.

Imported from the Rules section of the Halo guidance.

halo.visual.recognition.trace-every-reusable-visual-back-to-the-source-library-and-its-rights-re

must

Use cards only when the content behaves like a governed object, choice, evidence record, asset, metric, or workflow step.

Imported from the Rules section of the Halo guidance.

halo.visual.recognition.use-cards-only-when-the-content-behaves-like-a-governed-object-choice-ev

must

Use motion only when it clarifies target, alignment, capture, progress, or a state change.

Imported from the Rules section of the Halo guidance.

halo.visual.recognition.use-motion-only-when-it-clarifies-target-alignment-capture-progress-or-a

must

Use the canonical neutral sequence: Canvas, Paper or Raised object, Structure rule, and one Magenta state.

Imported from the Rules section of the Halo guidance.

halo.visual.recognition.use-the-canonical-neutral-sequence-canvas-paper-or-raised-object-structu