# UX Foundation

<!-- Managed with super-ux (ux-contract v4). The WHY layer: personas, jobs
to be done, customer journeys, user stories. Update when the understanding
of users changes; scenarios in scenarios.md trace to the IDs defined here. -->

## Personas

<!-- ### P-01: <name>
1-3 sentences: who they are, what they know, what they want. Grounded in
data/observation, recognizable by a real user. -->

## Jobs to Be Done

<!-- ### JTBD-01: <short job name>
- **Statement:** When <situation>, I want to <motivation>, so I can <expected outcome>.
- **Personas:** P-01
- **Type:** functional | emotional | social
- **Forces:** push: <...>; pull: <...>; anxiety: <...>; habit: <...>
- **Success metric:** <observable user outcome, not a feature>
-->

## Customer journeys

<!-- ### JRN-01: <persona> — <job> (JTBD-01)
| # | Stage | User action | Touchpoint | Emotion (1-5) | Pain | Opportunity |
|---|-------|------------|------------|---------------|------|-------------|
-->

## Monetization

<!-- When the product earns money (choose with data, BP-067..070):
- **Model:** hard paywall | freemium | hybrid | trial (type, length) — and why
- **Value metric:** <what the paid tier meters>
- **Free boundary:** <what stays free, where the visible limit sits>
- **Purchase surface:** in-app (IAP) | web checkout | web2app (web funnel -> app) — BP-030/BP-078/BP-127, and which storefronts
- **Money moments:** <paywall placement, upgrade triggers, checkout, failed payment, cancel, rating prompts, winback>
- **Acquisition coherence:** <the one story ad -> landing/listing -> onboarding tells>
-->

## Product mechanics

<!-- Two dimensions the practice-selection profile reads; record them once,
even when the answer is "none":
- **Personalization:** none | rule-based | inferred/model-driven — BP-143/BP-144 (what gets asked when, and how a wrong inference is corrected)
- **Engagement mechanics:** none | streaks/tiers | points/badges/leaderboards — BP-141/BP-142 (which traced job each mechanic reinforces, and the recovery path when progress is lost)
- **Accessibility regime:** none stated | EAA (EU) | ADA (US) | both — BP-138, with the owner
-->

## Design tooling

<!-- Visual mockups in Figma are optional (default on). Ask the user at the
start of design; record the choice here (see figma-integration). The Figma
file and design-system details live in docs/ux/screens.md (the UI map);
this section just records the on/off choice and the file location.
- **Figma:** enabled | disabled
- **Figma file:** <url — one project file, one page per feature/flow group>
-->

## User stories

<!-- ### ST-001: <short name>
- **Story:** As <persona>, I want <capability>, so that <benefit>.
- **Traces:** JTBD-01, JRN-01/#2
- **Acceptance criteria:**
  - Given <precondition>, when <action>, then <observable result>.
- **Priority:** must | should | could
- **Kill criteria:** <metric below threshold by date -> drop | iterate, or omit>
- **Status:** proposed
- **Product:** unobserved
-->