--- title: "Asset Brief — {Class Name}" description: "{One-line: which manifest category and D-235 axis (if any) this class covers}" type: design status: active ticket: "" # e.g. "T-NNN" (the child story this brief gates) decision_refs: [] # e.g. [D-235, D-244, D-257] author: "Araminta" created: YYYY-MM-DD updated: YYYY-MM-DD --- # Asset Brief — {Class Name} One page. Gates the story below — a story with no linked brief does not enter `in_progress`. Cite standing conventions/palette rows; do not restate them. --- ## 1. Scope {Which manifest category (`furniture` | `props`, or "N/A — building-exterior texture, no manifest entry") and which D-235 ObjectTag axis (wall/roof/facade/ street), if any. State plainly what this class IS and is NOT — e.g. "station walls, not rural walls" — so the story can't scope-creep into a sibling brief's territory.} ## 2. Visual Reference {Cite `palette.md` §3's register row(s) for the relevant D-235 token(s) — hue range, grain, weathering baseline — by tag name, no restating the table. For classes with no D-235 token, cite `palette.md` §2 (toon default) or the D-257 glazing carve-out if the class includes glass/polished metal. Note any mood/reference touchstone specific to this class if palette.md doesn't already cover it.} ## 3. Naming {Cite `conventions.md` §1 (`_.glb` model naming), §2 (mask sidecar, single-channel vs RGBA multi-region) if tintable, §4 (`footprint_tiles` manifest field) if multi-tile. Give 1-2 concrete example filenames for this class. Note any class-specific naming wrinkle (e.g. door state handling — §5's negative constraint) rather than inventing new rules.} ## 4. Generation Path {The standing path: `/image-gen` concept → `/glb-gen` (Trellis) → Blender postprocess → promotion into `client/assets/models/{furniture,props}/` + `manifest.json` entry. Note class-specific concept-prompt guidance only if it differs from the standard `/image-gen` style-guide block (toon-shaded, near-white base, plain dark background, 3/4 front view). Note whether this class instead runs the `textures.md` (PBR standalone) or `artwork.md` (flat 2D) pipeline if it's not a `.glb` model.} ## 5. Acceptance {N starter assets entering `models.md` (or `textures.md`/`artwork.md`) and `manifest.json` at `planned` status. List them by name if known, or state the count + selection principle (e.g. "the generic fallback parent + 2 specific tokens"). Note the Q-119 milestone-0 caveat if relevant: generic parents are milestone-0 IF Q-119 resolves yes — do not resolve Q-119 here.} --- ## Cross-References - `docs/assets/visual/conventions.md` — naming/mask/footprint rules - `docs/assets/visual/palette.md` — D-235 color/material register, toon/PBR treatment - `docs/assets/visual/models.md` (or `textures.md`/`artwork.md`) — the catalog this brief feeds - `client/assets/models/manifest.json` — the machine-readable registry - `.claude/skills/glb-gen/SKILL.md`, `.claude/skills/image-gen/SKILL.md` — production pipeline