# Built the company's whole visual identity from two hand‑made drawings, with every derived asset regenerated by script and a check that fails when a derived file is older than its source. 2025 **Situation.** A small company's visual identity is usually bought, generated, or assembled from stock, and the result is an identity that belongs to nobody. The alternative problem is worse: hand‑made artwork that exists only as exported files, where the source drawing is lost, the exports are edited directly, and within a year the versions in use disagree with each other and no original remains to settle it. **Task.** The identity had to be drawn rather than sourced, and the pipeline from drawing to published asset had to be reproducible, so that every file on the site is derivable rather than kept. **Action.** There are exactly two hand‑made source drawings — the company mark and the mascot — and everything else is generated from them. The mark is a vector source; the mascot is an illustration reused across thirty published images. From these, scripts produce every derived form: the favicon set in its required sizes, the touch icons, the social preview images, the responsive raster variants at each width and in each modern format, and the theme‑specific versions. The generation is a task anyone can run, so the question "where did this file come from" has an answer that is a command. The staleness check is the piece that makes it hold: it compares the modification time of every derived asset against its source and fails when a derived file is older, which catches the exact failure this design exists to prevent — someone edits the source, forgets to regenerate, and the published site keeps showing artwork that no longer matches the original. The rule that derived files are never edited by hand is stated where the sources live. **Result.** Two drawings produce the entire published identity, regeneration is one command, and a stale asset fails the build. The trade‑off is a hard dependency on the toolchain: the derived files are committed so the site builds anywhere, but changing the identity requires the generation tooling to still work, and a source format that stops being readable takes the whole identity with it. --- - Role: Brand and Identity Designer - Categories: [Web Development](https://engineer.company/categories/web-development/), [Automation & CI/CD](https://engineer.company/categories/automation/), [Testing & QA](https://engineer.company/categories/testing/), [Design Systems & UI](https://engineer.company/categories/design-systems/), [UX / UI Design](https://engineer.company/categories/ux-ui/), [Brand & Marketing](https://engineer.company/categories/brand-marketing/) - Services: [Website Development & CMS](https://engineer.company/services/web-development/), [UI/UX Design & Design Systems](https://engineer.company/services/ui-ux-design/), [Brand, Marketing & SEO](https://engineer.company/services/brand-marketing/)