# Intent brief

> The root artifact everything else traces to (GENESIS-FLOW-DESIGN.md §0, conversation 0 of
> the genesis walk). This is prose, not a clause spec — no `// SPEC:` tags apply here, and
> `specCoverage` never scans this file (it only scans `specs/*.spec.md`). The `cmp-new`
> interview fills in the sections below before the design-language, architecture, components,
> and exemplar-feature conversations begin; each of those is expressed in the vocabulary this
> brief establishes.

## Purpose

_not yet captured — filled by the cmp-new interview._ What is this app, in one or two
sentences? What problem does it solve, and for whom?

## Audience

_not yet captured — filled by the cmp-new interview._ Who uses this app? One primary
audience beats a vague list — name them.

## Platforms

_not yet captured — filled by the cmp-new interview._ Android, iOS, or both? Any platform-
specific constraints (e.g. iOS-only feature, Android-first launch)?

## Brand feel

_not yet captured — filled by the cmp-new interview._ Two or three adjectives for how this
app should feel (e.g. "calm, trustworthy, minimal" vs. "playful, bold, energetic"). This
seeds conversation 1 (design language) — the candidates it proposes react to what's written
here.

## Reference apps

_not yet captured — filled by the cmp-new interview._ One to three apps whose look, feel, or
interaction patterns this app should be judged against ("closer to X than Y").

## First screens

_not yet captured — filled by the cmp-new interview._ What are the first 2–4 screens you see
in your head? This grounds conversation 4 — the exemplar feature is the user's *actual* first
feature, not a generic placeholder.

## Glossary

_not yet captured — filled by the cmp-new interview._ The domain nouns specific to this app —
one line each, in the app's own vocabulary, not generic template terms (e.g. "**Trip** — a
single planned outing with an itinerary and companions", not "**Item**"). Usually falls out of
the Purpose/First screens answers above; confirm the list with the human rather than guessing.
This section is lifted verbatim into `docs/ARCHITECTURE.md` §8 — write it in the form you want
published: a Markdown bullet list, `**Term** — definition` per line.