1. Purpose
This document establishes the business and product foundation for Aevum. It exists to prevent strategic drift, reduce ambiguity across product and engineering teams, and provide a single authority for what Aevum is being built to do.
Primary Use
- Align executives, product, engineering, design, security, compliance, and delivery teams.
- Define the product boundary before feature-level planning begins.
- Serve as the parent reference for PRD, architecture, compliance, and operational planning.
2. Product Identity
What Aevum Is
Aevum is a sovereign, local-first intelligence companion that helps a user capture thoughts, preserve memory continuity, and generate grounded reflection from their own private context.
What Aevum Is Not
- Not a generic chatbot.
- Not a note-taking app with AI pasted on top.
- Not a cloud-first productivity suite.
- Not a passive archive of disconnected entries.
Product Thesis
The most valuable intelligence product for an individual is not one that knows the internet best. It is one that knows the user’s own mind best, while preserving privacy, continuity, and control.
3. Problem Statement
High-intensity thinkers generate far more thought, pattern, and internal signal than conventional software can preserve. Their ideas fragment across voice notes, chats, apps, documents, and unrecorded moments. Important thoughts disappear before they can compound into clarity.
Current User Pain
- Thoughts arrive quickly and disappear quickly.
- Context is spread across too many disconnected surfaces.
- Users cannot see how patterns form over time.
- Existing AI tools do not hold durable private continuity.
Market Gap
- Most AI products optimize for answers, not continuity.
- Most memory products optimize for storage, not sense-making.
- Most productivity tools optimize tasks, not cognition.
4. Target Users
Aevum is built first for users with sustained cognitive load, recurring reflection needs, and strong value from private longitudinal memory.
| User Group | Why They Fit | Primary Mode |
|---|---|---|
| Founder / Entrepreneur | Needs fast private capture and strategic continuity. | Voice + reflection |
| Builder / Product / Engineer | Needs persistent logic trails and problem structuring. | Text + system reasoning |
| Executive / Leader | Needs safe space for judgment and decision synthesis. | Private reflection |
| Creative / Writer | Needs fragment capture and thematic continuity. | Idea capture |
| Researcher / Analyst | Needs evolving memory and pattern retrieval. | Structured recall |
| Personal Reflection User | Needs self-understanding, calm processing, and inner continuity. | Guided reflection |
5. Value Proposition
Core Promise
Aevum becomes more useful the more a user speaks, writes, and returns. It transforms scattered input into preserved continuity and grounded intelligence.
User Value
- Capture without friction.
- Private memory that compounds.
- Reflection grounded in personal context.
- Reduced cognitive loss.
Enterprise / Strategic Value
- Category-defining personal intelligence platform.
- Strong Apple-native strategic alignment.
- High defensibility through local-first architecture and memory graph continuity.
- Potential platform extension into health, productivity, and assistive cognition domains.
6. Product Principles
- Local First: core thinking workflows must work on-device.
- Private by Default: first-party foreground thinking does not leave the device.
- Continuity Over Novelty: retained context is more valuable than flashy response generation.
- Companion, Not Tool Friction: UX must feel calm, immediate, and human.
- Deterministic Core: storage and state transitions must be explicit, auditable, and stable.
- Apple-Native Quality: the product should feel at home in the Apple ecosystem.
7. Scope Boundaries
In Scope for 1.0
- Voice and text thought capture.
- Immediate local persistence.
- Memory graph foundation.
- Persona-aware companion experience.
- Context-grounded reflection.
- Import of documents, OCR, and audio.
Out of Scope for 1.0
- Cloud-first collaboration.
- Open social sharing layer.
- Multi-tenant enterprise admin console.
- Marketplace ecosystem.
- Broad third-party automation sprawl.
8. Business Goals
| Goal | Description | Time Horizon |
|---|---|---|
| Product-Market Fit | Establish strong retention around repeat capture and reflection behavior. | 12 months |
| Category Positioning | Own the narrative of private personal intelligence continuity. | 12 months |
| Platform Readiness | Build a modular architecture able to scale into enterprise-grade controls and regulated environments. | 12 months |
| Strategic Value | Create a platform attractive to major ecosystem players, especially Apple-aligned buyers. | 12-24 months |
9. Success Metrics
Primary Product Signals
- 7-day and 30-day retention driven by repeated capture.
- Frequency of weekly active capture sessions per retained user.
- Ratio of returning users who engage with memory-grounded reflection.
- User-reported sense of “this understands how I think.”
Platform Signals
- Percentage of first-party inputs entering through one canonical ingestion contract.
- Percentage of visible user-triggered actions with complete backend execution.
- Reduction of generic fallback responses in companion flows.
- Compliance readiness evidence for GDPR, SOC 2, ISO 27001, and DORA-relevant obligations where applicable.
10. Constraints
- Primary target ecosystem is Apple-native: iPhone, iPad, Mac.
- Local-first data handling is mandatory for core flows.
- Security, privacy, and auditability must be designed early, not retrofitted.
- Documentation set must remain minimal but authoritative.
- 12-month delivery window with a 50-person team requires strict scope control.
11. Assumptions
- Users will adopt voice-first capture when latency and privacy trust are strong.
- Memory-grounded responses increase retention more than generic AI responses.
- Local-first positioning is a meaningful differentiator.
- Enterprise-grade trust posture materially increases strategic value.
12. Strategic Risks
- Risk: product becomes a generic journaling or chatbot experience.
- Risk: privacy story drifts from implementation reality.
- Risk: architecture fragments into surface-specific logic instead of a single ingestion and memory contract.
- Risk: response quality remains shallow because retrieval and reasoning are not grounded in live context.
- Risk: compliance is treated as documentation-only rather than control design.
13. Approval Model
Document Owner
Founder / Product Authority
Required Approvers
- CEO / Founder
- CTO
- Head of Product
- Head of Architecture
- CISO / Security Lead for privacy and compliance alignment