# Moujave Brand Asset Governance

## Authority

Use this order when brand material conflicts:

1. `docs/standards/moujave-brand.md` — canonical brand standard.
2. `docs/brand/moujave-content-reference.md` — approved practical copy and examples.
3. `sites/moujave/assets/brand/` — public implementation references and generated-asset records.
4. Individual derived assets — outputs that may be regenerated or replaced.

GitHub is the source of truth. The public page at `https://moujave.com/assets/brand/` is the deployed view of reviewed files.

## Asset classes

### Canonical assets

Canonical assets define the identity and require explicit approval before replacement:

- `/assets/moujave-mark.svg`
- `docs/standards/assets/moujave-logo.png`
- the language and palette in `docs/standards/moujave-brand.md`

### Production assets

Production assets are approved for current live use but may evolve through review:

- `/assets/moujave-mountains.webp`
- `/assets/moujave-mountains-960.webp`
- `/assets/moujave-social.jpg`
- the current fingerprinted social image recorded in `/assets/brand/generated-assets.json`

## Public privacy rule

Public asset references must not expose private account identifiers, personal email addresses, legal names, private repositories, internal infrastructure or non-public operational details.

Public references should describe the Moujave identity and the approved asset process only.

## Stable and fingerprinted URLs

Use stable URLs for human convenience and internal references. Use fingerprinted URLs for cache-sensitive social metadata.

- Stable social image: `/assets/moujave-social.jpg`
- Current social image: read `socialPreview.fingerprintedPath` from `/assets/brand/generated-assets.json`

## Change process

1. Update canonical documentation first when the meaning, voice, logo or palette changes.
2. Update public references so they agree with the canonical documentation.
3. Generate or export derived assets using the documented recipe.
4. Validate dimensions, format, legibility, source references and public privacy rules.
5. Review the public asset page and direct asset URLs.
6. Merge through a reviewed pull request.

Do not publish generated images with baked-in private details, direct private-account links or internal implementation references.

## Current generation commands

From the Dev Platform repository:

```bash
npm install --no-save sharp
node --check scripts/generate-moujave-social.mjs
node scripts/generate-moujave-social.mjs
```

## Validation checklist

Before merge, confirm:

- canonical language matches the brand standard;
- logos remain the approved geometric purple M;
- generated backgrounds contain no baked-in logos, text or interface controls;
- public files contain no private identity references;
- social metadata uses the approved fingerprinted image;
- the public brand gallery contains only approved references.