direct

# Direct an original identity Read the current `board/project.json` and `board/DESIGN.md`. Understand the actual business, audience, approved material and delivery requirements. The starter is a fictional bakery example, not a default visual direction. Produce a system suited to the person's brief. For structure, read [the project format](references/project.md). The model and validator in `studio/project.mjs` are the executable contract. Layouts and symbols are arbitrary design data; there is no supported list of styles. Reuse an existing direction only when it fits the request. ## Make decisions visible in usable work Show how the identity works on the actual materials: packaging, signage, a pitch, social assets, stationery or another requested medium. A palette and moodboard by themselves are incomplete. If alternatives help the decision, author materially different geometry and hierarchy. If the person already approved a direction, extend it instead of asking them to select again. Use shared copy bindings for facts that should stay consistent. Use named color roles and embedded fonts for the visual system. Author each format's composition, keeping important text editable. Separate source artwork from staged applications through logo lockups and asset slots. Keep licensed input fonts and their redistribution licenses; do not bundle arbitrary system fonts. Put supplied image files under `board/assets/` and refer to them with `file`. The build embeds them. The supplied ...