ALLOWLISTED DURABLE SOURCE

exhibition-space-design-system.md

docs/exhibition-space-design-system.md

This is the retained record itself—not a chat summary. It is exposed because it materially documents the research, method, evidence, audit, production, planning or release history of The 100.

# Selected Visual World — Exhibition Space

Status: SELECTED / system-wide design development

## Decision
The public destination will use the Exhibition Space concept as its canonical visual world. This is not a homepage skin. The entire experience must behave like a digital exhibition of functional systems, visual arguments, and infrastructure lineage.

## Core metaphor
Visitor, not user. Exhibition, not portfolio grid. Works/objects, not project cards. Rooms, walls, labels, plinths, accession numbers, routes, archive, study room, and practice desk are available information-architecture metaphors where they improve comprehension.

## Non-negotiable
No route may fall back to the former RN Builds visual language. The selected world must propagate to homepage, exhibition index, individual build case studies, A-side tools, B-side motion presentation, lineage, visual-build archive, about/practice, contact, mobile, empty/error states, and navigation.

## Proposed rooms
- Entrance / orientation
- The 100 / main exhibition
- Current work / newest accession
- Visual Builds / screening room
- Lineage / infrastructure room
- Field Notes / study room
- Practice / work with RN
- About / curator-builder context

## Build object anatomy
Every numbered cycle is one accession with two primary objects:
- A — functional system
- B — visual argument / reveal

The wall label/case-study record should expose: question, proposition, use case, build status, domain intersections, evidence/research basis, interaction, what it leaves behind, inherited infrastructure, limitations, build log, and related works.

## Conversion principle
Contact is contextual rather than a generic sales banner. After a visitor experiences a build, the site can ask whether they are facing a related system problem and route them to the Practice room/contact surface.

## Design development still required
Typography system; spatial grid; motion language; room transitions; object/plinth treatment; labels; responsive/mobile translation; accessibility; tool UI integration; motion-screening presentation; lineage visualization; contact/practice architecture; real content density testing; performance; browser QA.