Preserve Multiple Levels Without One Universal Voice
The app may support multiple levels, but the same guidance should not be delivered identically to all users.
Capture
- beginner;
- intermediate;
- advanced;
- professional;
- parent;
- teacher;
- returning adult;
- user without current teacher.
A broad audience increases usefulness but can make the product generic.
The app may support multiple levels, but the same guidance should not be delivered identically to all users.
Why
This decision matters because preserve Multiple Levels Without One Universal Voice constrains the product toward continuity, evidence, and human judgment rather than broad AI helpfulness.
Why-Not
A broad audience increases usefulness but can make the product generic.
Exact audience profiles, prompt variants, and state flags.
Commit
Decision: The app may support multiple levels, but the same guidance should not be delivered identically to all users.
- onboarding should collect only information that changes routing;
- level uncertainty should be handled gently;
- piece lists may help users self-identify;
- beginner routes should be more conservative;
- advanced users should not be patronized.
Public boundary: This ADR publishes the judgment and product boundary while withholding exact prompts, routes, thresholds, schemas, tests, and other reproducible implementation details where applicable.
Confidence: Medium-high for public architecture; implementation details remain private and subject to launch evidence.
Timestamp
2026-07-17