Deliverables (8/10 agents complete): - S3-H01: Pitch deck emphasizing sticky engagement (daily camera, maintenance, inventory) - S3-H02: 5-min demo script showing weekly app usage (not just resale-time) - S3-H03: ROI calculator (€28K-€48K inventory tracking value) - S3-H04: Objection handling playbook (5+ objections with data-backed responses) - S3-H05: 3-tier pricing strategy + Riviera Plaisance pilot program - S3-H06: Competitive differentiation vs 5 yacht doc competitors - S3-H07: Technical architecture diagram (Mermaid visualization) - S3-H09: Visual design system (nautical theme, typography, icons) Blocked waiting for Sessions 1+2 handoff files: - S3-H08: Case Study Writer (needs Session 1 pain points) - S3-H10: Sales Collateral Synthesis (needs all session data) IF.bus protocol: All agents sent inform/validate messages for coordination Token efficiency: 100% Haiku delegation (Agents 1-9)
131 lines
5.7 KiB
Markdown
131 lines
5.7 KiB
Markdown
# NaviDocs System Architecture
|
|
|
|
## Mermaid Architecture Diagram
|
|
|
|
```mermaid
|
|
graph TD
|
|
A["🏠 Yacht Owner<br/>Mobile/Web"] -->|Uploads Documents| B["📄 Document OCR<br/>Processing Engine"]
|
|
|
|
B -->|Extracts Data| C["💾 Warranty Database<br/>Central Store"]
|
|
|
|
C --> D["⏰ Expiration Tracker<br/>Smart Monitor"]
|
|
|
|
D -->|Low Stock Alert| A
|
|
D -->|Upcoming Expiry| A
|
|
D -->|Warranty Claims| E["📋 Claim Package<br/>Generator"]
|
|
|
|
E -->|Auto-compiles<br/>Documents| A
|
|
|
|
F["🏠 Home Assistant<br/>Smart Home Hub"] -->|Webhooks| C
|
|
F -->|Camera Feeds| B
|
|
F -->|Sensor Data| C
|
|
|
|
G["📱 Mobile Device<br/>Offline Mode"] -->|Service Workers| H["🔄 Local Cache<br/>Sync Queue"]
|
|
H -->|Syncs When Online| C
|
|
|
|
I["🔐 Multi-Tenant<br/>Isolation Layer"] -->|JWT Auth| C
|
|
I -->|Database Partitioning| C
|
|
I -->|Row-Level Security| C
|
|
|
|
style A fill:#e1f5ff
|
|
style B fill:#fff3e0
|
|
style C fill:#f3e5f5
|
|
style D fill:#fce4ec
|
|
style E fill:#e0f2f1
|
|
style F fill:#fff9c4
|
|
style G fill:#e8f5e9
|
|
style H fill:#e8f5e9
|
|
style I fill:#ffebee
|
|
```
|
|
|
|
## Component Explanations
|
|
|
|
### 1. **Document Upload & OCR Processing**
|
|
**What it does:** Yacht owners upload physical warranty documents (photos, PDFs) through the mobile or web app. The OCR (Optical Character Recognition) engine automatically reads the documents and extracts key warranty information like coverage dates, claim numbers, and coverage limits.
|
|
|
|
**Why it matters:** Eliminates manual data entry. Owners just take a photo of their warranty document, and the system instantly understands what coverage they have.
|
|
|
|
---
|
|
|
|
### 2. **Warranty Database (Central Store)**
|
|
**What it does:** All extracted warranty data is stored in a secure, centralized database. This is the single source of truth for all warranty information. It's organized by boat, owner, and warranty type.
|
|
|
|
**Why it matters:** Creates a searchable, organized library of all warranties. Users can instantly find any warranty detail without digging through files.
|
|
|
|
---
|
|
|
|
### 3. **Expiration Tracker & Smart Alerts**
|
|
**What it does:** The system continuously monitors warranty expiration dates. When a warranty is about to expire (or a maintenance is due), it sends automatic reminders to the yacht owner's phone.
|
|
|
|
**Why it matters:** No more missed warranty deadlines. Owners stay ahead of expirations and maintenance schedules with zero effort.
|
|
|
|
---
|
|
|
|
### 4. **Claim Package Generator**
|
|
**What it does:** When a warranty claim is needed, the system automatically compiles all relevant documents—warranty terms, proof of purchase, maintenance records, photos—into a complete claim package ready to submit.
|
|
|
|
**Why it matters:** Reduces claim submission time from hours to minutes. Everything is pre-organized and ready.
|
|
|
|
---
|
|
|
|
### 5. **Home Assistant Integration**
|
|
**What it does:** Connects to smart home devices (cameras, door sensors, water monitors) in the boat. These devices send sensor data and camera feeds that can trigger warranty claims automatically (e.g., water damage detected → start claim process).
|
|
|
|
**Why it matters:** Smart automation—warranty events can be detected automatically and claims initiated without manual intervention.
|
|
|
|
---
|
|
|
|
### 6. **Offline Mode (Service Workers & Sync)**
|
|
**What it does:** Mobile app works even without internet. Users can upload documents, view warranties, and request alerts while offline. When reconnected, all data automatically syncs to the cloud.
|
|
|
|
**Why it matters:** Yacht owners are often in remote locations with spotty internet. The app still works seamlessly.
|
|
|
|
---
|
|
|
|
### 7. **Multi-Tenant Security Architecture**
|
|
**What it does:** Each yacht owner's data is completely isolated. User A cannot see User B's warranties. Security uses JWT tokens (digital ID cards) for login and row-level database security to ensure data privacy.
|
|
|
|
**Why it matters:** Peace of mind. Sensitive warranty and insurance information is private and protected.
|
|
|
|
---
|
|
|
|
## Integration Points
|
|
|
|
| **Component** | **Connects To** | **Purpose** |
|
|
|---|---|---|
|
|
| OCR Engine | Warranty Database | Feed extracted data |
|
|
| Expiration Tracker | Alert System | Send notifications |
|
|
| Claim Generator | Warranty Database | Retrieve documents |
|
|
| Home Assistant | Warranty Database | Ingest sensor events |
|
|
| Offline Cache | Warranty Database | Sync on reconnect |
|
|
| Security Layer | All Components | Encrypt & isolate data |
|
|
|
|
---
|
|
|
|
## Data Flow: The Complete Journey
|
|
|
|
1. **Upload**: Yacht owner takes photo of warranty → uploads to app
|
|
2. **Process**: OCR engine reads document → extracts key data
|
|
3. **Store**: Warranty info saved to secure database
|
|
4. **Alert**: Expiration tracker monitors dates → sends reminder
|
|
5. **Generate**: Claim generator auto-compiles documents
|
|
6. **Sync**: Offline changes sync when online
|
|
|
|
---
|
|
|
|
## Security Features Highlighted
|
|
|
|
- **JWT Authentication**: Digital verification of user identity on every action
|
|
- **Database Isolation**: Each customer's data lives in separate partitions—cannot mix
|
|
- **Row-Level Security**: Even within a database, only authorized users can see specific records
|
|
- **Encrypted Data**: All sensitive information encrypted at rest and in transit
|
|
- **Offline Encryption**: Data cached locally is encrypted until synced
|
|
- **Audit Logging**: All access to warranty data is logged for compliance
|
|
|
|
---
|
|
|
|
## Non-Technical Summary
|
|
|
|
NaviDocs is essentially a **smart filing cabinet for yacht warranties**. Owner uploads documents → system reads them → remembers important dates → alerts when action is needed → auto-generates claim packages. It works offline, integrates with smart home devices, and keeps everything private and secure.
|
|
|
|
**The value:** What used to take hours (finding a warranty, filing a claim) now takes minutes.
|