# Moto feedback

Status: active owner-feedback log for Kiduna Design.  
Owner: Moto.  
Purpose: preserve direct feedback, active design constraints, and rejected directions so Moto does not have to repeat them.

Read this file before beginning or revising any Kiduna prototype. The latest dated note controls when two notes conflict. Prototype labels such as M0.1, M0.2, and M0.3 are design iterations, not claims of production ratification.

## Standing direction

- Work step by step. Make the next experience clear instead of expanding scope or presenting many competing options.
- Publish reviewable prototypes at `https://www.kiduna.design` and provide direct links to the exact view.
- Kiduna is a world inhabited by others and by Wisdom. It must not feel cold, clinical, administrative, empty, or like a dashboard.
- Keep each screen sparse. Give the Source one clear next move, with Ki offering a small number of useful chips, widgets, or Actions only when context calls for them.
- The Field should feel alive and spatial. Mouse and trackpad navigation should be immediate, fluid, and suitable as a behavioral study for a future Flutter/Flame implementation.
- In Studio, Ki is always on the right. No exceptions.
- In Studio, a fixed item near the top always shows available Compute in `$KIDUNA`, updates with live state, and includes **Go To Resources**.
- A Panel opened from a Realm sits in front of or slightly offset from that Realm. Keep part of the selected Realm visible so context is never lost.
- The outermost Field level contains only Realms. Do not label every object `Realm`; use its meaningful type: Organization, Alliance, Program, Project, Relationship, and so on.
- Keep the background crisp. Broad blue-green and brown casts make the Field muddy; confine color and glow to meaningful objects and relationships.
- Resting motion belongs inside the Field—breathing, drifting, orbiting, gathering—not in the entire viewport. Fixed orientation copy, Ki, Compute, and controls must not expand, contract, or drift.
- “The Field is alive” stays stable while the spatial Field beneath it remains highly responsive.

## Rejected directions

- Large navigation headers, simulated status chrome, walkthrough rails, Records/authority side menus, and other administrative framing inside the member experience.
- A cold collection of glowing buttons with little sense of people, Wisdom, relationship, or life.
- Too many options on one screen.
- Whole-view zoom or fullscreen behavior that enlarges the interface along with the Field.
- Panels detached from the object that opened them.
- Repeating system taxonomy when a specific human-readable type is more useful.
- Muddy full-screen color washes.

## Field iteration record

### 2026-07-22 — M0.1 · The Field as Alice

- Begin with the current Alice Field and revise it in place as a distinct prototype iteration.
- Put **M0.1 · The Field** immediately below M0 in the Design Lab View menu.
- Remove the internal Kiduna/Dunaversity header, mode controls, Persona menu, walkthrough side menu, Records summary, and authority summary.
- Show two starting Realms: Kinship Duna and Dunaversity.
- Let Alice navigate the Field, enter Dunaversity, see its Elements, and open appropriate Panels by selecting them.
- Ki should respond contextually and offer only appropriate chips and widgets.

### 2026-07-22 — M0.2 · The Field

- Use the warmer, inhabited Field direction represented by Moto's reference image and closest prior prototype.
- Make the world feel inhabited by others and by Wisdom.
- Use very few options on each screen and make the next move unmistakable.
- Support direct mouse and trackpad travel through the Field, responsive zoom, and an expanded view of the Field itself.
- Treat the web prototype as a living behavioral study for the later Flutter/Flame client.

### 2026-07-22 — M0.3 · The Field as Alice

- Keep Ki fixed on the right side of the Studio screen.
- Keep live available Compute near the top in `$KIDUNA` with **Go To Resources**.
- Show only Realms at this level, identified as Organization, Alliance, Program, Project, Relationship, or another specific type rather than with the generic eyebrow `Realm`.
- Open a Realm's Panel at or slightly offset from the selected Realm so the Realm remains partially visible.
- Remove broad blue-green and brown background casts and use a crisp ground.
- Add subtle resting movement to the Field.
- Keep “The Field is alive,” Ki, Compute, and controls stable. Pan and zoom only the spatial Field, and make it highly responsive.

## Maintenance rule

When Moto gives new design feedback:

1. Add it here under a dated heading before considering the iteration complete.
2. Promote enduring rules into `DESIGN-CANON.md` and the relevant Surface grammar.
3. Record rejected directions as explicitly as desired directions.
4. Update the route registry and documentation when a new labeled prototype is created.
5. Preserve earlier iterations as provenance unless Moto explicitly asks to replace or remove them.
