---
name: norden-cinematic-web
description: Plan, build, review, and document Norden's cinematic multilingual catalogue, scroll stories, media pipeline, and editable admin content without inventing product or trade facts.
---

# Norden Cinematic Web

Use this workflow for Norden homepage storytelling, series scrollytelling, gallery/media work, animation systems, multilingual content, and the admin content model.

## Non-negotiable rules

- Never invent product specifications, certifications, factory processes, export countries, customer counts, years of experience, or logistics routes.
- Separate verified facts, user-approved facts, assumptions, and proposed creative scenes.
- A beautiful effect is not accepted until desktop, mobile, reduced-motion, keyboard, and performance checks pass.
- Keep source renders untouched. Generate web derivatives; never optimize by overwriting the only master.
- Do not add a WebGL/3D/video effect when CSS transforms, masks, responsive images, or a short compressed video can deliver the same result.
- User-editable copy, product attributes, translations, gallery items, and story chapters must move toward the admin data model rather than being repeatedly hard-coded.
- Record every material decision, failed attempt, correction, test result, and unresolved dependency in the SHIELD project notes.

## Workflow

1. Read the current roadmap and the relevant protocol:
   - For interaction and motion work, read [references/animation-protocol.md](references/animation-protocol.md).
   - For images/video, read [references/media-pipeline.md](references/media-pipeline.md).
   - For admin or language editing, read [references/admin-content-model.md](references/admin-content-model.md).
2. Prioritize the customer/supplier-facing digital catalogue. Admin work is deferred until the visual catalogue system is approved.
3. Define one bounded scene or system per implementation batch. Do not mix homepage, seven series, gallery, logistics, and deferred admin changes into one unreviewable patch.
4. Make a scene contract before code: verified content, source media, motion states, mobile composition, performance budget, and future content fields.
5. Build a representative pilot first. Approve Nexus or Nero before applying the pattern to all seven.
6. Validate lint/build, desktop/mobile, three languages, reduced motion, overflow, console, and performance.
7. Log the result and only then replicate or begin the next phase.

## Stop conditions

- Stop and ask for source material if a scene requires unverified export countries, production stages, certificates, machinery, partners, or shipment routes.
- Stop replication if the pilot is not visually approved.
- Stop adding effects if animation causes layout shift, scroll trapping, unreadable text, persistent GPU load, or poor mobile behavior.