# I21 · Recognize an OpenBoa screen in everyday use

Status: DRAFT, revision 2. Decision owner: OpenBoa design-system owner with the company identity maintainer. Source: [product intent, revision 1](../../../intent.md). [Paired specification](spec.md) · [Recognize the same company across surfaces](../../../journeys/J1/README.md).

## Need

A team building an inbox or a record detail should be able to compose a screen that feels like OpenBoa even when the company logo is outside the viewport.

## Success and counterexample

**Success.** Compare a Meatball review, Sourdough detail and agent roster in light and dark examples. Each has a clear first read, a common typographic rhythm and only the emphasis its task needs.

**Convincing failure.** Every surface has the same generic stack of rounded cards, lightly colored badges and a floating mascot. The layout is quiet but the decision, evidence and available action are impossible to rank.

## Limits

The brand owner owns art direction, foundation tokens and shared expression. Products own the facts, consequences and order implied by their tasks. The system-wide primary is the original symbol’s Ink blue, slate.750 (#175174).

[Visual direction](../../../design-direction.md) · [Type scale](https://yogurt-theta.vercel.app/system.html#type) · [brand.json](../../../../design/tokens/brand.json) · [Product playbook](https://yogurt-theta.vercel.app/playbook.html) · [Component foundation](../../../component-foundation.md)
