Design direction changed from Clinical Utilitarian to Clinical Luxury, updated all plans etc

Ralph/IMPLEMENTATION_PLAN.md

@@ -1,55 +1,63 @@
-# Implementation Plan — Design 7: The Clinical Record (v2)
+# Implementation Plan — The Clinical Record (v3)
 
 ## Project Overview
 
-Redesign of the Clinical Record PMR interface to achieve **absolute thematic fidelity** to real NHS clinical software (EMIS Web, SystmOne). The codebase has existing components from a prior iteration that are functionally complete but lack the visual density, authentic clinical system feel, and design quality described in the specification. This plan rebuilds each visual component to production-showcase quality.
+A premium portfolio CV presented as a clinical information system. The *structure* and *layout* come from GP software (EMIS Web, SystmOne) — patient banner, sidebar navigation, consultation journal, medications table, etc. — but the *execution* is **Clinical Luxury**: refined typography, layered shadows, generous spacing, premium fonts, atmospheric depth.
 
-**Core principle:** This is NOT a clinical "theme" loosely applied — it's a **faithful digital clinical information system**. Every element must look like it belongs in actual NHS software. Border-heavy, table-heavy, functional — zero decorative flourish.
+**This is NOT a faithful NHS clone.** It's a showcase portfolio that *evokes* clinical software while being distinctly beautiful.
 
-**Data files are correct and complete** (`src/data/*`). The existing type system (`src/types/pmr.ts`) is sound. The phase management in `App.tsx` works. This plan focuses on **rebuilding the visual layer** to match the specification.
+**What's already done:** Data files (`src/data/*`), type system (`src/types/pmr.ts`), phase management (`App.tsx`), boot sequence, ECG animation, and design system foundation (Tailwind tokens, fonts, CSS variables).
+
+**What this plan builds:** The visual layer from login screen through to the full PMR interface — every component rebuilt to Clinical Luxury quality with the new premium font, refined surfaces, and user-interactive login.
 
 ## Quality Checks
 
-Run ALL of these after each task. All must pass before committing.
+Run after every task. All must pass before committing.
 
-- `npm run typecheck`
-- `npm run lint`
-- `npm run build`
+```
+npm run typecheck
+npm run lint
+npm run build
+```
 
 ## Reference Files
 
-Each task below references a specific file in `Ralph/refs/` — read ONLY that file for the task context. Do NOT read goal.md directly (it's 1100+ lines and will overwhelm your context).
+Each task references files in `Ralph/refs/`. Read the referenced file(s) for full design specs, implementation patterns, and code snippets. The ref files ARE the spec — do not duplicate their content here.
+
+Always also read `Ralph/refs/ref-design-system.md` — it is the single source of truth for colors, typography, spacing, surfaces, and motion.
+
+Also read `CLAUDE.md` for font setup instructions (Elvaro Grotesque and Blumir candidates in `Fonts/` directory).
 
 ## Tasks
 
-- [x] **Task 1: Design system foundation and font setup.** Read `Ralph/refs/ref-design-system.md`. Audit and fix the Tailwind config (`tailwind.config.js`) and global CSS (`src/index.css`) to ensure ALL PMR color tokens, typography, and spacing match the design system spec exactly. Specific fixes needed: (a) Ensure Geist Mono font is loaded via Google Fonts or local import — currently the project uses Fira Code for monospace but the spec requires Geist Mono for coded entries, timestamps, and data values. (b) Verify all PMR color tokens exist in Tailwind config: main content `#F5F7FA`, cards `#FFFFFF`, sidebar `#1E293B`, patient banner `#334155`, NHS blue `#005EB8`, green `#22C55E`, amber `#F59E0B`, red `#EF4444`, text primary `#111827`, text secondary `#6B7280`. (c) Ensure border-radius defaults to 4px for cards/inputs (not 8px or 12px — clinical systems use minimal rounding). (d) Add a `.pmr-theme` class or CSS custom properties layer for PMR-specific tokens if not already present. (e) Verify Inter font is loaded and configured as the primary font family. Do NOT invoke /frontend-design for this task — it's pure configuration.
+- [x] **Task 1: Design system foundation.** Tailwind config, CSS variables, font loading. *(Completed — see progress.txt)*
 
-- [x] **Task 1b: Rebuild boot sequence and ECG animation.** Read `Ralph/refs/ref-boot-ecg.md` and `Ralph/refs/ref-design-system.md`. Also read `ECGCombined.tsx` in the project root for the Remotion reference implementation of the mask-based text reveal. This task covers the full pre-login animation flow: (a) **Refactor BootSequence.tsx** — replace hardcoded HTML strings with a clean config-driven structure. Each line type (header, field, separator, module, ready) maps to a React component. Keep the same visual output: green-on-black terminal, Fira Code font, 220ms staggered line reveals, `#00ff41` bright green / `#3a6b45` dim green / `#00e5ff` cyan labels. (b) **Cursor → dot transition** — the blinking green cursor at the end of boot must smoothly morph into the ECG's glowing trace dot. Capture the cursor's screen position and pass it to ECGAnimation as a `startPosition` prop. The cursor stops blinking, transitions from block to circular glow (~300ms), then begins moving rightward as the ECG trace dot. (c) **ECG start sync** — ECGAnimation must start its trace from the cursor position (not the far left edge). The first beat begins after a flat gap from the cursor position. Shift the world-space origin so the trace starts where the cursor was. (d) **Mask-based text reveal** — adopt ECGCombined.tsx's technique where pre-rendered stroke-only text is revealed by a wipe mask following the trace head (instead of the current alpha fade approach). Keep the current character spacing (`LETTER_W`, `LETTER_G`, `SPACE_W`) and heartbeat waveform. Add connector lines between letters at baseline. (e) **Keep**: heartbeat shape, beat timing (0.3→0.55→0.85→1.0 amplitude), canvas rendering, viewport scrolling, flatline draw, scanlines, vignette, background transition to `#1E293B`. (f) Respect `prefers-reduced-motion` — with reduced motion, skip animation and show static final frame or jump to login.
+- [x] **Task 1b: Boot sequence and ECG animation.** *(Completed and locked — do not modify)*
 
-- [x] **Task 2: Rebuild LoginScreen component.** Read `Ralph/refs/ref-transition-login.md` and `Ralph/refs/ref-design-system.md`. Rebuild `src/components/LoginScreen.tsx` to match the login sequence specification exactly: (a) Dark blue-gray `#1E293B` background. (b) White card: 320px wide, **12px border-radius** (exception to the 4px rule — login cards can be rounder), subtle shadow. (c) NHS-blue shield icon at top with "CareerRecord PMR" branding text. (d) Username field types `A.CHARLWOOD` at 30ms/char in **Geist Mono** font. (e) Password field fills 8 dots at 20ms/dot. (f) Blinking cursor (530ms interval) in active field. (g) "Log In" button: NHS blue `#005EB8`, full width, pressed state darkens to `#004494`. (h) After submit: card scales to 103% and fades out over 200ms. (i) Respect `prefers-reduced-motion`. The login must feel like actually logging into NHS software at 8am on a Monday.
+- [ ] **Task 2: Set up premium font and update Tailwind config.** Read `CLAUDE.md` (Typography section) and `Ralph/refs/ref-design-system.md`. Load both candidate fonts from `Fonts/` directory (Elvaro Grotesque WOFF2 files and Blumir variable font WOFF2). Add `@font-face` declarations in `src/index.css`. Update Tailwind config to add `font-ui` family pointing to the chosen font (start with Elvaro, can be swapped later). Replace `font-inter` references in Tailwind config with `font-ui`. Ensure Geist Mono remains the monospace font. Keep Fira Code for boot/ECG phases only.
 
-- [ ] **Task 3: Rebuild PatientBanner component.** Read `Ralph/refs/ref-banner-sidebar.md` and `Ralph/refs/ref-design-system.md`. Rebuild `src/components/PatientBanner.tsx` to match the specification exactly: (a) Full banner 80px: background `#334155`, bottom border `1px solid #475569`. Name in Inter 600 **20px** (not 18px), details in Inter 400 14px. Layout must match the ASCII art in the ref file — surname-first format "CHARLWOOD, Andrew (Mr)", DOB/NHS No/Address on second row, phone/email/buttons on third row. (b) Status: green dot + "Active" text. Badge: "Open to opportunities" as blue pill. (c) Action buttons: outlined rectangles with NHS blue text and 1px border, 4px radius. Hover fills with NHS blue bg + white text. (d) Condensed banner 48px: single line with name, NHS number, status, action buttons only. Triggers at 100px scroll via IntersectionObserver. Smooth 200ms height transition. (e) Mobile banner: minimal top bar `CHARLWOOD, A (Mr) | 2211810 | dot` with overflow "..." menu. NHS Number tooltip: "GPhC Registration Number".
+- [ ] **Task 3: Rebuild LoginScreen.** Read `Ralph/refs/ref-transition-login.md`. Key changes from prior version: (a) Typing speed is now **80ms/char** for username, **60ms/dot** for password — natural pace, not frantic. (b) After typing completes, the "Log In" button becomes **user-interactive** — the user clicks it to proceed. It is NOT auto-triggered. Button should have hover state, full opacity when ready, disabled/dimmed while typing. (c) Card shadow uses multi-layered shadow per design system. (d) Uses [UI font] for labels, Geist Mono for input fields. (e) `prefers-reduced-motion`: typing completes instantly, button is immediately interactive.
 
-- [ ] **Task 4: Rebuild ClinicalSidebar component.** Read `Ralph/refs/ref-banner-sidebar.md` and `Ralph/refs/ref-design-system.md`. Rebuild `src/components/ClinicalSidebar.tsx` to match the specification exactly: (a) 220px fixed width, `#1E293B` background, `1px solid #334155` right border. (b) Header: "CareerRecord PMR / v1.0.0" in Inter 500, 13px, white at 50% opacity. (c) Search input: "Search record..." placeholder, integrated in sidebar below header. (d) **Navigation labels use CV-friendly terms**: Summary, Experience, Skills, Achievements, Projects, Education, Contact (NOT clinical jargon like Consultations, Medications, etc.). Same Lucide icons as before. Items: 44px height, 16px left padding, icons 18px + labels Inter 500 14px. Exact states: default white/70%, hover white/100% + `rgba(255,255,255,0.08)` bg, active white/100% + 3px NHS blue left border + `rgba(255,255,255,0.12)` bg + Inter 600 bold. (e) Separator line between Summary and Experience. (f) Footer: "Session: A.CHARLWOOD / Logged in: [time]" in Inter 400, 11px, `#64748B`. Time updates on mount. (g) Tablet mode: 56px icon-only with tooltips. (h) URL hash routing (`#summary`, `#experience`, `#skills`, `#achievements`, `#projects`, `#education`, `#contact`). (i) Alt+1-7 keyboard shortcuts, arrow key navigation, "/" for search focus. (j) Update the ViewId type in `src/types/pmr.ts` if needed to match the new labels.
+- [ ] **Task 4: Rebuild PatientBanner.** Read `Ralph/refs/ref-banner-sidebar.md` (Patient Banner section). Full banner (80px) with surname-first format, demographic details, action buttons. Condensed banner (48px) via IntersectionObserver at 100px scroll. Mobile minimal banner with overflow menu. Uses [UI font] throughout. NHS Number tooltip: "GPhC Registration Number".
 
-- [ ] **Task 5: Rebuild PMRInterface layout and add Breadcrumb.** Read `Ralph/refs/ref-banner-sidebar.md` and `Ralph/refs/ref-design-system.md`. Rebuild `src/components/PMRInterface.tsx` to ensure correct layout composition: (a) Fixed sidebar (220px) + sticky patient banner + scrollable main content area with `#F5F7FA` background. (b) Main content padding: 24px. No max-width — content fills available space. (c) Create `src/components/Breadcrumb.tsx`: displays "Patient Record > [Current View]" at the top of the main content area (using CV-friendly view names: Experience, Skills, Achievements, etc.). When a consultation/skill/achievement is expanded, the breadcrumb deepens to show the item name. Styled in Inter 400, 13px, gray-400, with chevron separators. Clickable links navigate back. (d) Interface materialization animations: patient banner slides down (200ms ease-out), sidebar slides from left (250ms ease-out, 50ms delay), content fades in (300ms, 100ms delay after sidebar). (e) View switching must be INSTANT — no crossfade or slide between views. (f) Ensure mobile layout uses bottom nav bar (56px height with safe area padding). (g) Update the view switching logic to use the new CV-friendly ViewId values (summary, experience, skills, achievements, projects, education, contact).
+- [ ] **Task 5: Rebuild ClinicalSidebar.** Read `Ralph/refs/ref-banner-sidebar.md` (Left Sidebar + Navigation sections). CV-friendly labels: Summary, Experience, Skills, Achievements, Projects, Education, Contact. 220px fixed width. Header branding, search input, navigation items with exact states (default/hover/active), separator line, footer with session info. Tablet mode: 56px icon-only. Keyboard shortcuts: Alt+1-7, arrow keys, "/" for search. URL hash routing.
 
-- [ ] **Task 6: Rebuild SummaryView with Clinical Alert.** Read `Ralph/refs/ref-summary-alert.md` and `Ralph/refs/ref-design-system.md`. Rebuild `src/components/views/SummaryView.tsx` and the clinical alert: (a) Clinical Alert: amber `#FEF3C7` background, 4px left border `#F59E0B`, text `#92400E`. Slides down with **spring animation** (not ease-out — use Framer Motion `type: "spring"` with appropriate damping). Acknowledge button: amber outlined. On click: warning icon cross-fades to green checkmark (200ms), holds 200ms, then alert height collapses (200ms ease-out). (b) 2-column card grid on desktop, single column on mobile. Cards have: header bar with title in Inter 600, 14px, uppercase, on `#F9FAFB` background with `1px solid #E5E7EB` bottom border. Card body: 16px padding, `1px solid #E5E7EB` border, 4px radius. (c) Demographics card: two-column key-value layout. Labels right-aligned Inter 500 13px gray-500, values left-aligned Inter 400 14px gray-900. (d) Active Problems card: traffic light dots + problem text + date in Geist Mono 12px. (e) Quick Meds card: 4-column table with top 5 skills. "View Full List ->" link. (f) Last Consultation card: preview with "View Full Record ->" link. All navigation links must actually switch the sidebar view.
+- [ ] **Task 6: Rebuild PMRInterface layout + Breadcrumb.** Read `Ralph/refs/ref-banner-sidebar.md` (PMRInterface Layout + Breadcrumb sections). Fixed sidebar + sticky banner + scrollable content on `#F5F7FA`. Create `Breadcrumb.tsx`. Interface materialization animations (banner → sidebar → content stagger). View switching is INSTANT. Mobile: bottom nav bar. Update ViewId type if needed.
 
-- [ ] **Task 7: Rebuild ConsultationsView.** Read `Ralph/refs/ref-consultations.md` and `Ralph/refs/ref-design-system.md`. Rebuild `src/components/views/ConsultationsView.tsx`: (a) Collapsed entries: date in Geist Mono 13px gray-500, organization in Inter 400 13px NHS blue, role in Inter 600 15px gray-900, "Key:" prefix in Inter 500 gray-500 with single-line achievement. Chevron button right-aligned. (b) Status dot: green for current, gray for historical. (c) 3px left border color-coded by employer (NHS blue `#005EB8` or Tesco teal `#00897B`). (d) Expanded state: Duration line, then HISTORY / EXAMINATION / PLAN sections with headers in Inter 600, 12px, uppercase, letter-spacing 0.05em, gray-400. Plan items as bullet lists. (e) CODED ENTRIES section at bottom: Geist Mono 12px, gray-500, bracket codes. (f) Height-only expand animation, 200ms ease-out. NO opacity fade on content — content simply grows/shrinks. (g) Only one expanded at a time. (h) Implement the second clinical alert (Python switching algorithm alert) that appears on first navigation to Consultations view, dismissible with same Acknowledge pattern.
+- [ ] **Task 7: Rebuild SummaryView + Clinical Alert.** Read `Ralph/refs/ref-summary-alert.md`. Clinical Alert with spring animation entrance, acknowledge → checkmark → collapse sequence. Summary cards: Demographics (full-width key-value), Active Problems (traffic lights), Current Skills quick table, Last Consultation preview. 2-column grid desktop, single column mobile. Navigation links to other views.
 
-- [ ] **Task 8: Rebuild MedicationsView.** Read `Ralph/refs/ref-medications.md` and `Ralph/refs/ref-design-system.md`. Rebuild `src/components/views/MedicationsView.tsx`: (a) Three category tabs: "Active Medications" (technical), "Clinical Medications" (healthcare domain), "PRN (As Required)" (strategic/leadership). Tab styling: active tab has white bg + NHS blue bottom border. (b) Full table with proper `<table>` markup: Drug Name | Dose | Frequency | Start | Status. Table headers: Inter 600, 13px, uppercase, `#F9FAFB` bg. Row height: 40px. All borders: `1px solid #E5E7EB`. Alternating `#FFFFFF`/`#F9FAFB` row backgrounds. (c) Hover: `#EFF6FF` background only — no transform, no lift. (d) Sortable columns: click header to sort, arrow indicator in active column. (e) Status dots: 6px green circles + "Active" text. (f) Expandable prescribing history: Geist Mono 12px, year markers bold, descriptions regular. (g) Mobile: card layout (stacked fields per card, not table).
+- [ ] **Task 8: Rebuild ConsultationsView.** Read `Ralph/refs/ref-consultations.md`. Reverse-chronological journal. Collapsed entries with date, org, role, key achievement. Expanded: H/E/P structure with coded entries. Height-only expand animation (no opacity fade). One expanded at a time. 3px left border color-coded by employer. Second clinical alert on first visit.
 
-- [ ] **Task 9: Rebuild ProblemsView.** Read `Ralph/refs/ref-problems.md` and `Ralph/refs/ref-design-system.md`. Rebuild `src/components/views/ProblemsView.tsx`: (a) Two sections: "ACTIVE PROBLEMS" and "RESOLVED PROBLEMS" with section headers in clinical style. (b) Table columns — Active: Status | Code | Problem | Since. Resolved: Status | Code | Problem | Resolved | Outcome. (c) Traffic light dots: 8px circles (green=resolved, amber=in-progress). Always paired with text labels — never the sole indicator. (d) Code column in Geist Mono. (e) Expandable rows showing full narrative + linked consultation buttons that navigate to Consultations view. (f) Row hover: `#EFF6FF`. (g) Mobile: card layout.
+- [ ] **Task 9: Rebuild MedicationsView.** Read `Ralph/refs/ref-medications.md`. Three category tabs (Active/Clinical/PRN). Semantic `<table>` with sortable columns. Expandable prescribing history in Geist Mono. Status dots with text labels. Mobile: card layout.
 
-- [ ] **Task 10: Rebuild InvestigationsView and DocumentsView.** Read `Ralph/refs/ref-investigations-documents.md` and `Ralph/refs/ref-design-system.md`. Rebuild both views: (a) InvestigationsView: table with Test Name | Requested | Status | Result. Status badges: green "Complete", amber "Ongoing", pulsing green "Live". Expanded view uses tree-indented monospace structure with box-drawing characters (pipe symbols). "View Results" NHS blue button for PharMetrics only. (b) DocumentsView: table with Type icon | Document | Date | Source. Lucide icons per document type (FileText, Award, GraduationCap, FlaskConical). Expanded preview uses same tree-indented structure. (c) Both views share the expandable-row pattern — maintain visual consistency. (d) Mobile: card layouts for both.
+- [ ] **Task 10: Rebuild ProblemsView.** Read `Ralph/refs/ref-problems.md`. Two sections: Active Problems and Resolved Problems. Traffic light dots (8px, always with text labels). Code column in Geist Mono. Expandable rows with narrative + linked consultation navigation. Mobile: card layout.
 
-- [ ] **Task 11: Rebuild ReferralsView.** Read `Ralph/refs/ref-referrals.md` and `Ralph/refs/ref-design-system.md`. Rebuild `src/components/views/ReferralsView.tsx`: (a) Form header: "New Referral" with pre-filled patient info (non-editable). (b) Priority radio buttons: Urgent (red), Routine (blue, default), Two-Week Wait (amber). Each with tongue-in-cheek tooltips. (c) Form fields: standard clinical inputs with `1px solid #D1D5DB` border, 4px radius, `8px 12px` padding. Labels in Inter 500, 13px, gray-600 above inputs. Focus: NHS blue border + `box-shadow: 0 0 0 3px rgba(0,94,184,0.15)`. (d) Contact Method radio group. (e) Submit: "Send Referral" NHS blue button. Loading spinner state. Success state with reference number (REF-YYYY-MMDD-NNN format), checkmark, "24-48 hours" response time. (f) Direct Contact table below form: Email, Phone, LinkedIn, Location with action buttons.
+- [ ] **Task 11: Rebuild InvestigationsView + DocumentsView.** Read `Ralph/refs/ref-investigations-documents.md`. Both views share the expandable-row pattern with tree-indented monospace content (box-drawing characters). Investigations: status badges (Complete/Ongoing/Live). Documents: type icons per document category. "View Results" button for PharMetrics only. Mobile: card layouts.
 
-- [ ] **Task 12: Implement fuzzy search with fuse.js.** Read `Ralph/refs/ref-interactions.md`. Install fuse.js (`npm install fuse.js`). Rebuild the search functionality in the sidebar: (a) Build a search index on mount from ALL content: consultation titles/descriptions, medication names, problem descriptions, investigation names, document titles. (b) Search options: `{ keys: ['title', 'description', 'name'], threshold: 0.3, includeScore: true }`. (c) Results dropdown grouped by section (Consultations, Medications, Problems, etc.) with section icon, matching text, and relevance indicator. (d) Clicking a result navigates to the section AND expands/highlights the matching item. (e) Dropdown styled: white bg, `1px solid #E5E7EB`, 4px radius, shadow. Items in Inter 400 14px, 36px height. (f) Escape closes dropdown. (g) Mobile: search bar at top of each view instead of sidebar.
+- [ ] **Task 12: Rebuild ReferralsView (Contact).** Read `Ralph/refs/ref-referrals.md`. Clinical referral form with priority radio buttons (Urgent/Routine/Two-Week Wait with tongue-in-cheek tooltips). Form validation, reference number generation, success state. Direct contact table below form.
 
-- [ ] **Task 13: Implement context menus.** Read `Ralph/refs/ref-interactions.md`. Add right-click/long-press context menus: (a) On consultation entries: "Expand", "Copy to clipboard", "View coded entries". (b) On medication rows: "View prescribing history", "Copy to clipboard". (c) On problem entries: "View linked consultations", "Copy to clipboard". (d) Styled: white bg, `1px solid #E5E7EB` border, 4px radius, `box-shadow: 0 4px 12px rgba(0,0,0,0.1)`. Items: Inter 400, 14px, 36px row height. (e) Escape closes menu. Focus returns to trigger element on close. (f) Use Headless UI or a custom implementation — accessible with keyboard navigation.
+- [ ] **Task 13: Fuzzy search with fuse.js.** Read `Ralph/refs/ref-interactions.md` (Search section). Install fuse.js. Build search index from all content. Results dropdown grouped by section. Clicking a result navigates to section + expands matching item. Mobile: search at top of each view.
 
-- [ ] **Task 14: Responsive design audit and fix.** Read `Ralph/refs/ref-interactions.md`. Systematically test and fix all three breakpoints: (a) Desktop (>1024px): full sidebar 220px, full patient banner 80px condensing to 48px, full tables. (b) Tablet (768-1024px): sidebar collapses to 56px icon-only with tooltips on hover/tap. Patient banner always condensed. Tables may horizontally scroll. Context menus via long-press. (c) Mobile (<768px): bottom nav bar with 7 icon buttons (56px height + safe area). Minimal top bar. ALL tables convert to card layout (stacked fields). Search bar at top of views. Back arrow to Summary. Touch targets minimum 48px. (d) Run `npm run build` and verify no layout breaks.
+- [ ] **Task 14: Responsive design audit.** Read `Ralph/refs/ref-interactions.md` (Responsive Strategy section). Test all three breakpoints: Desktop (>1024px), Tablet (768-1024px), Mobile (<768px). Tables → card layouts on mobile. Bottom nav bar. Touch targets ≥48px.
 
-- [ ] **Task 15: Accessibility audit and final polish.** Read `Ralph/refs/ref-interactions.md`. Audit and fix accessibility: (a) Semantic HTML: sidebar `<nav>` with `aria-label`, main `<main>`, banner `<header>`, tables with `scope="col"`. (b) ARIA: `aria-current="page"` on active sidebar item, `aria-expanded` on expandable items, `role="alert"` on clinical alerts. (c) Focus management: after login focus to sidebar, after view switch focus to first heading, after expand focus to section heading, after alert dismiss focus to main content. (d) Keyboard: Tab order, roving tabindex in sidebar, Escape closes everything. (e) Screen reader: announce view changes, table headers, alert text. (f) `prefers-reduced-motion`: login instant, alert no slide, expand/collapse instant, banner condensation instant. (g) Color contrast: verify all text meets WCAG 2.1 AA. Traffic lights always have text labels. (h) Final visual polish pass: ensure consistent spacing, borders, fonts across all views.
+- [ ] **Task 15: Accessibility audit + final polish.** Read `Ralph/refs/ref-interactions.md` (Accessibility section). Semantic HTML, ARIA attributes, focus management, keyboard navigation, screen reader announcements, `prefers-reduced-motion` support, WCAG 2.1 AA contrast. Final visual consistency pass.

Ralph/guardrails.md

@@ -2,100 +2,108 @@
 
 Hard rules that MUST be followed in every iteration. Violating these will produce incorrect output.
 
+## Design Direction
+
+### When: Making ANY aesthetic decision
+**Rule:** The direction is **Clinical Luxury** — the *structure* of clinical software (tables, status dots, coded entries, patient banner, sidebar) with *premium execution* (refined shadows, generous spacing, premium typography, atmospheric depth). This is NOT a faithful NHS clone.
+**Why:** The previous "clinical utilitarian" direction produced generic, flat output. The new direction keeps the clinical metaphor but makes it beautiful.
+
 ## Design System Guardrails
 
 ### When: Writing ANY visual component
-**Rule:** Light-mode only. Do NOT add dark mode classes, `dark:` prefixes, or theme toggles. Clinical record systems operate exclusively in light mode.
-**Why:** Dark mode breaks the clinical system metaphor. NHS clinical software is always light-mode due to high ambient lighting in consulting rooms.
+**Rule:** Light-mode only. Do NOT add dark mode classes, `dark:` prefixes, or theme toggles.
+**Why:** The design direction is light-mode only.
 
 ### When: Setting border-radius on cards, inputs, or table elements
-**Rule:** Use 4px border-radius (`rounded` in Tailwind, which is 4px). Do NOT use `rounded-lg` (8px), `rounded-xl` (12px), or `rounded-2xl` (16px). The only exception is the LoginScreen card which uses 12px.
-**Why:** Clinical systems use minimal rounding. Larger radii look like consumer apps, not NHS software.
+**Rule:** Use 4px border-radius (`rounded` in Tailwind). The only exception is the LoginScreen card which uses 12px.
+**Why:** Clinical systems use minimal rounding. This precision is part of the Clinical Luxury feel.
 
 ### When: Using monospace/code font
-**Rule:** Use Geist Mono (font-family: 'Geist Mono', monospace), NOT Fira Code, for coded entries, timestamps, clinical codes, and data values.
-**Why:** The spec requires Geist Mono. Fira Code was used in the ECG/boot phase but is wrong for the PMR interface.
+**Rule:** Use Geist Mono (`font-family: 'Geist Mono', monospace`), NOT Fira Code, for coded entries, timestamps, clinical codes, and data values in the PMR interface. Fira Code is used in boot/ECG phases only.
+**Why:** Geist Mono is the specified monospace font for the PMR interface.
+
+### When: Choosing the UI text font
+**Rule:** Use [UI font] — either Elvaro Grotesque or Blumir (see CLAUDE.md for setup). Do NOT use Inter, Roboto, or system defaults for the PMR interface.
+**Why:** Premium typography is the primary vehicle for the luxury feel. Generic fonts undermine the entire direction.
 
 ### When: Adding shadows to cards or panels
-**Rule:** No shadows, or at most `0 1px 2px rgba(0,0,0,0.03)`. Do NOT use prominent shadows like `shadow-md` or `shadow-lg`.
-**Why:** Clinical systems structure with borders, not shadows. Prominent shadows look like marketing sites.
+**Rule:** Use multi-layered shadows per the design system: `0 1px 2px rgba(0,0,0,0.04), 0 4px 12px rgba(0,0,0,0.03)`. Cards should feel like they float slightly above the content surface. Do NOT use flat, borderless cards or overly dramatic Material Design shadows.
+**Why:** Layered shadows create the subtle depth that distinguishes Clinical Luxury from both flat clinical software and generic SaaS.
 
 ### When: Styling borders
-**Rule:** All card and table borders must be `1px solid #E5E7EB` (gray-200). Use `border-gray-200` in Tailwind.
-**Why:** This is the universal border color in NHS clinical software.
+**Rule:** All card and table borders must be `1px solid #E5E7EB` (gray-200). Keep borders on tables — they're authentically clinical.
+**Why:** Borders provide clinical texture. Combined with shadows, they create the luxury-clinical contrast.
 
 ## Sidebar Label Convention
 
 ### When: Building or modifying sidebar navigation labels
-**Rule:** Sidebar labels MUST use CV-friendly terms: Summary, Experience, Skills, Achievements, Projects, Education, Contact. Do NOT use clinical jargon (Consultations, Medications, Problems, Investigations, Documents, Referrals) as sidebar labels. The clinical metaphor lives in the LAYOUT of each view, not the navigation labels.
-**Why:** Non-clinical visitors should immediately understand what each section contains. The clinical system aesthetic comes from the visual presentation (consultation journal format, medications table format, etc.), not from the nav labels.
+**Rule:** Labels MUST be CV-friendly: Summary, Experience, Skills, Achievements, Projects, Education, Contact. Do NOT use clinical jargon (Consultations, Medications, etc.) as labels. The clinical metaphor lives in the LAYOUT of each view, not the labels.
+**Why:** Non-clinical visitors should immediately understand what each section contains.
 
 ## Navigation Guardrails
 
 ### When: Switching between sidebar views
-**Rule:** View switching must be INSTANT. No crossfade, no slide animation, no opacity transition between views. The main content area simply replaces its content immediately.
-**Why:** Clinical systems use instant tab switching. Any animation makes it feel like a website, not clinical software.
+**Rule:** View switching must be INSTANT. No crossfade, no slide animation, no opacity transition.
+**Why:** Clinical systems use instant tab switching. This preserves the "application" feel.
 
 ### When: Building navigation
-**Rule:** URL hash routing is required. Each view must update `window.location.hash` and the app must read the hash on load to navigate to the correct view.
-**Why:** Direct linking to specific views is required for shareability.
+**Rule:** URL hash routing is required. Each view updates `window.location.hash`.
+**Why:** Direct linking to specific views is required.
+
+## Login Screen Guardrails
+
+### When: Building the login typing animation
+**Rule:** Username types at 80ms/char. Password dots at 60ms/dot. After typing completes, the "Log In" button becomes interactive — the user clicks it. It is NOT auto-triggered.
+**Why:** The natural pace lets users absorb what's happening. The interactive button creates a moment of user agency.
 
 ## Component Guardrails
 
-### When: Expanding/collapsing consultation entries
-**Rule:** Use height animation ONLY (200ms, ease-out). Do NOT fade opacity on the content. Content simply grows/shrinks in height.
-**Why:** The spec explicitly states "No opacity fade — the content simply grows/shrinks."
+### When: Expanding/collapsing entries
+**Rule:** Height animation ONLY (200ms, ease-out). Do NOT fade opacity on content.
+**Why:** The spec explicitly states content grows/shrinks without opacity change.
 
 ### When: Displaying traffic light status indicators
-**Rule:** Traffic lights (colored dots) must ALWAYS be accompanied by text labels (Active, Resolved, In Progress, etc.). Dots are never the sole indicator of state.
-**Why:** WCAG accessibility — color cannot be the only means of communicating information.
-
-### When: Writing consultation entries
-**Rule:** Use History / Examination / Plan section headers (uppercase, Inter 600, 12px, letter-spacing 0.05em, gray-400). Include CODED ENTRIES at the bottom of each expanded consultation in [XXX000] format.
-**Why:** This is the core metaphor — SOAP notes format mapped to career content.
+**Rule:** Colored dots must ALWAYS have text labels. Never use color as the sole indicator.
+**Why:** WCAG — color cannot be the only means of communicating information.
 
 ### When: Rendering the clinical alert
-**Rule:** Use Framer Motion `type: "spring"` animation for the alert entrance (not ease-out). The alert uses amber colors: bg `#FEF3C7`, left border `#F59E0B`, text `#92400E`.
-**Why:** The spec specifies spring animation with slight overshoot. Alerts demand attention.
+**Rule:** Use Framer Motion `type: "spring"` animation for entrance (not ease-out). Amber colors: bg `#FEF3C7`, left border `#F59E0B`, text `#92400E`.
+**Why:** Spring animation with slight overshoot makes alerts feel alive and demanding.
 
 ### When: Writing table markup
-**Rule:** Use semantic `<table>`, `<thead>`, `<th>`, `<tbody>`, `<tr>`, `<td>` elements. Column headers must include `scope="col"`. Do NOT use div-based table layouts.
-**Why:** Screen readers navigate tables using native table semantics. Div tables are inaccessible.
+**Rule:** Use semantic `<table>`, `<thead>`, `<th scope="col">`, `<tbody>`, `<tr>`, `<td>`. No div-based tables.
+**Why:** Screen readers require native table semantics.
 
 ## Data Guardrails
 
-### When: Displaying CV content (dates, numbers, roles, achievements)
-**Rule:** All data must come from `src/data/*.ts` files. Do NOT hardcode CV content directly in components. Do NOT change any numbers or dates — they are sourced from the verified CV.
-**Why:** Data accuracy is critical. The data layer has been validated against CV_v4.md.
-
-### When: Modifying data files
-**Rule:** Do NOT modify data files in `src/data/` unless the task explicitly requires it. The data is correct and complete.
-**Why:** Data was verified in a prior iteration. Unnecessary changes risk introducing inaccuracies.
+### When: Displaying CV content
+**Rule:** All data must come from `src/data/*.ts` files. Do NOT hardcode content in components or change any numbers/dates.
+**Why:** Data has been validated against CV_v4.md.
 
 ## Visual Review Guardrails
 
-### When: Completing any visual component task (Tasks 1b-11)
-**Rule:** After quality checks pass, you MUST open the dev server (`http://localhost:5173`) in the browser using Claude in Chrome tools (`tabs_context_mcp`, `navigate`, `computer` with `action: "screenshot"`), take a screenshot of the relevant view, and compare against the reference file spec. Fix any visual discrepancies before committing. If browser tools are unavailable (e.g. Chrome not connected), document this in progress.txt and proceed — do NOT block the iteration.
-**Why:** Code review alone cannot catch visual issues. The previous iteration loop produced functionally correct but visually generic output because no one verified the rendered result.
+### When: Completing any visual task
+**Rule:** After quality checks, open `http://localhost:5173` via Claude in Chrome tools, take a screenshot, and compare against the ref file spec. Fix visual discrepancies. If browser tools are unavailable, note in progress.txt and proceed.
+**Why:** Code review alone cannot catch visual issues.
 
-### When: Browser tools fail or Chrome is not connected
-**Rule:** If `tabs_context_mcp` or other browser tools fail, skip the visual review step, note it in progress.txt, and continue. Do NOT retry more than twice or spend time debugging browser connectivity.
-**Why:** Visual review is valuable but not blocking. The loop must keep making progress.
+### When: Browser tools fail
+**Rule:** Skip visual review, note it in progress.txt, continue. Do NOT retry more than twice.
+**Why:** Visual review is valuable but not blocking.
 
 ## Technical Guardrails
 
 ### When: Writing TypeScript
-**Rule:** No `any` types. All props must have typed interfaces. All data must use the types from `src/types/pmr.ts`.
-**Why:** Strict typing prevents runtime errors and maintains code quality.
+**Rule:** No `any` types. All props must have typed interfaces.
+**Why:** Strict typing prevents runtime errors.
 
 ### When: Adding animations
-**Rule:** All animations must respect `prefers-reduced-motion`. With reduced motion: login typing completes instantly, alerts appear without slide, expand/collapse is instant, banner condensation is instant.
-**Why:** Accessibility requirement. Users who've opted out of motion must still have a functional experience.
+**Rule:** All animations must respect `prefers-reduced-motion`. With reduced motion: all animations skip to final state instantly.
+**Why:** Accessibility requirement.
 
-### When: Building visual components (Tasks 1b-11)
-**Rule:** Each reference file in `Ralph/refs/` contains a "Design Guidance (from /frontend-design)" section with pre-generated design direction and code patterns. Read this section BEFORE writing code. Do NOT invoke the `/frontend-design` skill at runtime — the guidance is already embedded in the ref files. Follow the aesthetic direction and code patterns provided.
-**Why:** The design guidance was pre-generated to avoid context overflow. Previous iterations stalled because the skill output consumed the entire context window, leaving no room to write files.
+### When: Building visual components
+**Rule:** Each ref file in `Ralph/refs/` contains a "Design Guidance" section with design direction and code patterns. Read it BEFORE writing code. Do NOT invoke `/frontend-design` at runtime.
+**Why:** Design guidance is pre-baked to avoid context overflow.
 
 ### When: Running quality checks
 **Rule:** Run `npm run typecheck`, `npm run lint`, and `npm run build` after EVERY task. Fix all errors before committing.
-**Why:** Build failures compound across iterations. Fix them immediately.
+**Why:** Build failures compound across iterations.

Ralph/progress.txt

@@ -24,11 +24,12 @@
 ### Design System Requirements (from ref-design-system.md)
 - Light-mode ONLY — no dark mode
 - NHS blue: #005EB8 (primary interactive)
-- Border radius: 4px for cards/inputs (clinical systems use minimal rounding)
-- Borders dominate — 1px solid #E5E7EB everywhere
-- Table row height: 40px, card padding: 16px, main content padding: 24px
-- Fonts: Inter (general text), Geist Mono (coded entries, timestamps, data values)
-- Base spacing unit: 4px — clinical density, not marketing site spacing
+- Border radius: 4px for cards/inputs
+- Borders: 1px solid #E5E7EB on tables and cards, combined with multi-layered shadows for depth
+- Card shadows: 0 1px 2px rgba(0,0,0,0.04), 0 4px 12px rgba(0,0,0,0.03)
+- Table row height: 40px, card padding: 16-24px, main content padding: 24px
+- Fonts: [UI font] (Elvaro Grotesque or Blumir from Fonts/ dir), Geist Mono (coded entries, timestamps, data values)
+- Base spacing unit: 4px — generous but structured, more whitespace than real clinical systems
 
 ### Known Dependencies
 - React 18.3.1, TypeScript, Vite
@@ -51,10 +52,13 @@
 - If browser tools fail, skip visual review and note in iteration log — don't block progress
 
 ### Critical Styling Notes
-- Geist Mono font must be loaded (NOT Fira Code) for coded entries and timestamps
-- Patient banner name must be 20px Inter 600 (not 18px)
-- Clinical alert must use spring animation (Framer Motion type: "spring"), not ease-out
-- View switching must be INSTANT — no crossfade, no slide between views
+- Design direction is **Clinical Luxury** — clinical structure, premium execution
+- Premium UI font loaded from Fonts/ directory (Elvaro Grotesque or Blumir, NOT Inter/Roboto)
+- Geist Mono for coded entries and timestamps (NOT Fira Code)
+- Multi-layered shadows on cards — NOT flat/borderless
+- Clinical alert uses spring animation (Framer Motion type: "spring"), not ease-out
+- View switching INSTANT — no crossfade, no slide between views
+- Login typing: 80ms/char username, 60ms/dot password. Button is USER-INTERACTIVE (not auto-triggered)
 - Consultation expand/collapse: height animation ONLY, no opacity fade on content
 
 ## Iteration Log
@@ -144,5 +148,27 @@ Do NOT invoke the `/frontend-design` skill at runtime — it was pre-run and the
 - Letter spacing: LETTER_W 72px, LETTER_G 10px, SPACE_W 30px (matches original, tighter than ECGCombined)
 - Morph animation uses Framer Motion scaleX/width/opacity for smooth cursor-to-dot transition
 
-**Next task:** Task 2 — Rebuild LoginScreen component
+**Next task:** Task 2 — Set up premium font
+
+## Manual Intervention — 2026-02-12
+### Reason: Design direction changed from "Clinical Utilitarian" to "Clinical Luxury"
+### Changes made:
+- Rewrote IMPLEMENTATION_PLAN.md — leaner format, tasks point to ref files for detail
+- Rewrote guardrails.md — updated shadow rules, font rules, login pacing, luxury direction
+- Updated all Ralph/refs/*.md files to align with Clinical Luxury direction
+- Updated CLAUDE.md with new login typing spec (80ms/char, user-interactive button)
+- Updated ref-design-system.md login typing speed
+### Tasks reset: Task 2 (LoginScreen — needs new typing speed + interactive button + premium font)
+### Tasks added: New Task 2 (font setup) inserted before LoginScreen rebuild (now Task 3)
+### Context for next iteration:
+- The design direction is "Clinical Luxury" — clinical STRUCTURE, premium EXECUTION
+- All ref files now say "Clinical Luxury" not "Clinical Utilitarian" or "faithful reproduction"
+- Cards get multi-layered shadows (not flat/borderless)
+- Premium font from Fonts/ directory replaces Inter (see CLAUDE.md Typography section)
+- Login screen typing is slower (80ms/char, 60ms/dot) and the button is USER-CLICKED
+- Sidebar labels are CV-friendly (Experience, Skills, etc.) — clinical metaphor is in the LAYOUT
+### New guardrails added:
+- Shadow guardrail updated: multi-layered shadows required (was: "no shadows")
+- Font guardrail added: use [UI font] from Fonts/, not Inter/Roboto
+- Login guardrail added: 80ms/char typing, user-interactive button
 

Ralph/refs/ref-banner-sidebar.md

@@ -76,15 +76,15 @@ The sidebar replicates the dark navigation panel found in EMIS Web and similar c
 
 ### Styling
 
-- Each item: 44px height, 16px left padding, icon (18px, `lucide-react`) + label in Inter 500, 14px
+- Each item: 44px height, 16px left padding, icon (18px, `lucide-react`) + label in [UI font] 500, 14px
 - Default state: white text at 70% opacity, transparent background
 - Hover state: white text at 100% opacity, background `rgba(255,255,255,0.08)`
-- Active state: white text at 100%, NHS blue left border (3px), background `rgba(255,255,255,0.12)`, label in Inter 600
+- Active state: white text at 100%, NHS blue left border (3px), background `rgba(255,255,255,0.12)`, label in [UI font] 600
 - A thin horizontal separator line (`1px solid rgba(255,255,255,0.1)`) appears between "Summary" and "Consultations" (separating the overview from the detail views)
 
 ### Sidebar Footer
 
-At the bottom of the sidebar, in small text (Inter 400, 11px, `#64748B`):
+At the bottom of the sidebar, in small text ([UI font] 400, 11px, `#64748B`):
 ```
 Session: A.CHARLWOOD
 Logged in: [current time]
@@ -98,7 +98,7 @@ At the top, above the navigation items, a small logo or system name:
 CareerRecord PMR
 v1.0.0
 ```
-In Inter 500, 13px, white at 50% opacity. Styled like the "EMIS Web" branding that appears in the top-left of the real system.
+In [UI font] 500, 13px, white at 50% opacity. Styled like clinical system branding that appears in the top-left of the navigation.
 
 ---
 
@@ -132,7 +132,7 @@ A breadcrumb appears at the top of the main content area:
 Patient Record > Consultations > Interim Head, Population Health
 ```
 
-The breadcrumb updates as the user navigates deeper (e.g., expanding a consultation). Clicking "Patient Record" returns to Summary. Clicking "Consultations" collapses any expanded entries and shows the full journal list. The breadcrumb is styled in Inter 400, 13px, gray-400, with chevron separators.
+The breadcrumb updates as the user navigates deeper (e.g., expanding a consultation). Clicking "Patient Record" returns to Summary. Clicking "Consultations" collapses any expanded entries and shows the full journal list. The breadcrumb is styled in [UI font] 400, 13px, gray-400, with chevron separators.
 
 ### Secondary Navigation: Within-View Interactions
 
@@ -146,18 +146,18 @@ The breadcrumb updates as the user navigates deeper (e.g., expanding a consultat
 
 ---
 
-## Design Guidance (from /frontend-design)
+## Design Guidance
 
 ### Aesthetic Direction
 
-**Clinical Institutional Precision** — The NHS Patient Administration System (PAS) header bar, faithfully reproduced as personal branding. This is not a "medical theme" website. It is a clinical system UI that happens to contain career data instead of patient data. The fidelity to real NHS IT systems (EMIS Web, SystmOne, Lorenzo) is the entire point.
+**Clinical Luxury** — The patient banner and sidebar draw their *structure* from NHS clinical systems (PAS headers, EMIS Web navigation), but the *execution* is premium — refined typography, layered shadows, considered spacing. The clinical metaphor lives in the layout and conventions (surname-first, pipe separators, status dots); the luxury lives in the finish.
 
-- **Tone**: Utilitarian, institutional, information-dense. No decoration. No gradients. No shadows. The beauty is in the data density, the pipe separators, the monospaced identifiers, the surname-first convention, the green status dot.
+- **Tone**: Precise, information-dense, and refined. Generous whitespace, layered shadows, and premium typography elevate what would otherwise be institutional UI. The clinical conventions (data density, pipe separators, monospaced identifiers, surname-first, green status dot) provide authentic texture.
 - **Typography Discipline**:
-  - Inter at 600 weight for the patient name — the anchor element
+  - [UI font] at 600 weight for the patient name — the anchor element
   - Geist Mono for structured identifiers (NHS Number, DOB) — monospaced data feels like it came from a database
-  - Inter at normal weight for demographic text
-  - The pipe character `|` as a data separator is a deliberate NHS PAS convention
+  - [UI font] at normal weight for demographic text
+  - The pipe character `|` as a data separator is a deliberate clinical convention
 
 ### Design System Tokens
 
@@ -170,7 +170,7 @@ The breadcrumb updates as the user navigates deeper (e.g., expanding a consultat
 | Border | `#E5E7EB` | 1px solid borders |
 | Border Radius | `4px` | All UI elements |
 | Green Status | `#22C55E` | Active status dot |
-| Font Text | `Inter` | All text content |
+| Font Text | [UI font] | All text content (Elvaro or Blumir — see CLAUDE.md) |
 | Font Data | `Geist Mono` | Monospaced identifiers |
 
 ### Key Design Decisions
@@ -197,7 +197,7 @@ The breadcrumb updates as the user navigates deeper (e.g., expanding a consultat
 5. **Navigation Item States**:
    - Default: white text at 70% opacity, transparent background
    - Hover: white text at 100%, background `rgba(255,255,255,0.08)`
-   - Active: white text at 100%, 3px NHS blue left border, background `rgba(255,255,255,0.12)`, Inter 600 weight
+   - Active: white text at 100%, 3px NHS blue left border, background `rgba(255,255,255,0.12)`, [UI font] 600 weight
 
 6. **Interface Materialization Animations** (PMRInterface):
    - Patient banner slides down (200ms ease-out)
@@ -281,7 +281,7 @@ const navItems: NavItem[] = [
 <button
   className={`
     w-full h-[44px] px-4 flex items-center gap-3
-    font-inter text-[14px] font-medium
+    font-ui text-[14px] font-medium
     transition-all duration-150
     ${isActive 
       ? 'text-white bg-white/[0.12] border-l-[3px] border-pmr-nhsblue font-semibold' 
@@ -485,7 +485,7 @@ const viewLabels: Record<ViewId, string> = {
   referrals: 'Contact'
 }
 
-// Styling: Inter 400, 13px, gray-400
+// Styling: [UI font] 400, 13px, gray-400
 // Chevron separators using Lucide ChevronRight
 // Clickable links navigate back
 ```

Ralph/refs/ref-consultations.md

@@ -24,9 +24,9 @@ Entries are stacked vertically, most recent at top. Each entry has a collapsed s
 ```
 
 - Date in Geist Mono, 13px, gray-500 (left-aligned)
-- Organization in Inter 400, 13px, NHS blue
-- Role title in Inter 600, 15px, gray-900
-- Key coded entry: a single-line summary of the most notable achievement, prefixed with "Key:" in Inter 500, gray-500
+- Organization in [UI font] 400, 13px, NHS blue
+- Role title in [UI font] 600, 15px, gray-900
+- Key coded entry: a single-line summary of the most notable achievement, prefixed with "Key:" in [UI font] 500, gray-500
 - Expand chevron button (right-aligned)
 - Status dot: green for current roles, gray for historical
 
@@ -78,7 +78,7 @@ This is a direct mapping from the clinical consultation format (SOAP notes) to c
 | **Examination** | Analysis / Findings | What Andy discovered, built, or analyzed — the technical and analytical work |
 | **Plan** | Outcomes / Delivery | What was achieved, what impact was measured, what's ongoing |
 
-Section headers ("HISTORY", "EXAMINATION", "PLAN") are styled in Inter 600, 12px, uppercase, letter-spacing 0.05em, gray-400 — exactly like the section dividers in a clinical consultation record.
+Section headers ("HISTORY", "EXAMINATION", "PLAN") are styled in [UI font] 600, 12px, uppercase, letter-spacing 0.05em, gray-400 — styled like clinical consultation record section dividers.
 
 ## Coded Entries
 
@@ -110,15 +110,13 @@ This visual grouping helps the user quickly scan which organization each entry b
 
 ---
 
-## Design Guidance (from /frontend-design)
+## Design Guidance
 
 ### Aesthetic Direction
 
-**Utilitarian clinical information system.** Zero decorative flourish. Border-heavy, table-heavy, functional. Light-mode only. The design language of EMIS Web and SystmOne—systems that every NHS pharmacist interacts with daily.
+**Clinical Luxury.** The structure and conventions of a clinical consultation journal — reverse-chronological entries, H/E/P format, coded entries, traffic-light status indicators — executed with premium refinement. Refined shadows, generous spacing, considered typography. Light-mode only.
 
-This is a **faithful digital clinical information system**—structured, database-driven, tabular, with the distinctive UI patterns of actual NHS clinical software: patient banner, tabbed clinical views, consultation history as a reverse-chronological journal, coded entries with SNOMED-style references, traffic-light status indicators, and action buttons styled as clinical system controls.
-
-**What makes this unforgettable:** The History / Examination / Plan structure maps perfectly to Context / Analysis / Outcome. A clinician seeing this will immediately recognize the consultation journal format. A recruiter gets highly structured, scannable career data. The accordion behavior, coded entries, and status indicators all draw from real clinical software patterns.
+**What makes this unforgettable:** The History / Examination / Plan structure maps perfectly to Context / Analysis / Outcome. A clinician seeing this will immediately recognize the consultation journal format. A recruiter gets highly structured, scannable career data. The accordion behavior, coded entries, and status indicators draw from clinical software patterns — but the execution feels polished and premium, not institutional.
 
 ### Key Design Decisions
 
@@ -127,7 +125,7 @@ This is a **faithful digital clinical information system**—structured, databas
      - **History** → Context / Background (why the role existed, reporting lines)
      - **Examination** → Analysis / Findings (what was discovered, built, analyzed)
      - **Plan** → Outcomes / Delivery (what was achieved, impact measured)
-   - Section headers styled as clinical system dividers: Inter 600, 12px, uppercase, letter-spacing 0.05em, gray-400
+   - Section headers styled as clinical system dividers: [UI font] 600, 12px, uppercase, letter-spacing 0.05em, gray-400
 
 2. **Height-Only Expand Animation (200ms)**
    - No opacity fade on content—content simply grows/shrinks
@@ -140,7 +138,7 @@ This is a **faithful digital clinical information system**—structured, databas
    - Tesco PLC: Teal (`#00897B`)
 
 4. **Typography System**
-   - Inter for text content
+   - [UI font] for text content (Elvaro or Blumir — see CLAUDE.md)
    - Geist Mono for dates, codes, timestamps
    - Border radius: 4px throughout
    - Borders: 1px solid #E5E7EB

Ralph/refs/ref-design-system.md

@@ -1,12 +1,12 @@
 # Reference: Visual Design System
 
-> The SINGLE SOURCE OF TRUTH for colors, typography, spacing, surfaces, and motion throughout the Clinical Record PMR. Aligned with the **Clinical Luxury** direction defined in CLAUDE.md.
+> The SINGLE SOURCE OF TRUTH for colors, typography, spacing, surfaces, and motion throughout the Clinical Record PMR. Follows the **Clinical Luxury** direction in CLAUDE.md.
 
 ---
 
 ## Design Philosophy
 
-This is a **premium portfolio** that uses the structure and metaphor of a GP clinical system — not a faithful NHS software clone. Real clinical systems (EMIS Web, SystmOne) are dense, border-heavy, and purely functional. We keep their *structure* (patient banner, sidebar navigation, record sections, tables, status indicators) but elevate the *execution* with refined typography, atmospheric depth, and considered whitespace.
+A **premium portfolio** that uses the structure and metaphor of a GP clinical system — not a faithful NHS software clone. Real clinical systems (EMIS Web, SystmOne) are dense, border-heavy, and purely functional. We keep their *structure* (patient banner, sidebar navigation, record sections, tables, status indicators) but elevate the *execution* with refined typography, atmospheric depth, and considered whitespace.
 
 The goal is contrast: clinical precision married to luxury refinement. The "wow" comes from recognizing the clinical metaphor while being surprised by how good it looks.
 
@@ -17,9 +17,9 @@ The goal is contrast: clinical precision married to luxury refinement. The "wow"
 **Light-mode only.** The metaphor demands it — clinical systems operate under bright consulting room lights. No dark mode.
 
 **Backgrounds:**
-- Main content area: `#F5F7FA` — cool light gray base. Add atmospheric depth: a very faint noise/grain texture overlay, or a subtle warm tint, so it feels like quality paper rather than a flat spreadsheet. The content surface should have *presence*.
+- Main content area: `#F5F7FA` — cool light gray base. Add atmospheric depth — a faint noise/grain texture overlay or a subtle warm tint — so the surface feels like quality paper, not a flat spreadsheet.
 - Card/panel surfaces: `#FFFFFF` — clean white. Cards float above the content surface via layered shadows (see Surfaces section).
-- Sidebar: `#1E293B` — dark blue-gray. The gravitas anchor. This dark chrome is what makes it feel like "serious software."
+- Sidebar: `#1E293B` — dark blue-gray. The gravitas anchor — dark chrome that reads as serious software.
 - Patient banner: `#334155` — lighter blue-gray with white text. Subtle drop shadow below to separate from content.
 - Login screen background: `#1E293B` — same as sidebar. Carries through to PMR entrance seamlessly.
 
@@ -30,7 +30,7 @@ The goal is contrast: clinical precision married to luxury refinement. The "wow"
 - On dark surfaces: `#FFFFFF` (white primary), `#94A3B8` (slate-400 secondary)
 
 **Accent and status colors:**
-- **NHS Blue `#005EB8`** — THE accent color. Buttons, active nav states, links, interactive elements. This is the actual NHS brand blue — it will be instantly recognized and is the strongest signal of the clinical metaphor. Use it confidently but not everywhere.
+- **NHS Blue `#005EB8`** — THE accent color. Buttons, active nav states, links, interactive elements. The actual NHS brand blue — instantly recognizable, the strongest signal of the clinical metaphor. Use it confidently but not everywhere.
 - Green `#22C55E` — active/resolved/current states. Status dots, current role indicators.
 - Amber `#F59E0B` — alerts, in-progress items. The clinical alert banner background.
 - Red `#EF4444` — urgent/critical. Used very sparingly — only genuinely important items.
@@ -47,12 +47,7 @@ The goal is contrast: clinical precision married to luxury refinement. The "wow"
 
 ## Typography
 
-Typography is the primary vehicle for the premium feel. The font choice must feel *designed* — intentional and distinctive — while still reading cleanly at small clinical-system sizes (11-14px).
-
-**Font selection:**
-- **UI / Body font**: Choose a distinctive geometric or humanist sans-serif with character. **Do not use** Inter, Roboto, Arial, or system-ui defaults — these read as generic/AI-generated. Candidates: **Satoshi**, **General Sans**, **Outfit**, **DM Sans**, or similar. The chosen font should have personality at 13px. Whichever is selected, configure it as the primary `font-family` across all UI elements.
-- **Monospace / Data font**: **Geist Mono** — for timestamps, coded entries, registration numbers, NHS numbers, tabular data values. This monospace texture is what sells the "clinical software" feel. Falls back to Fira Code.
-- **Terminal phase**: **Fira Code** — locked, do not change.
+See Claude.md for info on font choice. Typography carries the premium feel. The font choice must feel *designed* — intentional and distinctive — while reading cleanly at small clinical-system sizes (11-14px).
 
 **Type scale (tight, clinical):**
 - Patient banner name: [UI font] 600, 20px
@@ -69,7 +64,7 @@ Typography is the primary vehicle for the premium feel. The font choice must fee
 - Timestamps: Geist Mono 400, 11-12px
 - Alert banner text: [UI font] 500, 14px
 
-**Hierarchy through weight, not size.** Use 400/500/600/700 weight variations within a narrow size range. Bold section headers, medium labels, regular body. This keeps the clinical density while creating clear scannable hierarchy.
+**Hierarchy through weight, not size.** Use 400/500/600/700 weight variations within a narrow size range. Bold section headers, medium labels, regular body. This keeps the clinical density while creating clear, scannable hierarchy.
 
 ---
 
@@ -85,27 +80,27 @@ More generous than real clinical software. The clinical metaphor provides struct
 - **Border radius:** 4px default for cards, inputs, buttons (clinical precision). 12px exception for the login card only.
 - **Table row height:** 40px
 - **Section spacing:** 24px between content blocks
-- **Base unit:** 4px grid — but use it with more generosity than a real clinical system would
+- **Base unit:** 4px grid — applied more generously than in real clinical systems
 
 ---
 
 ## Surfaces & Depth
 
-This is where we diverge most from real clinical software. Real systems are flat and border-heavy. This project uses **shadows and layering** to create premium depth — while keeping borders where they're authentically clinical (tables, input fields).
+Our biggest departure from real clinical software. Real systems are flat and border-heavy; we use **shadows and layering** for depth — while keeping borders where they're authentically clinical (tables, input fields).
 
 **Cards:**
 - Border: `1px solid #E5E7EB` (keep the clinical border — it's authentic)
 - Shadow: Multi-layered — `0 1px 2px rgba(0,0,0,0.04), 0 4px 12px rgba(0,0,0,0.03)`. Gentle float, not Material Design dramatic.
 - Border-radius: `4px`
 - Hover: Cards may lift very slightly — 1-2px translateY + shadow deepens to `0 2px 4px rgba(0,0,0,0.06), 0 8px 16px rgba(0,0,0,0.04)`. Restrained, not bouncy.
-- Card headers: Light gray `#F9FAFB` background with `1px solid #E5E7EB` bottom border. Uppercase title in [UI font] 600, 12-13px. This is the most "clinical" element — keep it precise.
+- Card headers: Light gray `#F9FAFB` background with `1px solid #E5E7EB` bottom border. Uppercase title in [UI font] 600, 12-13px. The most "clinical" element — keep it precise.
 
 **Tables:**
-- Full `<table>` markup with styled headers — this is where clinical authenticity lives.
+- Full `<table>` markup with styled headers — where clinical authenticity lives.
 - Table headers: `#F9FAFB` background, `1px solid #E5E7EB` borders.
 - Alternating rows: `#FFFFFF` / `#F9FAFB` — subtle but scannable.
 - Row hover: `#EFF6FF` background (blue tint).
-- Cell borders: `1px solid #E5E7EB` — keep full borders on tables. This is authentic.
+- Cell borders: `1px solid #E5E7EB` — keep full borders on tables. Authentic.
 
 **Sidebar:**
 - Background: `#1E293B`
@@ -131,21 +126,21 @@ Motion should feel **considered and premium** — never flashy, never gratuitous
 - Patient banner slides down: 200ms, ease-out
 - Sidebar slides from left: 250ms, ease-out, 50ms delay
 - Content fades in: 300ms, 100ms delay after sidebar
-- This staggered materialization is the single most impactful animation moment.
+- The staggered materialization — the most impactful animation.
 
 **Navigation switches:** Instant content swap. No crossfade, no slide. This preserves the "software application" feel — clinical systems switch tabs instantly.
 
 **Expandable content:** Height-only animation, 200ms, `ease-out`. Content grows/shrinks — no opacity fade.
 
-**Clinical alert entrance:** Spring animation (Framer Motion `type: "spring"`, moderate damping). This is the one element that *demands attention* — the spring overshoot is earned here.
+**Clinical alert entrance:** Spring animation (Framer Motion `type: "spring"`, moderate damping). The one element that *demands attention* — the spring overshoot is earned here.
 
 **Alert acknowledge:** Warning icon cross-fades to green checkmark (200ms) → hold 200ms → alert height collapses (200ms ease-out).
 
 **Hover states:** Subtle and immediate. Background-color transitions at 100ms. Card lifts are 1-2px max with shadow deepening. Think: OS-level responsiveness, not playful bouncing.
 
-**Login typing:** Character-by-character reveal: 30ms/char for username, 20ms/dot for password. Cursor blink at 530ms.
+**Login typing:** Character-by-character reveal at a natural pace: 80ms/char for username, 60ms/dot for password. Cursor blink at 530ms. After typing completes, "Log In" button becomes interactive — user clicks to proceed (not auto-triggered).
 
-**Patient banner condensation:** Smooth height transition (200ms) from 80px → 48px as user scrolls past 100px. Buttery smooth, no jank.
+**Patient banner condensation:** Height transition (200ms) from 80px → 48px as user scrolls past 100px. Buttery smooth, no jank.
 
 **`prefers-reduced-motion`:** All animations skip to final state instantly. Typing completes immediately. Alert appears without slide. Expand/collapse is instant. No exceptions.
 
@@ -153,7 +148,7 @@ Motion should feel **considered and premium** — never flashy, never gratuitous
 
 ## What Makes This Design Distinctive
 
-The memorability comes from **contrasts**:
+The design stands on **contrasts**:
 - Dark, serious sidebar next to warm, airy content
 - Small, precise monospace data in generous whitespace fields
 - NHS blue punching through an otherwise muted, restrained palette

Ralph/refs/ref-interactions.md

@@ -49,13 +49,14 @@
   - On a consultation entry: "Expand", "Copy to clipboard", "View coded entries"
   - On a medication row: "View prescribing history", "Copy to clipboard"
   - On a problem entry: "View linked consultations", "Copy to clipboard"
-- Context menus styled: white background, `1px solid #E5E7EB` border, 4px radius, `box-shadow: 0 4px 12px rgba(0,0,0,0.1)`. Items in Inter 400, 14px, 36px row height.
+- Context menus styled: white background, `1px solid #E5E7EB` border, 4px radius, `box-shadow: 0 4px 12px rgba(0,0,0,0.1)`. Items in [UI font] 400, 14px, 36px row height.
 
 ### Login Screen Typing
-- The username types character-by-character (30ms per character).
-- The password dots appear faster (20ms per dot).
+- The username types character-by-character at a natural reading pace (80ms per character).
+- The password dots appear at a deliberate pace (60ms per dot).
 - A blinking cursor appears in the active field (530ms blink interval).
-- The "Log In" button shows a brief active/pressed state before the interface materializes.
+- After typing completes, the "Log In" button becomes clearly interactive (full opacity, hover state). The user clicks it to proceed — this is NOT auto-triggered.
+- On click, the button shows a brief pressed state before the interface materializes.
 
 ---
 

Ralph/refs/ref-investigations-documents.md

@@ -109,13 +109,13 @@ The preview panel uses the same tree-indented structure as the Investigations ex
 
 ---
 
-## Design Guidance (from /frontend-design)
+## Design Guidance
 
 ### Aesthetic Direction
 
-**Tone:** Clinical utilitarian — faithful reproduction of NHS clinical software (EMIS Web / SystmOne). Zero decorative flourish. Borders as the dominant structuring element. Dense, scannable, table-first. Light-mode only. The visual language is institutional and familiar to any NHS clinician.
+**Tone:** Clinical Luxury — the *structure* of clinical investigation results and attached documents (tables, status badges, expandable rows) executed with premium refinement. Borders provide authentic clinical structuring; layered shadows, generous spacing, and refined typography provide the luxury finish. Light-mode only.
 
-**Differentiation:** The expanded-row tree-indented monospace structure using box-drawing characters is the signature element. It transforms a flat data table into something that reads like a lab report or radiology result — structured, indented, with labelled fields in `Geist Mono`. The pipe-and-branch characters (`├─`, `│`, `└─`) create a distinctly clinical-system aesthetic that no standard portfolio site would ever use.
+**Differentiation:** The expanded-row tree-indented monospace structure using box-drawing characters is the signature element. It transforms a flat data table into something that reads like a lab report or radiology result — structured, indented, with labelled fields in `Geist Mono`. The pipe-and-branch characters (`├─`, `│`, `└─`) create a distinctly clinical aesthetic that no standard portfolio site would ever use.
 
 ### Key Design Decisions
 
@@ -136,11 +136,12 @@ Both views share an identical expand/collapse mechanic:
 
 #### Typography & Spacing
 
-- **Primary font:** Inter (text, labels, table headers)
+- **Primary font:** [UI font] (text, labels, table headers — Elvaro or Blumir, see CLAUDE.md)
 - **Monospace font:** Geist Mono (tree-indented expanded content)
 - **Border radius:** 4px throughout
 - **Border color:** `#E5E7EB` (Tailwind gray-200)
 - **NHS Blue:** `#005EB8` (action buttons, links)
+- **Card shadow:** Multi-layered per design system
 
 ### Implementation Patterns
 

Ralph/refs/ref-medications.md

@@ -65,7 +65,7 @@ Skills are grouped into three "medication types," mimicking how clinical systems
 
 ## Table Styling
 
-- Table headers: Inter 600, 13px, uppercase, gray-400, `#F9FAFB` background
+- Table headers: [UI font] 600, 13px, uppercase, gray-400, `#F9FAFB` background
 - Table rows: alternating `#FFFFFF` / `#F9FAFB` backgrounds
 - Row height: 40px
 - All borders: `1px solid #E5E7EB`
@@ -94,44 +94,44 @@ Table columns are sortable by clicking the header. Clicking "Dose" sorts by prof
 
 ---
 
-## Design Guidance (from /frontend-design)
+## Design Guidance
 
 ### Aesthetic Direction
 
-**Clinical-Utilitarian / NHS PMR Fidelity**
+**Clinical Luxury**
 
-This implementation follows the Clinical Record (Design 7) medications-as-skills metaphor with absolute fidelity to the specification. The aesthetic is clinical-utilitarian: light-mode only, border-heavy, table-driven, zero decorative flourish. Every design decision mirrors real NHS PMR systems (EMIS Web, SystmOne). The component is not themed loosely -- it is a faithful reproduction of how medications lists appear in actual GP clinical software, repurposed to present skills as active prescriptions.
+The medications-as-skills metaphor uses the *structure* of an active medications list — tabs, table layout, status indicators, prescribing history — but executed with premium refinement. Layered shadows on cards, generous spacing, refined typography. Light-mode only.
 
-**Purpose:** Present 18 professional skills as an active medications list that clinicians will instantly recognize and recruiters will find navigable and information-dense.
+**Purpose:** Present 18 professional skills as an active medications list. Clinicians recognize the format; recruiters get navigable, information-dense content.
 
-**Tone:** Institutional, functional, border-heavy. No shadows, no rounded corners beyond 4px, no gradients. Clinical systems are designed for rapid information retrieval under time pressure -- that same quality makes this an efficient skills display.
+**Tone:** Precise, structured, refined. Tables and borders provide clinical authenticity; shadows, typography, and spacing provide the luxury finish. Clinical systems are designed for rapid information retrieval under time pressure — that same quality makes this an efficient skills display.
 
-**Constraints followed:**
-- Light-mode ONLY (clinical systems are light-mode by design)
+**Constraints:**
+- Light-mode ONLY
 - NHS blue `#005EB8` as the sole accent color
-- Border radius capped at 4px
-- Inter for all text, Geist Mono for prescribing history data
-- All borders `1px solid #E5E7EB`
-- No decorative elements whatsoever
+- Border radius 4px for clinical elements
+- [UI font] for all text (Elvaro or Blumir — see CLAUDE.md), Geist Mono for prescribing history data
+- Borders `1px solid #E5E7EB` on tables
+- Card surfaces with multi-layered shadows per design system
 
-**Differentiation:** The medications-as-skills mapping provides richer data than any traditional "skills list." Dose maps to proficiency, Frequency maps to usage patterns, Start maps to when the skill was acquired, and prescribing history shows the skill's evolution over time. This is not decoration -- it is genuinely useful information architecture.
+**Differentiation:** The medications-as-skills mapping provides richer data than any traditional "skills list." Dose maps to proficiency, Frequency maps to usage patterns, Start maps to when the skill was acquired, and prescribing history shows the skill's evolution over time. Genuinely useful information architecture.
 
 ### Key Design Decisions
 
 #### 1. Three Category Tabs
 - **"Active Medications"** (8 technical skills), **"Clinical Medications"** (6 healthcare domain skills), **"PRN (As Required)"** (4 strategic/leadership skills)
 - Active tab: white background + NHS blue (`#005EB8`) 2px bottom border
-- Inactive tabs: `#F9FAFB` background, gray text, hover brightens
+- Inactive tabs: `#F9FAFB` background, gray text, hover brightens to white
 - Count badges show the number of items per category
 - Full ARIA `role="tablist"`, `role="tab"`, `aria-selected`, `aria-controls` semantics
 
 #### 2. Semantic HTML Table
 - Proper `<table>`, `<thead>`, `<th scope="col">`, `<tbody>`, `<tr>`, `<td>` markup
 - Five columns: Drug Name, Dose, Frequency, Start, Status
-- Headers: Inter 600, 13px, uppercase, 0.03em tracking, `#F9FAFB` background
+- Headers: [UI font] 600, 13px, uppercase, 0.03em tracking, `#F9FAFB` background
 - Row height: 40px
 - Alternating `#FFFFFF` / `#F9FAFB` row backgrounds via CSS `:nth-child(even)`
-- Hover state: `#EFF6FF` (subtle blue tint) -- **no transform, no lift, no shadow**
+- Hover state: `#EFF6FF` (subtle blue tint)
 - Status dots: 6px green circles inline with "Active" text
 - All borders: `1px solid #E5E7EB`
 

Ralph/refs/ref-problems.md

@@ -61,13 +61,13 @@ Traffic lights are 8px circles with the status colors (green, amber, red, gray).
 
 ---
 
-## Design Guidance (from /frontend-design)
+## Design Guidance
 
 ### Aesthetic Direction
 
-**Clinical Utilitarian** — This is not a place for flashy gradients or playful animation. The metaphor demands the disciplined, functional aesthetic of an actual NHS clinical system. Think EMIS/SystmOne: white backgrounds, precise table layouts, 1px borders, quiet colour discipline. The visual power comes from the *content structure*, not decoration. The traffic light dots and expandable narratives do all the heavy lifting. Every pixel serves a clinical purpose.
+**Clinical Luxury** — The Problems view uses the clinical structure of a problem list (traffic lights, coded entries, expandable narratives) but executes with premium refinement. White card surfaces with layered shadows, generous padding, refined typography. The visual power comes from the *content structure* — traffic light dots and expandable narratives do the heavy lifting — while the luxury finish makes it feel polished and intentional.
 
-The distinctiveness comes from the *concept itself* — framing career achievements as a Problem List is the creative act. The execution must be restrained to sell the metaphor.
+The distinctiveness comes from the *concept itself* — framing career achievements as a Problem List is the creative act. The premium execution makes it memorable.
 
 ### Key Design Decisions
 
@@ -78,18 +78,18 @@ The distinctiveness comes from the *concept itself* — framing career achieveme
    - Implementation uses flexbox with gap-2 for dot-label pairing
 
 2. **Typography System**
-   - **Inter** for all body text, headers, and UI labels — clean, clinical, readable
+   - **[UI font]** for all body text, headers, and UI labels (Elvaro or Blumir — see CLAUDE.md)
    - **Geist Mono** for codes and dates — SNOMED-style codes like `[EFF001]`, `[MGT001]` must be monospace
    - Font sizes: 13px for table headers (uppercase, tracking-wider), 14px for body text
-   - Header styling: `font-inter font-semibold text-xs uppercase tracking-wider text-gray-400`
+   - Header styling: `font-ui font-semibold text-xs uppercase tracking-wider text-gray-400`
 
 3. **Color Palette (Locked)**
-   - Light-mode ONLY (clinical systems are light-mode by design)
+   - Light-mode ONLY
    - NHS Blue: `#005EB8` (Tailwind `text-pmr-nhsblue`) — used for links and accents
    - Borders: `1px solid #E5E7EB` (gray-200) — consistent table borders
-   - Row hover: `#EFF6FF` (blue-50) — subtle clinical highlight
-   - Background: White cards on `#F5F7FA` (pmr-content) background
-   - Border radius: 4px max — clinical systems use sharp corners
+   - Row hover: `#EFF6FF` (blue-50) — subtle highlight
+   - Background: White cards on `#F5F7FA` (pmr-content) background with layered shadows per design system
+   - Border radius: 4px for clinical elements
 
 4. **Table Structure**
    - Semantic HTML: `<table>`, `<thead>`, `<th scope="col">`, `<tbody>`, `<tr>`, `<td>`

Ralph/refs/ref-referrals.md

@@ -1,12 +1,12 @@
 ---
 
-## Design Guidance (from /frontend-design)
+## Design Guidance
 
 ### Aesthetic Direction
 
-**Tone: Clinical Utilitarian** — This is an NHS-styled patient medical record system. The aesthetic is intentionally institutional: clean, functional, bureaucratic-in-a-charming-way. The humor comes from the deadpan application of clinical form conventions to a personal contact form. No flourishes, no gradients, no decorative frills. The beauty is in the precision of the grid, the crispness of the type hierarchy, and the tongue-in-cheek seriousness of it all.
+**Tone: Clinical Luxury** — A contact form styled as a clinical referral, with the *structure* of an NHS referral form (priority levels, reference numbers, clinical fields) but executed with premium refinement. The humor comes from the deadpan application of clinical form conventions to a personal contact form. The beauty is in the precision of the grid, the crispness of the type hierarchy, refined inputs, and the tongue-in-cheek seriousness of it all.
 
-**What makes it memorable**: The collision between NHS clinical form seriousness and the fact that you are "referring" to a person's contact page. The pre-filled "patient" header, the priority radio buttons with their wry tooltips, the reference number generation — all of this is a joke delivered with a completely straight face.
+**What makes it memorable**: The collision between clinical form structure and the fact that you are "referring" to a person's contact page. The pre-filled "patient" header, the priority radio buttons with their wry tooltips, the reference number generation — all of this is a joke delivered with a completely straight face, in a beautifully finished package.
 
 ### Key Design Decisions
 
@@ -37,7 +37,7 @@ Each priority option features a colored dot indicator and supports hover tooltip
 | Card border | `1px solid #E5E7EB` | `border-pmr-border` |
 | Input border | `1px solid #D1D5DB` | `border-pmr-border-dark` |
 | Border radius | `4px` | `rounded` |
-| Label font | Inter 500, 13px, gray-600 | `font-inter font-medium text-sm text-gray-600` |
+| Label font | [UI font] 500, 13px, gray-600 | `font-ui font-medium text-sm text-gray-600` |
 | Mono font | Geist Mono | `font-mono` (reference numbers) |
 | Input padding | `8px 12px` | `py-2 px-3` |
 | Focus state | NHS blue border + glow | `focus:border-pmr-nhsblue focus:ring-2 focus:ring-pmr-nhsblue/15` |

Ralph/refs/ref-summary-alert.md

@@ -8,7 +8,7 @@
 
 The landing view after login. This mimics the "Patient Summary" screen — the first screen a clinician sees when opening a patient record, showing the most important information at a glance.
 
-**Layout:** A grid of summary cards arranged in a 2-column layout on desktop, single column on mobile. Each card has a header bar with the card title in Inter 600, 14px, uppercase, on a `#F9FAFB` background with `1px solid #E5E7EB` bottom border.
+**Layout:** A grid of summary cards arranged in a 2-column layout on desktop, single column on mobile. Each card has a header bar with the card title in [UI font] 600, 14px, uppercase, on a `#F9FAFB` background with `1px solid #E5E7EB` bottom border.
 
 ### Card 1: Patient Demographics (spans full width)
 
@@ -21,7 +21,7 @@ The landing view after login. This mimics the "Patient Summary" screen — the f
 +---------------------------------------------------------------------+
 ```
 
-A two-column key-value table. Labels in Inter 500, 13px, gray-500. Values in Inter 400, 14px, gray-900. Labels right-aligned, values left-aligned — mimicking clinical system demographics layout.
+A two-column key-value table. Labels in [UI font] 500, 13px, gray-500. Values in [UI font] 400, 14px, gray-900. Labels right-aligned, values left-aligned — clinical form layout.
 
 ### Card 2: Active Problems (left column)
 
@@ -34,7 +34,7 @@ A two-column key-value table. Labels in Inter 500, 13px, gray-500. Values in Int
 +---------------------------------------------------------------------+
 ```
 
-A list with green dots for active/current items, amber dots for in-progress items. Each entry has a title in Inter 500, 14px, and a date range or status in Geist Mono, 12px, right-aligned. Click an entry to navigate to the corresponding Consultation.
+A list with green dots for active/current items, amber dots for in-progress items. Each entry has a title in [UI font] 500, 14px, and a date range or status in Geist Mono, 12px, right-aligned. Click an entry to navigate to the corresponding Consultation.
 
 ### Card 3: Current Medications — Quick View (right column)
 
@@ -89,7 +89,7 @@ When the user first loads the Summary view (immediately after the login transiti
 - Background: amber (`#FEF3C7` — amber-100, light amber)
 - Left border: 4px solid `#F59E0B` (amber-500)
 - Warning icon: `AlertTriangle` from Lucide, amber-600
-- Text: Inter 500, 14px, `#92400E` (amber-800)
+- Text: [UI font] 500, 14px, `#92400E` (amber-800)
 - "Acknowledge" button: small outlined button, amber border and text
 
 ### Behavior
@@ -117,19 +117,19 @@ This second alert reinforces the key technical achievement in clinical language.
 
 ---
 
-## Design Guidance (from /frontend-design)
+## Design Guidance
 
 ### Aesthetic Direction
 
-**Clinical Precision Meets Professional Polish**
+**Clinical Luxury**
 
-The NHS clinical record aesthetic draws from real-world electronic patient record systems (EPR), balancing institutional gravitas with polished execution. Key visual principles:
+The Summary view and Clinical Alert use clinical structure (card-based summary, status dots, coded entries, alert banners) with premium execution. Key visual principles:
 
-- **Light-mode ONLY** — Consistent with clinical systems that prioritize readability over dark aesthetics
-- **NHS blue (#005EB8)** — Institutional anchor color for headers and accents
-- **Card-based architecture** — All information lives in contained, bordered cards (1px solid #E5E7EB, 4px border-radius)
-- **Monospace for data** — Geist Mono for all coded entries, dates, and numerical values (creates clinical system authenticity)
-- **High information density** — Compact layouts that maximize data visibility (16px card padding, tight line-heights)
+- **Light-mode ONLY**
+- **NHS blue (#005EB8)** — The accent color for headers and accents
+- **Card-based architecture** — All information lives in contained, bordered cards with layered shadows (per design system)
+- **Monospace for data** — Geist Mono for all coded entries, dates, and numerical values (clinical texture)
+- **Generous but structured** — More whitespace than a real clinical system. Cards have 16-24px padding. Content breathes.
 - **Status dots** — Green/amber/red traffic light indicators for at-a-glance status assessment
 
 ### Key Design Decisions
@@ -157,9 +157,9 @@ This sequence transforms dismissal from a jarring disappearance into a satisfyin
 
 **3. Typography Hierarchy**
 
-- **Card headers**: Inter 600, 14px, uppercase, letter-spacing-wide — creates clear section delineation
-- **Labels**: Inter 500, 13px, gray-500, right-aligned — mimics clinical form layout
-- **Values**: Inter 400, 14px, gray-900, left-aligned — primary data focus
+- **Card headers**: [UI font] 600, 14px, uppercase, letter-spacing-wide — creates clear section delineation
+- **Labels**: [UI font] 500, 13px, gray-500, right-aligned — clinical form layout
+- **Values**: [UI font] 400, 14px, gray-900, left-aligned — primary data focus
 - **Coded values**: Geist Mono, 12px — all dates, IDs, percentages, status codes
 
 ### Implementation Patterns

Ralph/refs/ref-transition-login.md

@@ -18,16 +18,16 @@ The flatline has a subtle audio-visual implication without actual sound — the
 
 The entire canvas fades to black over 200ms (the name and flatline dissolve into darkness). Then, from black, the background transitions to a dark blue-gray (`#1E293B`) over 200ms. This is the color of a clinical system login screen — the dark institutional background that every NHS worker recognizes from their Monday morning.
 
-## Phase 3: Login Sequence (1200ms)
+## Phase 3: Login Sequence (user-paced)
 
-A login panel materializes center-screen: a white card (320px wide, 12px border-radius, subtle shadow) on the dark blue-gray background. The card contains:
+A login panel materializes center-screen: a white card (320px wide, 12px border-radius, refined shadow) on the dark blue-gray background. The card contains:
 
 - A small NHS-blue shield icon or generic clinical system logo at the top
-- **Username field**: Empty text input with label "Username". After 200ms, a cursor appears and types `A.CHARLWOOD` character by character (30ms per character, ~350ms total). The typing uses Geist Mono / monospace font.
-- **Password field**: After a 150ms pause, dots fill the password field in rapid succession (8 dots, 20ms each, ~160ms total).
-- **"Log In" button**: NHS blue (`#005EB8`), full width. After another 150ms pause, the button receives a subtle pressed state (darkens slightly, 100ms) as if clicked.
+- **Username field**: Empty text input with label "Username". After 400ms, a cursor appears and types `A.CHARLWOOD` character by character at a natural reading pace (80ms per character, ~880ms total). The typing uses Geist Mono / monospace font.
+- **Password field**: After a 300ms pause, dots fill the password field at a deliberate pace (8 dots, 60ms each, ~480ms total).
+- **"Log In" button**: NHS blue (`#005EB8`), full width. After typing completes, the button becomes clearly available as a **user-interactive element**. The user clicks it to proceed. The button should have a visible hover state and feel like a natural call-to-action — this is the moment where the user "logs in" to the record.
 
-The login card holds for 200ms in its "submitted" state, then...
+**Important**: The login button is NOT auto-clicked. The user must click it. This creates a deliberate, satisfying interaction — the user is choosing to enter the record. On click, the button shows a brief pressed state (darkens slightly, 100ms), then...
 
 ## Phase 4: Interface Materialization (500ms)
 
@@ -42,42 +42,41 @@ The login card scales up slightly (103%) and fades out (200ms). As it fades, the
 
 The full PMR interface is visible: patient banner at top, dark sidebar on left, Summary view in the main content area, and the clinical alert banner demanding attention. The user is now "logged in" to Andy's career record.
 
-**Total transition duration:** ~2.7 seconds
+**Total transition duration:** ~2s for typing to complete, then user-paced (waits for button click), then ~500ms for interface materialization.
 
 ## Why This Works
 
-The login sequence is the most immersive transition of all designs. Every NHS worker, every pharmacist, every GP has typed their credentials into a clinical system at 8am on a Monday. This transition puts them right there. It's specific, it's authentic, and it immediately establishes the metaphor: you are opening a patient record. The "patient" happens to be a career.
+The login sequence is the most immersive transition. Every NHS worker, every pharmacist, every GP recognizes the shape of a clinical login screen. This transition evokes that recognition — but executed with premium refinement rather than institutional austerity. The natural typing pace lets the user absorb what's happening. And the interactive login button is the pivotal moment: the user *chooses* to enter the record. That moment of agency makes the experience feel personal, not passive.
 
 ## Login Animation Implementation Notes
 
 - Component mounts with dark blue-gray background
 - Login card fades in (Framer Motion, 200ms)
-- Username typing: `setInterval` adds one character per 30ms to a state string
-- Password dots: `setInterval` adds one dot per 20ms
-- Button press: state change triggers visual pressed state, then 200ms delay
-- `onComplete` callback fires, parent component swaps to PMRInterface
-- Typing respects `prefers-reduced-motion` — with reduced motion, full username appears instantly and login completes in ~500ms total
+- Username typing: `setInterval` adds one character per 80ms to a state string (~880ms total)
+- Password dots: `setInterval` adds one dot per 60ms (~480ms total)
+- After typing completes: button becomes interactive (opacity goes to 1, cursor: pointer)
+- **User clicks the "Log In" button** — this is NOT auto-triggered
+- On click: button shows pressed state (100ms), then `onComplete` callback fires
+- Typing respects `prefers-reduced-motion` — with reduced motion, full username and password appear instantly, button is immediately interactive
 - **Font: Geist Mono** for username/password fields (NOT Fira Code)
 
 ---
 
-## Design Guidance (from /frontend-design)
+## Design Guidance
 
-> Pre-baked design direction. Do NOT invoke `/frontend-design` at runtime — this section contains the output.
+### Aesthetic Direction: Clinical Luxury
 
-### Aesthetic Direction: Institutional Utilitarian
-
-This is not "exciting" design — it is the visual equivalent of fluorescent lights, laminate desks, and the smell of hand sanitiser at 07:58 on a Monday morning. The card must look like every single hospital login prompt a doctor has ever seen: clean white, unadorned, functional. No personality. The branding is the only concession to identity. The magic is not visual flair — it is the uncanny recognition of "oh, this is exactly what that looks like" combined with the satisfying typewriter rhythm of credentials appearing.
+The login card evokes the structure of a clinical system login — shield icon, two fields, a button — but executed with premium refinement. Clean white card with refined shadow, considered spacing, and the satisfying rhythm of credentials appearing at a natural pace. The recognition factor ("oh, this looks like a clinical login") is the creative hook; the premium finish is what makes it memorable.
 
 ### Key Design Decisions
 
-1. **Active field focus ring**: NHS-blue border (`1px solid #005EB8`) on the currently active field, inactive fields shift to `#FAFAFA` background. Mirrors real NHS login forms (Lorenzo, SystmOne, EMIS Web). Transition 150ms.
-2. **Reduced shadow to spec**: Use exactly `0 1px 2px rgba(0,0,0,0.03)`. Card sits on dark background through border definition, not shadow depth — more faithful to real NHS software.
-3. **Border**: Use `1px solid #E5E7EB` per design system (not `rgba(255,255,255,0.1)`).
-4. **Timer cleanup**: Track every `setInterval` and `setTimeout` via refs, clear all on unmount.
-5. **Consolidated active field state**: Single `activeField` state (`'username' | 'password' | null`) instead of separate booleans.
-6. **Accessibility**: `role="status"` + `aria-label` on outer container. Cursor pipes `aria-hidden="true"`. Card entrance `scale: 0.98` (not 0).
-7. **The Monday-morning feeling**: No gradients, no decorative elements, no loading spinners, no "Welcome back!" messaging. Just white rectangle on gray, shield icon, two fields, button. Typing speed deliberately mechanical.
+1. **Active field focus ring**: NHS-blue border (`1px solid #005EB8`) on the currently active field, inactive fields shift to `#FAFAFA` background. Clinical login convention. Transition 150ms.
+2. **Refined card shadow**: Multi-layered shadow `0 1px 2px rgba(0,0,0,0.04), 0 4px 12px rgba(0,0,0,0.03)` — the card should feel like it floats above the dark background. Combined with `1px solid #E5E7EB` border.
+3. **Timer cleanup**: Track every `setInterval` and `setTimeout` via refs, clear all on unmount.
+4. **Consolidated active field state**: Single `activeField` state (`'username' | 'password' | 'done' | null`) instead of separate booleans. `'done'` state indicates typing is complete and button is ready.
+5. **Accessibility**: `role="status"` + `aria-label` on outer container. Cursor pipes `aria-hidden="true"`. Card entrance `scale: 0.98` (not 0).
+6. **User-initiated login**: After typing completes, the "Log In" button is clearly interactive. Hover state (slight darken), cursor: pointer, and the button should feel like an invitation to click. This is the one moment of user agency in the boot sequence — make it satisfying.
+7. **Natural typing pace**: 80ms/char for username, 60ms/dot for password. Deliberate and readable, not frantically fast.
 
 ### Implementation Pattern
 
@@ -94,9 +93,10 @@ interface LoginScreenProps {
 const [username, setUsername] = useState('')
 const [passwordDots, setPasswordDots] = useState(0)
 const [showCursor, setShowCursor] = useState(true)
-const [activeField, setActiveField] = useState<'username' | 'password' | null>('username')
+const [activeField, setActiveField] = useState<'username' | 'password' | 'done' | null>('username')
 const [buttonPressed, setButtonPressed] = useState(false)
 const [isExiting, setIsExiting] = useState(false)
+const [typingComplete, setTypingComplete] = useState(false)
 
 const fullUsername = 'A.CHARLWOOD'
 const passwordLength = 8
@@ -111,7 +111,7 @@ Card structure:
     padding: '32px',
     borderRadius: '12px',
     border: '1px solid #E5E7EB',
-    boxShadow: '0 1px 2px rgba(0, 0, 0, 0.03)',
+    boxShadow: '0 1px 2px rgba(0,0,0,0.04), 0 4px 12px rgba(0,0,0,0.03)',
   }}
   initial={{ opacity: 0, scale: 0.98 }}
   animate={isExiting ? { scale: 1.03, opacity: 0 } : { scale: 1, opacity: 1 }}
@@ -131,12 +131,12 @@ Branding header:
     <Shield size={26} style={{ color: '#005EB8' }} strokeWidth={2.5} />
   </div>
   <span style={{
-    fontFamily: "'Inter', system-ui, sans-serif",
+    fontFamily: "'[UI font]', system-ui, sans-serif",
     fontSize: '13px', fontWeight: 600,
     color: '#64748B', letterSpacing: '0.01em',
   }}>CareerRecord PMR</span>
   <span style={{
-    fontFamily: "'Inter', system-ui, sans-serif",
+    fontFamily: "'[UI font]', system-ui, sans-serif",
     fontSize: '11px', fontWeight: 400,
     color: '#94A3B8', marginTop: '2px',
   }}>Clinical Information System</span>
@@ -165,18 +165,25 @@ Input field pattern (username example):
 </div>
 ```
 
-Login button:
+Login button (interactive — user clicks to proceed):
 ```tsx
-<button style={{
-  width: '100%',
-  padding: '10px 16px',
-  fontFamily: "'Inter', system-ui, sans-serif",
-  fontSize: '14px', fontWeight: 600,
-  color: '#FFFFFF',
-  backgroundColor: buttonPressed ? '#004494' : '#005EB8',
-  border: 'none',
-  borderRadius: '4px',
-}}>Log In</button>
+<button
+  onClick={typingComplete ? handleLogin : undefined}
+  disabled={!typingComplete}
+  style={{
+    width: '100%',
+    padding: '10px 16px',
+    fontFamily: "'[UI font]', system-ui, sans-serif",
+    fontSize: '14px', fontWeight: 600,
+    color: '#FFFFFF',
+    backgroundColor: buttonPressed ? '#004494' : '#005EB8',
+    border: 'none',
+    borderRadius: '4px',
+    cursor: typingComplete ? 'pointer' : 'default',
+    opacity: typingComplete ? 1 : 0.6,
+    transition: 'background-color 150ms, opacity 300ms',
+  }}
+>Log In</button>
 ```
 
 Typing sequence (reduced motion branch):
@@ -184,18 +191,21 @@ Typing sequence (reduced motion branch):
 if (prefersReducedMotion) {
   setUsername(fullUsername)
   setPasswordDots(passwordLength)
-  setActiveField(null)
-  setTimeout(() => { setButtonPressed(true); setTimeout(triggerComplete, 100) }, 300)
+  setActiveField('done')
+  setTypingComplete(true)
+  // Button is immediately available for user to click
   return
 }
-// Normal: username at 30ms/char, 150ms pause, password at 20ms/dot, 150ms pause, button press
+// Normal: username at 80ms/char, 300ms pause, password at 60ms/dot
+// After typing completes: setTypingComplete(true), button becomes interactive
+// User clicks "Log In" to proceed — no auto-click
 ```
 
 Footer:
 ```tsx
 <div style={{ marginTop: '22px', paddingTop: '18px', borderTop: '1px solid #E5E7EB' }}>
   <p style={{
-    fontFamily: "'Inter', system-ui, sans-serif",
+    fontFamily: "'[UI font]', system-ui, sans-serif",
     fontSize: '11px', color: '#94A3B8', textAlign: 'center',
   }}>Secure clinical system login</p>
 </div>