# Creative brief template pack

This pack helps a creative lead turn a campaign or design request into bounded, reviewable direction. It records the business and user problem, evidence-backed audience, objective, message hierarchy, deliverables, constraints, source facts, assumptions, rights status, reviewer roles, feedback route, approval handoff, success-measure definitions, and revision history.

## Files

- `creative-brief-template.md` is the editable Markdown worksheet.
- `creative-brief-example.md` is a completed fictional example.
- `creative-brief-example.json` is the same fictional example as structured data.
- `creative-brief.schema.json` is a closed Draft 2020-12 JSON Schema.
- `validate-creative-brief.mjs` is a dependency-free structural and cross-reference validator.
- `validate-creative-brief.test.mjs` contains deterministic positive and negative contract tests.
- `build-pack.mjs` rebuilds the ZIP from an exact flat-file allowlist with fixed metadata.

## Verify the pack

```bash
npm test
npm run validate
npm run build
```

## Use the template

1. Copy the Markdown worksheet and the JSON example into a private working area.
2. Replace the fictional facts, roles, reserved URLs, assumptions, and deliverables with reviewed project information.
3. Link every audience claim and support message to a source fact or mark the gap as an assumption with a validation route.
4. Keep rights, accessibility, feedback, and external approval states explicit. A brief can request or route these checks; it cannot grant clearance.
5. Run the validator after every structured-record edit, then review the Markdown for parity and useful creative latitude.

The example is fictional. `Juniper Way`, its role identifiers, paths, and `example.test` URLs do not identify a real person, organization, campaign, or asset. The pack contains no finished copy or artwork, project plan, procurement record, product requirements, design-system tokens, media budget, legal decision, production authorization, or promised outcome. Validation proves internal consistency and safety constraints only.