Chapter 4: Research Packets

Created by Sarah Choi (prompt writer using ChatGPT)

Research Packets (Taxonomy, Specs, Language / Typography References)

A research packet is the bridge between open‑ended exploration and reliable production. It is a compact, source‑backed bundle that defines what we call things (taxonomy), how they are built and measured (specifications), and how they speak to users in‑world (language and typography references). For prop concept artists, a good packet accelerates ideation, prevents rework for modelers and look‑dev, and keeps diegetic UI consistent. This article outlines how to assemble research packets grounded in fieldwork, disciplined collections, and clear ethics—equally useful to concepting and production sides.

1) Purpose and outcomes

Research packets turn raw reference into an actionable standard. When complete, a teammate should be able to design or model a new prop in the same family without asking for clarifications. The packet determines the naming system, locks critical dimensions and tolerances, codifies interaction rules, and supplies language/typography assets that read inside the fiction. Treat it like a mini‑design system for a prop line.

2) Core sections of a packet

Overview. One page stating scope (e.g., “Portable analyzers, Gen‑3”), target users, and contexts (handheld / tabletop / installed). Include two sentences on tone (utilitarian, ceremonial, etc.).

Taxonomy. A controlled vocabulary for parts, states, and interactions. Provide plain‑language names plus technical synonyms. Define parent/child relationships (assembly → sub‑assembly → component) and list aliases to prevent drift across teams. Include a short “do/don’t” on word choice (e.g., “Use ‘latch’, not ‘clip’”).

Specifications. Orthographic guides, module pitches, envelope sizes, grip diameters, wall thickness ranges, bevel hierarchies, fastener families, connector standards, and LOD survival rules. Express numbers both in real units and in screen‑space targets (pixels at typical gameplay distance) so readability is preserved.

Interaction & states. Diagrams of stowed/ready/fault with silhouette deltas, hinge axes, travel distances, interlocks, and non‑bypass sequencing. Annotate minimum clearances for fingers, cables, and tool access.

Language & typography references. A diegetic UI kit: typefaces (or invented alphabets), numeral style, stroke weights, icon grid, label hierarchy, wrapping rules on cylinders, and minimum sizes that remain legible. Include localization notes for long strings and right‑to‑left languages where relevant.

Materials & finishes snapshot. Edge behavior (fillets, chamfers), roughness bands, coating logic, and wear archetypes tied to function. Provide three‑read swatches (distance/mid/close) that demonstrate how the finish supports silhouette.

Sources & ethics. A list of fieldwork dates/locations, museum or archive accessions, permissions or licenses, and cultural consultation notes. Add any “off‑limits” motifs or brands.

3) Fieldwork that earns authority

Primary capture makes packets trustworthy. Plan site visits for analogs: homes and labs for domestic/sci‑fi, workshops for industrial, museums for historical, and guild studios for fantasy craft logic. Photograph at three distances (context, three‑quarter, macro), record scale markers, and sketch motion paths and joinery. Pair photos with short audio notes that you later transcribe into the packet’s metadata. Fieldwork also includes conversations: interview users or technicians about failure points and maintenance—these insights shape specs and wear patterns.

4) Building the taxonomy: names that design

Names shape decisions. Begin with the user’s mental model: what would a novice call this part? Add technical terms in parentheses for searchability. Structure the taxonomy as a tree with reusable sub‑assemblies (e.g., “Guard → Flip‑Cover (spring‑hinged) → Detent Pin”). Standardize verbs for interactions (press, pull, rotate, slide, lift) and map them to affordance shapes. Provide a compact glossary at the end of the packet and use the same labels in orthos and callouts to avoid cross‑team confusion.

5) Specifications that survive camera and LOD

Specs must protect readability, not just realism. For each principal dimension, include: real‑world range, gameplay screen‑space minimums, and tolerance bands. Define minimum radii for touch zones, minimum edge thickness for tips/fins, and bevel step widths that hold highlight bands at distance. Lock module pitches for arrays (vents, fasteners, rails) so variants remain coherent. Include a short LOD plan: which silhouette edges and voids must remain distinct to LOD2, and which micro‑details may collapse into baked normals.

6) Interaction and state logic

Show how the object changes. Provide clean silhouette pairs (“stowed → ready,” “safe → armed,” “open → locked”) and label non‑bypass sequences with orthogonal motions (lift, then slide). Mark hinge axes, slide rails, and interference geometry so rigging cannot accidentally permit illegal motion. Include clearance callouts for gloves and sleeves. If alarm or feedback exists, specify mechanical tells (flags, windows) before emissive lights, so the read survives harsh lighting.

7) Language & typography: diegetic UI that scales

Select or design type that fits the fiction and pipelines. Define primary and secondary fonts (or glyph sets), numeral forms (lining vs. old‑style), permitted weights, and a base stroke thickness that remains crisp at minimum pixel size. Provide an icon grid (e.g., 24×24 with 2‑px stroke) and a handful of core icons (power, access, hazard, alignment) drawn in that grid. Document label hierarchy (serial plates, caution boxes, micro‑captions) with examples on flat and curved surfaces. Include wrapping/kerning policies for cylinders and minimum contrast ratios in grayscale so labels read even when color grading shifts.

8) Collections and versioning

Store packets with version numbers (“RP‑ANLYZR‑G3 v1.2”) and changelogs. Bundle the following files: PDF of the packet, source photography thumbnails with IDs, orthographic overlays, icon/typography assets (SVG/TTF), measured sketches, and a license/permissions text. Maintain a central index that lists active packets and their owners so teammates know which bundle is authoritative.

9) Ethics and cultural respect

Treat sources with care. Obtain permissions for private workshops and proprietary machinery. Credit museums and comply with reproduction limits. When referencing living cultures, abstract structural principles rather than lifting sacred symbols; seek consultation, log guidance, and record any restrictions. Avoid copying distinctive contemporary product silhouettes; combine multiple influences and focus on construction logic. Include a simple “Ethics Notes” page in every packet summarizing permissions and red lines.

10) Cross‑genre guidance

Domestic. Emphasize ergonomic ranges, child‑safety features, water/grease wear, and appliance standards (plug types, hose threads). Language refs should include friendly icons and soft stroke weights.

Industrial. Prioritize module pitches (racks, ladders), lockout/tagout hardware, valve/gauge conventions, and service clearances. Typography leans toward stencil or DIN‑like clarity; icons favor high legibility.

Sci‑Fi. Extrapolate from real connectors, thermal paths, and vacuum hardware. Define speculative icons and a numeric grammar that feels engineered. Lock shell radii and seam logic so variants stay coherent.

Fantasy. Build from craft processes (forging, carving, weaving). Specs define joinery thicknesses and allowable ornament depth. Language assets may be runic or calligraphic; provide transliteration rules and spacing so text stays consistent.

Historical. Narrow date and locale; cross‑check catalog dimensions. Include period typefaces or letterforms, scribal abbreviations, and signage conventions. Annotate conjectural reconstructions to avoid false precision.

11) Production‑minded handoff

End each packet with a one‑page “Spec at a Glance”: key dimensions, silhouette non‑negotiables, interaction sequence, material stack, label sizes, and icon kit. Provide orthographic templates and a hero angle with notes on FOV and intended on‑screen size. Add a checklist for modelers (bevel widths, wall thicknesses, LOD survival), for riggers (axes, limits, order of operations), and for texture artists (roughness bands, decal scale, wear placement). This ensures the packet moves cleanly from concept wall to engine.

12) Common pitfalls and how to avoid them

Taxonomy drift. Teams invent synonyms. Fix: publish a glossary and enforce labels in callouts.

Spec myopia. Realistic numbers that kill readability. Fix: include screen‑space targets and test in engine early.

Typography that won’t ship. Fancy type that moirés or blurs. Fix: set minimum pixel sizes and stroke weights; test curves on cylinders.

Ethics gaps. Unlicensed or sensitive sources. Fix: log permissions; substitute original studies for restricted images.

Packet sprawl. Too long to read. Fix: keep the “Spec at a Glance” page brutally concise and link to deeper sections.

13) A repeatable workflow

  1. Define scope and questions the packet must answer.
  2. Do fieldwork (photos, sketches, interviews) and log permissions.
  3. Build taxonomy tree and glossary from user language and technical terms.
  4. Create orthographic overlays; lock specs with real and screen‑space values.
  5. Diagram states and interactions; test sequences with a quick blockout.
  6. Assemble language/typography kit and icon grid; test legibility at gameplay size.
  7. Compile materials/finishes with three‑read swatches and edge behavior.
  8. Write ethics notes and sources; version the packet and export the bundle.
  9. Run a cross‑discipline review (concept, modeling, rigging, look‑dev) and revise.

Research packets are living contracts. When anchored in fieldwork, disciplined taxonomy, readable specs, and coherent language assets, they enable rapid invention without sacrificing credibility. Build them as shared tools—not private notebooks—and your props will stay consistent, legible, and respectful from thumbnail to shipped asset.