## Overview
Same AInstein visual identity as v1 and v2 — default shadcn theme, brand-blue primary, system sans, no overrides — pivoted around **outcomes**. The reader sees the product immediately, then four concrete capabilities, then a 90-day promise, before the workflow ever appears. This is the version you send to a buyer who already knows the category and just wants to know what they'll have in three months.
## Colors
Identical to v1 — inherits the default shadcn theme. See `apps/shots/projects/ainstein/templates/v1/DESIGN.md` for the token list. No overrides.
## Typography
Identical to v1 — system sans at every level, tight tracking on headlines, semibold/medium weights. No custom font wrapper.
## Elevation
Identical to v1 — inherited from the shadcn theme.
## Components
Composed entirely from `@repo/design-system/blocks` — no custom section components.
1. **Hero3** — split layout with the AInstein product image on the right and the outcome-led headline + CTA + disclaimer on the left.
2. **Feature3** — "Four capabilities" with the canonical content surfaces (research, mapping, drafting, publishing) as tagline + description cards.
3. **Feature24** — "What you get in the first 90 days" with the four concrete deliverables.
4. **Process1** — same six-step workflow as v1 and v2, framed as the engine behind the outcomes.
5. **Cta1** — closing centered card CTA.
## Do's and Don'ts
- Do lead with the product image, then capabilities, then the 90-day promise.
- Do frame the workflow as the engine behind outcomes, not as the main story.
- Do compose from `@repo/design-system/blocks` only.
- Don't override the shadcn theme to differentiate from v1 or v2.
- Don't bury the product image — it's the opening move.