# 02 — Experience strategy

Cites `brand/CANON.md`. Does not contradict it.

## Product promise

Give AI product builders a readable presence during latency — mountable today, honest about limits, activated by a file on disk.

## North-star experience

Within one minute a builder talks to a companion, configures a **free** creature, and opens an offline starter — without creating an account or clicking a fake Buy button.

## Experience principles (checkable)

1. **Presence over decoration** — every motion maps to `presence.state` or attention/react.
2. **Honesty under uncertainty** — local vs live; waitlist vs checkout; free vs try.
3. **Activation is a file** — success = starter/`glim.js` on disk.
4. **One loud thing** — hero demo first; gallery second; never compete with confetti.
5. **Ration the accent** — mood teal for action/alive only.
6. **Junior Friday filter** — no invented metrics or buy theatre (Canon).

## Primary value path

`discover → try demo → configure free creature → download → integrate → return → waitlist/feedback`

Friction to remove: unclear free eligibility, buried downloads, over-exposed native stack tabs, unreadably faint meta text.

## Success measures

- Downloads (north star)
- Feedback yes-rate; kill at <20% after 50 taps
- Pro/Team notify emails
- (New) visits to `/design` / `/brand` as secondary docs engagement — optional

## Core flows (see 06)

Demo ask · Configure+download · Gallery pick · Intent waitlist · Feedback signals