---
name: compose-kiduna-interaction
description: Turn a Kiduna user intention or capability into a precise conversational and spatial interaction. Use when designing a Studio flow, determining what appears in chat versus the Field, expanding an Element, proposing an Action, adding a gate or receipt, or specifying normal and exceptional states without falling back to a conventional form-heavy interface.
---

# Compose a Kiduna Interaction

Read [pattern-selection.md](references/pattern-selection.md) before selecting an interaction pattern.

## 1. Frame the interaction

Identify:

- the Actor and their intended outcome;
- the active Realm and current Focus;
- the relevant Elements, Actors, Sources, Connections, and Records;
- who may see, propose, authorize, execute, or reverse the Action;
- what must remain hidden until it becomes relevant.

Separate inherited requirements from proposals and expose contradictions.

## 2. Select the smallest sufficient pattern

Prefer a calm conversational surface. Introduce an instrument, lens, stage, or Atlas view only when it materially improves comprehension or control. Do not place multiple unrelated activities at equal visual weight.

Use this sequence when applicable:

`intention → grounded context → instrument → proposed change → gate → execution → receipt or recovery`

Not every interaction needs every step. Never omit authority, consequence, or recovery when they matter.

## 3. Specify progressive disclosure

For each Element, define only the lifecycle states needed from:

`signal → preview → address → lens → stage → pin → compare/compose → propose → gate → execute → receipt → recede`

“Chat with an Element” means that Ki or a relevant Actor grounds the exchange in the selected Element. Do not imply that an inert Artifact has become an autonomous agent.

## 4. Cover states and trust

Specify:

- starting, loading, empty, ready, changed, and completed states;
- insufficient context, permission, connection, Compute, and unavailable-Actor states;
- cancellation, retry, rollback, and return-to-Focus behavior;
- privacy/visibility cues, provenance, gates, and durable Records.

## 5. Deliver the interaction specification

Return:

1. concise user story and outcome;
2. inherited requirements, proposals, contradictions, and gaps;
3. surfaces and pattern choices;
4. step-by-step interaction states;
5. normal and exceptional flows;
6. conversational behavior and suggested prompts;
7. visual hierarchy and motion notes;
8. measurable acceptance criteria.

Avoid technical architecture unless requested.
