0451fbe00a
The project owner supplied artwork and a full visual brand guide mid-session, which answers #8: the three marks an agent must not fake now exist because a person made them. docs/data/img now holds icon.webp (512x512, 11 KB), logo.webp (1024 long edge, 28 KB) and banner.webp (2176x725, 20 KB) — all webp by magic bytes, all far under the 512 KB ceiling. Produced from the supplied art rather than invented. Two things had to be handled rather than converted blindly. The sources render their rounded corners against black, so a naive crop carried black wedges into the banner; the corners are flood-filled to the artwork's own ground first. And the lockup is square, so a 3:1 crop would have cut the wordmark in half — the banner is the whole lockup on a matching ground, which has no seam to see because the artwork's edges ARE that ground. The source PNGs and the guide moved to docs/design/: docs/data/img is for the three marks the Command Center renders, and its README is explicit that reference art and exported sources do not belong there. THE PALETTE, AND ONE DELIBERATE CONFLICT core/designsystem now carries the guide's colours — deep plum, rich purple, period rose, lavender mist, and an eggplant dark theme that is never flat black. §39 of the specification asks for a muted teal or sage fertile window, to hold it apart from the period colour. The guide is plum and rose throughout and gives fertility its own pink. The guide wins: it is newer, it is the owner's, and a teal accent inside this identity would look borrowed from another app. What §39 was protecting is kept by other means, and this is why the conflict is safe to resolve that way: the calendar's states differ in SHAPE. A solid disc, a dotted ring, a continuous ring and a star stay tellable apart in greyscale and to a colourblind user, which is what §43 actually requires. The departure is written down in docs/design/README.md rather than left to be discovered. The launcher icon keeps its vector for now, in brand colours. The supplied emblem has content close to its edges and an adaptive icon masks about a quarter of the canvas away, so dropping it in unmodified would crop the shield. Fitting it to the safe zone is Batch 08's final-artwork work. closes #8 |
||
|---|---|---|
| .. | ||
| README.md | ||
| banner.webp | ||
| icon.webp | ||
| logo.webp | ||
README.md
Project images
Status: Current
Owner: _null
Last reviewed: 2026-08-18
Governs: docs/data/img/** — the three files and their sizes
Review trigger: A rebrand; any change to a required name, dimension or ceiling;
any change to what the consumer accepts.
Three files, all webp, all required, at exactly these names:
| File | Dimensions | Aspect | Typical weight |
|---|---|---|---|
icon.webp |
512 × 512 | 1:1 | 8–60 KB |
logo.webp |
1024 on the long edge | whatever the lockup is | 20–190 KB |
banner.webp |
2176 × 725 | 3:1 | 30–130 KB |
Not icon.ico. The consumer checks the file's magic bytes, not its name: a
.ico, or a PNG renamed to .webp, is refused with a 415 and the project falls
back to an initials tile. That signature check is what makes it safe to render
these inline, so it is not going to be relaxed.
512 KB is a hard ceiling per file, enforced in code — the size is read from the listing before the bytes are fetched, so an oversized asset is never downloaded and simply never appears. Nothing enforces the dimensions, which is why they are written down.
Making them
magick logo-source.png -resize 512x512 -quality 82 icon.webp
identify -format '%f %wx%h %b\n' *.webp # check before committing
Quality 80–85 suits a flat mark. If a file lands over ~200 KB it is usually a photographic banner that wants a lower quality rather than fewer pixels.
Why these numbers
The icon renders small — a 44 px tile in a list, 58 px on a project header — so 512 covers the densest display several times over; the reference project deliberately halved it from 1024. The banner spans a card about 760 px wide, so ~2176 covers it at 2×, and its 3:1 shape matters more than its width because the header crops to fill. The logo has no fixed frame, so only its long edge is specified.
Extra sizes and variants are welcome beside these — icon-512.webp,
logo-dark.webp. Only the three exact names are checked for.
No placeholders ship with this template. An empty file is the worst of the three states: a check that asks whether the path exists calls it present, and anything reading the bytes rejects it. Absent is honest, and the conformance check reports it as absent — which is what gets it filled in.
Why the requirement exists, and what reads it: ../README.md.