# Yogurt product intent

An OpenBoa product team should be able to start with what a person came to do and build a recognizable, usable screen. Designers, engineers and agents need one source for how OpenBoa looks, speaks and behaves, from a company signature to a receipt after a lost connection. An independent product should be able to pin and use that source on its own.

**Recognizable success.** A new team can use Yogurt to design a revisioned decision or a partially observed record. From the same Yogurt revision, independent projects find the appropriate patterns, English language and supported components or identify a gap on their target. A reader can tell who is speaking, what is known and which action is available. Each project keeps its own facts, commands and release dates.

**Convincing failure.** Two screens share a font and rounded corners, yet both celebrate an unconfirmed result, hide the source of their data, or use an agent mark as the company logo. A gallery of screenshots alone cannot carry the system into a working client.

**Retained decisions.** OpenBoa owns the identity, shared conventions and component support claims. Each product owns its authority, data model, user tasks and production adoption. App clients use Vercel Native SDK as their default stack. The main brand color is the original symbol’s Ink blue, slate.750 (#175174). The production web behavior provider remains under review.

[Product specification](spec.md) · [Visual direction](design-direction.md) · [Working product examples](https://yogurt-theta.vercel.app/playbook.html)
