Aevum Onboarding Persona Baseline

Primary prompt: What feels most like you right now

This document makes the onboarding/persona contract fundamental for PM, Antigravity, and future implementation. It aligns external PM guidance with the repo-level rule and is intended to stop drift into vague archetypes, fake companion behaviour, duplicate raw-write capture, and incomplete onboarding flows.

Baseline Decisions

Onboarding must feel companion-like, not quiz-like.
The user selects 1 required primary persona and 1 optional secondary persona.
Persona cards must speak in the user’s voice.
QWEN or any local model must not boot on persona card tap.
Local companion handoff may occur only after Continue.
First-party foreground user capture must use one shared direct-save path first.
Pipeline remains reserved for background intents, imports, system-generated entries, and deferred/derived processing.

Required Interaction Model

Keep the 5 intro quotes with autoplay and manual advance.
Use soft fade only; no heavy transition choreography.
After primary persona selection, softly auto-scroll toward the secondary section and Continue.
Secondary persona is optional and cannot duplicate primary.
Continue remains disabled until primary persona is selected.
If the model is unavailable, onboarding still completes with deterministic local fallback copy.

Approved Persona Set

These replace vague archetypes such as “The Analyst”, “The Mentor”, and “The Muse”.

Founder / Entrepreneur

Resonance line: I’m building something complex and need a system that keeps up with my mind.

Starting promise: Help me capture decisions, ideas, and patterns across what I’m building.

Hidden mapping: Analytical + Reflective

Operations / Project Lead

Resonance line: I need to hold a lot of moving parts without losing the thread.

Starting promise: Help me keep continuity across priorities, people, projects, and decisions.

Hidden mapping: Analytical + Reserved

Creative / Writer

Resonance line: My best thoughts come in fragments and I need a place that can hold them.

Starting promise: Help me capture unfinished ideas, themes, and creative signals before they disappear.

Hidden mapping: Exploratory + Reflective

Builder / Product / Engineer

Resonance line: I need somewhere to think through problems without losing the logic chain.

Starting promise: Help me preserve reasoning, structure, and decisions across what I’m building.

Hidden mapping: Analytical + Exploratory

Executive / Leader

Resonance line: I need a trusted private space to think clearly under pressure.

Starting promise: Help me process judgment, direction, leadership pressure, and strategic decisions.

Hidden mapping: Reserved + Reflective

Researcher / Scientist / Academic

Resonance line: I need to track how ideas evolve, not just store isolated notes.

Starting promise: Help me capture hypotheses, patterns, frameworks, and long-range intellectual continuity.

Hidden mapping: Analytical + Exploratory

Strategist / Investor

Resonance line: I want a system that helps me track how conviction forms over time.

Starting promise: Help me preserve signals, theses, contradictions, and strategic pattern memory.

Hidden mapping: Analytical + Reserved

Coach / Therapist / Advisor

Resonance line: I need a space that helps me reflect deeply and notice patterns in what I’m hearing and thinking.

Starting promise: Help me hold reflective insight, human patterns, and meaningful continuity.

Hidden mapping: Reflective + Reserved

Student / Learner

Resonance line: I want my learning to build on itself instead of constantly resetting.

Starting promise: Help me capture questions, insights, and growing understanding over time.

Hidden mapping: Exploratory + Analytical

Personal Reflection / Growth

Resonance line: I want to better understand my own patterns, thoughts, and inner life.

Starting promise: Help me reflect calmly, remember what matters, and notice patterns in myself.

Hidden mapping: Reflective + Reserved

Antigravity Non-Negotiables

No archetype labels in the onboarding grid.
No QWEN/model startup on card tap.
No duplicate direct-save plus pipeline enqueue of the same foreground user-authored input without explicit dedupe and correlation.
No fake secondary persona UI without persistence behind it.
No cloud fallback during onboarding.
No release-visible onboarding control without a complete backing state path.

Implementation Rule

This onboarding baseline is now captured in the repo at Docs/00_Product_Requirements/AEVUM_ONBOARDING_PERSONA_BASELINE_RULE.md and linked from the tooling policy. Any deviation requires explicit user approval before implementation.