# J1 · Recognize the same company across surfaces

Scenario specification, revision 1. An editor introduces an OpenBoa project. A reader later encounters it in the product and an agent roster.

[I21 · Recognize an OpenBoa screen in everyday use](../../intents/identity/I21-recognize-an-openboa-screen/intent.md) · [I01 · Recognize who is signing a surface](../../intents/identity/I01-sign-a-surface/intent.md) · [I02 · Know what happened and what to do next](../../intents/language/I02-write-in-context/intent.md) · [I03 · Use one palette across the product](../../intents/foundations/I03-choose-system-colors/intent.md) · [I04 · Read and operate the same layout at different sizes](../../intents/foundations/I04-read-at-any-size/intent.md) · [I05 · Recognize the right artwork at message size](../../intents/artwork/I05-choose-recognizable-art/intent.md) · [I06 · Recognize an agent before it moves](../../intents/artwork/I06-recognize-an-agent/intent.md)

| Step | Required observation | Reject this substitute |
| --- | --- | --- |
| Sign the company introduction. | The company signature and approved copy survive the handoff from editor to web. | A project emoji fills the company signature slot. |
| Open a project header or release note on paper and ink. | The project food mark, surface tokens, type and wording can be traced to the same kit revision. | The colors happen to match but come from a locally invented palette. |
| Narrow the screen and reduce motion in the roster. | The agent and its state stay identifiable by name, fitted outline and text. | The roster requires motion or a hue distinction to identify its state. |

The brand owner chooses expression and the project owner chooses the actual subject and facts. If a mark cannot load, retain readable attribution.

[Design portfolio](../../README.md)
