# Refinement brief — Alice · The Field M0.3

## Assignment

Refine the existing Alice Field M0.3 into a warmer, clearer, more convincing living-world prototype. Do not redesign the overall product, add more screens, or introduce a broad component system. This round is about the felt quality and interaction of one Field distance.

The current prototype already establishes the correct structural direction:

- The Field is on the left.
- Ki is permanently on the right.
- Compute is fixed near the top and links to Resources.
- The outermost distance contains only Realms, labeled by their meaningful kinds.
- Realm selection opens a contextual Panel near the selected Realm.
- The title and interface stay still while the Field pans and zooms.
- Realm objects, relationship paths, and motes move subtly at rest.

Refine those choices. Do not replace them.

## The experiential problem

The Field must feel inhabited by people, relationships, work, and Wisdom—not like an empty space containing attractive buttons. A Source should understand where they are, notice one meaningful change, and know what to do next without reading a dashboard.

The design test is:

> Can Alice feel that these places continue to live, understand that Dunaversity needs attention, and move toward it with one obvious gesture—without the screen becoming busy or administrative?

## Required refinement focus

### 1. Living presence

Make each Realm feel like a place with continuing life. Use restrained local signs—movement inside a boundary, orbiting relationships, a brief pulse from recent change, small traces of people or Wisdom—without revealing lower-level Elements at this distance or adding status dashboards.

### 2. Spatial clarity

Make relative distance and relationship readable. The Field should respond immediately to drag, two-finger travel, wheel, and pinch. Movement should have appropriate inertia or settling only if it remains precise. Never animate the whole interface.

### 3. One next move

Dunaversity has one change awaiting Alice. Let that be noticeable without turning it into a notification badge. Ki’s primary Action is the clearest next step. Secondary controls should remain quiet.

### 4. Anchored context

When Alice selects a Realm, its Panel belongs visually to that Realm. The Panel may overlap or sit slightly offset, but part of the Realm remains visible. The relationship should survive panning and zooming.

### 5. Warmth without muddiness

Keep the ground crisp and neutral. Build warmth with cream typography, localized gold, coral, stone, and gentle living light. Do not use broad blue-green or brown washes.

### 6. Ki as present intelligence

Ki remains a stable right-side presence. Ki should notice the current selection, speak in Alice’s terse/exact rhythm, and offer one meaningful next Action. Ki may use a small number of contextual prompts or widgets when they reduce ambiguity; do not fill the panel with controls.

### 7. Compute truth

Available Compute is expressed in `$KIDUNA`, changes visibly with state, and always offers **Go To Resources**. In this prototype the changing value is a live fixture, not a production ledger. Preserve that honesty in the interface and implementation notes.

## Deliverables

Create `field-m0.3-refined/` containing:

1. Updated `StudioField03.tsx` and its CSS module.
2. Any new local assets used by the view.
3. A working static preview.
4. `CHANGELOG.md` describing only meaningful experiential or behavioral changes.
5. `TAXONOMY-IMPACT.md` stating either **No taxonomy change** with a reason, or naming each proposed change explicitly.
6. `OPEN-QUESTIONS.md` containing only decisions that genuinely require Moto. Do not use it to avoid making ordinary design judgments.

Do not alter M0, M0.1, M0.2, M1–M5, Outside the Field, Live, Express, or TV.
