# Design Experiments

## Experiment 1 — One-center shell

This is the recommended next design task. Do not begin with another Field map.

Create three connected high-fidelity desktop scenes in one visual direction and one active Realm.

### Scene A — Calm start

The user enters a Realm with no emergency.

Show:

- Realm identity and one-line purpose;
- Ki;
- one central conversational invitation;
- a concise attention brief with no more than three items; and
- the input.

Do not show:

- a module menu;
- a people panel;
- a grid of unrelated capabilities;
- wisdom, tools, calendars, or governance by default; or
- the Field.

### Scene B — Instrument appears

The user says: “Find a time for the steering group before Friday and prepare the decision.”

Show:

- Ki's concise response;
- one scheduling/coordination instrument inside the conversation;
- valid choices and the one conflict that matters;
- a draft agenda or decision context; and
- an Action proposal to send invitations.

Calendars and integrations should remain behind the result unless the user asks why.

### Scene C — Element becomes the work

In the Palo Alto Commemoration Realm, the user says: “Help Matt and me decide how the event should open.”

Show:

- the same main conversation;
- a Source set as compact attached Elements;
- Matt's bilingual-opening proposal;
- one Artifact or program Element expanded into a Lens or Stage;
- a clear human decision;
- source provenance; and
- the path to accept the change and create a Record.

Collaborators should appear through contribution and approval, not as the screen's permanent subject.

## Review questions

1. Is the Focus unmistakable within three seconds?
2. Does structured work feel like a continuation of conversation?
3. Can the user tell what each Element is and why it is present?
4. Does the interface feel powerful without exposing the machinery?
5. Does the expanded Element support real work without becoming a generic dashboard?
6. Does the system feel warm, magical, and human with a restrained palette?
7. Is it clear what will happen before the user commits an Action?

## Experiment 2 — Reveal the machinery

Only after Experiment 1 is accepted, show the same scheduling instrument after the user asks:

> Why are these the only available times?

Open a Lens that reveals calendar sources, constraints, timezone, permissions, freshness, and one missing connection. This tests progressive disclosure and trust.

## Experiment 3 — Atlas and return

Only after the one-center shell is accepted:

1. Open the Atlas from the Palo Alto conversation.
2. Show only relevant Realms, related work, and the connection to Matt.
3. Enter Service Alliance or return to the project.
4. Preserve the conversation, selected Source, and pending decision.

This tests whether the Field supports orientation without taking over the product.
