# Surface grammar

## Field

Canonical always-live projection. Scenes hold stable identity; paired Portals join contexts; ACTIONS remain at objects; Ki is continuously reachable.

## Studio

Desktop working distance: Projects, materials, package inspection, Ally/Actor benches, collaboration, authoritative diffs, complex acceptance. No IDE or file-tree metaphor.

## Live

Mobile human distance: navigation, presence, capture, Relationship lens, simple approvals, “at my desk later.” No full Studio or complex grant/package acceptance.

## Express

Browser surface: quiet registration state, honest unregistered response, page/domain proof, provenance, and Ally-mediated open-web Actions.

## TV

Ten-foot shared-safe presence. D-pad/OK/back. No signatures, money, balances, wallets, building, or per-person accounts.

## Attention depth and member-facing Transparency

Clear: Field leads. Context: balanced. Focus: information surface leads. `HUD` is internal builder vocabulary and must not appear as the label of a member-facing control.

Render the member-facing override as **Transparency**, from `0% · Opaque` to `100% · Clear`. Set it automatically from context, allow the Persona to override, and return control to Auto when requested. Focus normally reduces Transparency; ambient presence increases it. Gold only marks a signed act entering/changing an Organization Record.

## Conversational choices

Render only two chip types:

- Suggested prompt: quiet, secondary words the Persona may choose to say.
- Primary Action: a visually primary CTA for an Action Ki is ready to take, with its consequence available before execution.

Never render retrieval headings, citations, internal modes, taxonomies, or capability labels as conversational chips.
