# Claude Design implementation brief

## Objective

Bring the existing Kiduna Studio model and the new Ally system into one visual and behavioral language. Implement the full design system demonstrated by the included site, with special attention to:

1. Studio — Field ground & ambient motion
2. Studio — Realms
3. Studio — Field taxonomy & Realm anatomy

This is an extension, not a replacement. Preserve the original Studio semantics, interaction contract, and owner constraints unless this handoff explicitly refines their visual expression.

## Core proposition

**Everything in the Field is alive. Allies carry faces; Realms carry crests; connections carry relationship. Emphasis follows relevance, not object class.**

All three share celestial-enamel material language:

- deep-umber lacquer ground
- tactile enamel color
- fine warm-metal rims
- moon-cream highlights
- celestial arcs, nodes, and relational filaments
- local reflected light
- slow meaningful motion

They remain distinguishable:

- Allies have faces, eyes, cheek sigils, identity adornments, and a moon-cream identity ring.
- Realms have custom geometric crests, semantic enamel structure, nested contents, and a celestial chassis. They never have faces.
- Elements are simpler functional medallions inside Realms.
- Ki keeps its nonhuman relational-constellation identity and does not become a Field object.

## Implementation order

1. Add the tokens in `STUDIO-ENAMEL-TOKENS.css` to the canonical Studio token layer.
2. Build the Realm emblem primitive from the supplied crest assets and its distance states.
3. Update the Field ground and motion grammar.
4. Implement click/Panel and approach/threshold entry using the same Realm primitive.
5. Implement nesting and recursive context.
6. Replace Source placeholders with approved Ally assets.
7. Apply taxonomy and Element hue rules.
8. Validate keyboard, pointer, trackpad, touch, reduced motion, narrow desktop, and small-avatar legibility.
9. Confirm no Realm taxonomy falls back to the old stock icon set.

## Reference priority

When references conflict, use this order:

1. This handoff’s Studio Enamel canon
2. The existing Alice · The Field system canon and owner constraints
3. The Ally system
4. The working design-system site
5. Presentation imagery

The site demonstrates intent. Production code must still use real data, honest states, and existing application architecture.

## Non-goals

- Do not redesign the entire Kiduna product outside Studio.
- Do not add generalized game mechanics, rarity traits, or NFT-style randomization.
- Do not turn Realm types into characters.
- Do not infer a Source’s emotion from camera, face, demographics, or private activity.
- Do not use expressive Ally state as evidence of legal intent or authorization.
