docs: discovery blueprint + multi-provider design (#8)
CI / backend (push) Successful in 52s
CI / frontend (push) Successful in 14s
Deploy Staging / deploy (push) Successful in 18s
CI / backend (pull_request) Successful in 52s
CI / frontend (pull_request) Successful in 15s
Security / secrets (push) Successful in 4s
Security / dependencies (push) Successful in 55s
Security / secrets (pull_request) Successful in 4s
Security / dependencies (pull_request) Successful in 54s

This commit was merged in pull request #8.
This commit is contained in:
2026-07-01 19:59:53 +02:00
parent 9ee5d757f5
commit 4ce2df0a2b
27 changed files with 2032 additions and 0 deletions
+48
View File
@@ -0,0 +1,48 @@
# InboxIntel — Discovery & Blueprint
This folder is the **product discovery output**: a world-class specification that will
become the blueprint for the next generation of InboxIntel. It is a **planning
artifact** — no application code is changed during discovery.
> Vision: become one of the best **email search and management** experiences available —
> extremely fast, scalable, secure, and intuitive. AI is introduced **only where it
> clearly beats traditional approaches**, and never as a hard dependency.
## Non-negotiable constraints (carried into every phase)
- **AI is optional & modular.** The app must work fully with AI disabled. All AI sits
behind an `IAIProvider` abstraction (already seeded: `NullAiProvider` / `OllamaProvider`
/ `OpenAiProvider`) so providers swap without touching application logic.
- **Local-first AI.** Primary target: Ollama on an NVIDIA RTX 3080 (10 GB).
- **Privacy.** Read-only Gmail scope; AI advisory-only; no destructive AI actions.
- **Speed & security are features**, not afterthoughts.
## Document index
> **Start here:** [Executive Summary](EXECUTIVE-SUMMARY.md)
| # | Document | Phase | Status |
|---|----------|-------|--------|
| — | [Executive Summary](EXECUTIVE-SUMMARY.md) | all | ✅ draft |
| 00 | [Design Brief](00-design-brief.md) | 4A (interview) | ✅ locked |
| 01 | [Architecture Review](01-architecture-review.md) | 1 | ✅ draft |
| 02 | [Competitor Analysis](02-competitor-analysis.md) | 2 | ✅ draft |
| 03 | [User Research & Journey Maps](03-user-research.md) | 3 | ✅ draft |
| 04 | [UX/UI Redesign + Design System](04-ux-redesign-and-design-system.md) | 4A | ✅ draft |
| 05 | [Search Redesign](05-search-redesign.md) | 4B | ✅ draft |
| 06 | [AI Strategy & Model Recommendations](06-ai-strategy.md) | 5 | ✅ draft |
| 07 | [AI Feature Catalogue](07-ai-feature-catalogue.md) | 6 | ✅ draft |
| 08 | [Technical Architecture](08-technical-architecture.md) | 7 | ✅ draft |
| 09 | [Product Roadmap (MVP→v3)](09-roadmap.md) | 8 | ✅ draft |
| 10 | [Git Implementation Plan](10-git-plan.md) | 10 | ✅ draft |
| 11 | [Risk Assessment & Future Opportunities](11-risks-and-future.md) | cross-cutting | ✅ draft |
## Extension designs
- [**Multi-Provider Email Platform + Admin/Settings**](multi-provider/README.md) — evolves
InboxIntel into a small-team, multi-provider (Gmail/Outlook/IMAP) platform with OAuth-as-
login, settings, feature flags, and an admin panel. Reshapes the core assumptions above
(see the "Update" callouts in [08](08-technical-architecture.md) and [09](09-roadmap.md)).
## Conventions
- Every recommendation is a durable markdown doc suitable for long-term maintenance.
- Each feature is specified with: **problem solved · why AI (or why not) · complexity ·
estimated effort · user value · perf & privacy considerations**.
- Nothing here is implemented until explicitly approved and scheduled via the Git plan.