Prepare the right asset for each use
A logo needs more than one file: small icons, header compositions and sharing images have different constraints. Derived assets keep their relationship to the accepted source while declaring where each version belongs.
Example — A mark that works in a tab and a header
A compact symbol stays recognizable at icon size, while the header uses a wider composition. Both come from the same accepted identity rather than unrelated redesigns.
For engineers
The runtime asset query names the three decisions independently. This illustrative consumer query uses the public model exports and an existing runtime asset list:
const headerAsset = resolveBrandAsset(assets, {
composition: BrandAssetComposition.SYMBOL,
theme: BrandAssetTheme.DEFAULT,
purpose: BrandAssetPurpose.PRIMARY,
});
Import the resolver and enums from @wildo-ai/saas-models. assets is the accepted runtime projection, not a list of staging files. The caller uses the returned URL if present and its normal empty-brand fallback otherwise. Choose the composition appropriate to the actual surface.
Preserve derivation and serving information
Specification assets record their source relationship as well as composition, theme, purpose, format and dimensions. Validation checks duplicate slots and invalid derivation chains. Generation prepares the required formats; acceptance makes the set canonical; propagation places the files where their URLs resolve.
A master is source material, not a substitute for every small delivery asset. Check actual legibility, crop and background at the consuming size; declaring dimensions or a purpose does not itself make an image suitable.