View source on GitHub →

ICN Visual Assets — Planning Layer

This directory is the planning layer for ICN visual explainers. It does not contain production assets, generated images, or shipped figures. It contains:

  • the asset register — the live list of planned and tracked visual assets
  • the visual review checklist — the gate every asset clears before it can ship
  • per-asset briefs under `briefs/` — one file per asset, named VE-NNN-slug.md

All three layers defer to the ICN Visual Explainer Bible for doctrine. The bible governs; this directory plans and reviews.

Where production assets live

Class Lives in Notes
Astro / SVG components `website/src/components/` Tokenized, themable, grayscale-tested. Canonical form.
Optimized raster assets used by the website `website/src/assets/` Goes through Astro's image pipeline.
SVG-in-docs figures Inline in the doc that explains them Hand-authored, design-token-grounded.
Mermaid diagrams Inline in markdown docs Structural diagrams only.

This directory does not host production assets. Production assets live where the consumer expects them.

Where sketches live

Generated-image sketches and exploration material live alongside the brief that motivated them, inside a sketches/ folder under the brief. Example: briefs/VE-005-kernel-app-separation/sketches/. The folder is not registered. Sketches never enter website/src/assets/.

Per the bible §11, sketches are not load-bearing and never become shipped assets.

Lifecycle

  1. Idea — captured as a row in ASSET_REGISTER.md. Status: planned.
  2. Brief — written to briefs/VE-NNN-slug.md. Status: briefed. Brief gate (bible §10) closes the brief to generation until satisfied.
  3. Sketch (optional) — exploration sketches live under the brief. Always labeled. Never load-bearing.
  4. Build — Astro / SVG / source asset implemented in the consumer (website or docs). Status: built.
  5. Review — runs the VISUAL_REVIEW_CHECKLIST.md. Status moves to shipped only when the review passes.
  6. Decay — when the substrate changes, the brief and the asset are re-reviewed. Status returns to briefed or moves to historical / do not use.

What does not go here

  • Brand kits for any institution package (NYCN, Summit, future packages).
  • Member personal data, even as fixtures.
  • Real partner / cooperative / member names.
  • Generated images promoted to "final."
  • Asset content for institution-specific surfaces — those live in the institution package's own repo.

See also

← Back to Docs