# Design record: <feature or screen set>

Skill: design-decision-method <version> · Date: <YYYY-MM-DD> · Visual system: <name and version> · Project guidelines: <name and version, or "none supplied">

## 1. Context

- Audience and roles:
- Experience purpose and primary outcomes:
- Primary tasks (frequency, urgency):
- Cost of error:
- Device, input, language, connectivity:
- Known facts:
- Assumptions (mark each):

## 2. Object map

Apply the gate in `SKILL.md`. Produce or reuse a verified map when meaningful relationships affect the navigation, routes, or screen structure being designed or changed. Treat the four conditions there as structural signals scoped to that change. Existing product complexity alone does not require a map for an unrelated copy or styling fix. Use the smallest sufficient map. Record `Map: produced / reused / skipped — <reason>`.

| Object | Relationships | Decision-relevant attributes | Actions |
|---|---|---|---|
| e.g. Appointment | belongs to Patient; with Clinician | date, status, location | book, move, cancel |

Routes and screens derived from the map:

- 

## 3. Decisions

| Decision | Frequency | Familiarity | Error cost | Device | Pattern chosen | Reason |
|---|---|---|---|---|---|---|

Adaptation lines (only where departing from a cited source rule):

- Source rule / this design instead / why:

Presentation direction (when purpose, hierarchy, composition, density, or responsive behaviour changes, including on an existing themed screen; brief and proportional; skip when those decisions are unchanged):

Visual roles and tokens, or exact verified inherited tokens/components. New focus, errors and disabled/read-only behaviour still need checks:

When adopting a component or pattern: exact source/library/version, maturity (upstream status or "not stated"), adoption reason, and any fallback or further validation needed:

When text limits apply: counting unit and locale, displayed limit and backend rule, supported languages/browser fallback, and boundary-test status:

## 4. Acceptance criteria

| Task, audience, device | Expected outcome | Check or metric | Target (proposed or evidence-based) | Method | Result (or "not tested") |
|---|---|---|---|---|---|

## 5. Validation status

- Evidence levels reached:
- Accessibility target, what was tested, what was not:
- Open questions and deferred items: