copy(a-grade): biopharma-first chip + regulated-inclusive continuity + two missing pains

[build-with-dhiraj]

Three copy-only UX moves that close the gap from a verified A- to an unqualified A on the LabOS UX evaluation v2 (findings IA-6, IA-7, EU-5). Rationale: reports/jove-labs/review/labos-ux-evaluation-v2.md.

Scope guardrails honored: copy + one tiny chip element only. No redesign, no layout change, no aesthetic change to anything that already exists. The Compliance toggle behavior is unchanged. The two LOW findings (Flow 1 title, tour "knowledge compounds") were deliberately left untouched. Zero em-dashes / en-dashes in the diff.

---

IA-6 [HIGH] — make the biopharma pain visible on the first screen

One small eyebrow chip added beside the existing hero pill, so a five-second scanner sees the regulated story without flipping the toggle. Styled to match the existing pill exactly (same rounded-full, same text-[11px] uppercase tracking-[0.12em] mono treatment, same px-3 py-1.5), in the action-blue chip family (bg-chip-bg + text-action-onchip, AA on #E7F2FD per DESIGN-SYSTEM).

• Before: single pill only — A JoVE product for research labs
• After: that pill, unchanged, now sits beside a new chip — Academic and biopharma (21 CFR Part 11)
• src/components/landing/Landing.tsx:41

IA-7 [MED] — broaden continuity from academic-only to regulated-inclusive

One clause in the hero subhead broadened so both the academic PI and the regulated buyer see themselves. Rest of the sentence intact. Mirrored in the page <meta description> so the share-preview matches the hero.

• Before (hero subhead): ...so it survives the next person leaving and the next new hire starting.
• After (hero subhead): ...so it survives turnover, an audit, and the next person who has to run it.
• src/components/landing/Landing.tsx:55
• Before (meta description): ...so it survives turnover and onboards the next hire. A JoVE product.
• After (meta description): ...so it survives turnover, an audit, and the next person who has to run it. A JoVE product.
• src/app/layout.tsx:10

EU-5 [MED] — name the two pains that appeared on no surface

Equipment-change and data-interpretation, both first-party-confirmed, were named nowhere. Two scripted-string additions into existing surfaces (no new UI), adapted to this lab's real graph (confocal / LSM 900 / ICC / Priya) so they stay grounded.

Equipment-change — one new Brain example question, with a grounded answer wired through CHAT_SCRIPTS (cites real nodes person:priya, equipment:lsm900, protocol:icc; house voice; not an abstain).

• Added question: We swapped the confocal and the ICC images look different. What did the previous owner set on the old one?
• src/lib/scripts.ts (EXAMPLE_QUESTIONS + matching CHAT_SCRIPTS entry)

Data-interpretation — one why-line on the confocal journey step, in the existing why format (read the data, not just operate the scope).

• Before (j-confocal.why): Operating the Zeiss. Prerequisite is ICC sign-off.
• After (j-confocal.why): Operating the Zeiss is half of it. Learn why Priya gates on a single-stain control before reading a triple stain, so your images mean what hers did. Prerequisite is ICC sign-off.
• src/lib/scripts.ts (SOFIA_JOURNEY, step j-confocal)

---

Local verification (same checks CI runs)

• npm run typecheck (tsc --noEmit): clean, no errors
• npm run build (next build): clean, all routes prerender static
• New strings confirmed present in built HTML for /, /flows/brain, /flows/journey
• No em-dashes or en-dashes in the diff

🤖 Generated with Claude Code