# Product history — how two concepts became Elevra

Kept as a record of the ideation process, not as active documentation.

## Concept A — "Atlas" (precision matching)

Early framing centred on a 5-question identity quiz feeding a weighted match engine, returning 3–5 role models scored by identity overlap. Strong on precision and on the "missing story" accountability metric, but the quiz-first flow risked asking for sensitive information before a user had any reason to trust the product.

## Concept B — "RoleOn" (swipe discovery)

A parallel concept treated role-model discovery as a low-friction, swipeable feed of story cards — no quiz required. Strong on immediate engagement, weak on precision: nothing stopped a user from feeling like the results were generic.

## The merge

The team recognised the two concepts solved different parts of the same problem: RoleOn was the front door, Atlas was the depth behind it. Elevra combines both as two entry points into one shared story and matching layer — a user can swipe with zero commitment or run the quiz for precision matches, and either path leads to the same story detail, timeline, and take-action experience.

This merge is also why the design principle "progressive disclosure" (see [`design-and-ux.md`](./design-and-ux.md)) exists as a named principle rather than an implicit choice — it's the direct lesson learned from Concept A's weakness.