From c815ef862988231589edb14d55bc29eadd913199 Mon Sep 17 00:00:00 2001 From: Danny Stocker Date: Thu, 13 Nov 2025 02:22:59 +0100 Subject: [PATCH] CRITICAL MISSION CORRECTION: NaviDocs makes Riviera include it by default, not helps them sell boats MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Key Changes: - Mission: Make NaviDocs so compelling that Sylvain includes it BY DEFAULT with every boat sale - Sales context: Sylvain decides "you should have it by default" (not "do you need this?") - Core value prop: Document tracking/versioning with IF.TTT traceability (not just sticky features) - NEW Agent 8 (Session 2): WhatsApp group integration (CRITICAL) - Boat-specific chat: owner, after-sales, captain + NaviDocs AI agent - AI logs all chats (IF.TTT audit trail) - AI answers questions, posts updates, sends reminders - IF.TTT dogfooding: ed25519 signatures, SHA-256 hashes, citation IDs - NEW Agent 9 (Session 2): Document versioning (git-style with IF.TTT compliance) - Updated Agent 10: Week 1 prioritizes document tracking + WhatsApp (core value props) After-Sales Workflow: - Boat sold → WhatsApp group created - NaviDocs tenant joins as AI agent - Logs conversations, answers questions, posts maintenance reminders - Document versioning notifications to group Business Model: - 150 boats/year × €15/month = €27K ARR (Year 1) - Broker value: After-sales support reduction + IF.TTT warranty compliance - IF.TTT dogfooding: We're using our own traceability standards in production 🤖 Generated with Claude Code Co-Authored-By: Claude --- CLOUD_SESSION_2_TECHNICAL_INTEGRATION.md | 70 +++++++++++++++++------- NAVIDOCS-WELCOME-ONBOARDING.md | 40 ++++++++++---- 2 files changed, 79 insertions(+), 31 deletions(-) diff --git a/CLOUD_SESSION_2_TECHNICAL_INTEGRATION.md b/CLOUD_SESSION_2_TECHNICAL_INTEGRATION.md index 41850b2..72e015e 100644 --- a/CLOUD_SESSION_2_TECHNICAL_INTEGRATION.md +++ b/CLOUD_SESSION_2_TECHNICAL_INTEGRATION.md @@ -31,6 +31,8 @@ Design technical architecture for **sticky daily-use features** (inventory track - Auth: JWT + bcrypt **Critical Feature Gaps (from Session 1):** +- **No document tracking/versioning** (core value prop: warranties, manuals, service records with IF.TTT traceability) +- **No WhatsApp group integration** (boat-specific chat with owner, after-sales, captain + AI agent) - **No inventory tracking** (€15K-€50K forgotten value at resale) - **No camera/monitoring integration** (owners want "is my boat OK?" reassurance) - **No maintenance log** (when was last engine service? upcoming work alerts?) @@ -148,38 +150,64 @@ Each agent MUST: **Deliverable:** Search UX spec with visual mockups (avoid long lists!) -### Agent 8: Notification System Design +### Agent 8: WhatsApp Group Integration (CRITICAL - NEW!) **AGENT ID:** S2-H08 ** -**Design:** -- Email notification service -- SMS alerts (warranty expiration, document missing) -- In-app notification center -- Push notifications (PWA) +**Research + Design:** +- WhatsApp Business API integration (boat-specific group chat) +- Group membership: Owner, Riviera after-sales, captain, stakeholders + NaviDocs AI agent +- AI agent capabilities: + - **Log all chats** (IF.TTT audit trail: who said what, when, with citations) + - **Answer questions** ("Where's the tender warranty?" → NaviDocs searches, responds with doc link) + - **Post updates** ("Maintenance service due in 2 weeks" → proactive reminders) + - **Document versioning notifications** ("New manual uploaded for autopilot") +- Technical architecture: + - Webhook from WhatsApp → NaviDocs tenant API + - AI agent response generation (Claude API integration) + - Message history storage (IF.TTT compliance: ed25519 signatures, SHA-256 hashes) + - Multi-tenant isolation (each boat's chat stays separate) +- Use cases: + - Owner: "When was last engine service?" → AI responds with maintenance log data + - After-sales: "@NaviDocs upload warranty for new tender" → AI confirms, creates inventory entry + - Captain: "Bilge pump alarm triggered" → AI logs incident, suggests mechanic contact -**Deliverable:** Notification architecture with templates +**Deliverable:** WhatsApp integration architecture with AI agent spec + IF.TTT compliance checklist -### Agent 9: Database Migration Plan +### Agent 9: Document Tracking & Versioning (CORE VALUE PROP) **AGENT ID:** S2-H09 ** -**Create:** -- Migration scripts for warranty tracking -- Charter mode fields (flag, crew, safety) -- Expiration tracking tables -- Collaboration features schema +**Design:** +- Document versioning system (git-style: track changes, rollback, history) +- IF.TTT compliance: Every doc upload/edit gets: + - Ed25519 signature (who uploaded) + - SHA-256 content hash (tamper detection) + - Timestamp (when) + - Citation ID (if://doc/navidocs/boat-123/warranty-tender-v2) +- Document categories: warranties, manuals, service records, invoices, certificates, insurance +- Versioning metadata: version number, change description, changed_by, changed_at +- Search integration: Meilisearch indexes doc content (OCR text + metadata) +- Mobile-first: owners upload photos of receipts/manuals → OCR extraction → structured data -**Deliverable:** SQL migrations + rollback scripts +**Deliverable:** Document versioning spec with IF.TTT traceability architecture -### Agent 10: Sprint Planning +### Agent 10: Architecture Synthesis & Sprint Planning **AGENT ID:** S2-H10 ** -**Compile:** -- Week 1-4 task breakdown -- Dependencies mapped (e.g., DB migrations before API work) -- Acceptance criteria per feature -- Testing strategy (unit, integration, E2E) +**Wait for:** Agents 1-9 to complete -**Deliverable:** 4-week sprint plan with Gantt chart +**Compile:** +- Integration architecture (all 9 features working together) +- Week 1-4 task breakdown with priorities: + - **Week 1:** Document tracking/versioning + WhatsApp integration (core value props) + - **Week 2:** Inventory tracking + maintenance log + - **Week 3:** Camera integration + contact management + - **Week 4:** Expense tracking + search UX + AI agent training +- Dependencies mapped (e.g., WhatsApp AI agent needs document search working first) +- Acceptance criteria per feature +- Testing strategy (unit, integration, E2E + IF.TTT audit validation) +- IF.TTT dogfooding checklist (we're using our own traceability standards) + +**Deliverable:** Complete architecture document + 4-week sprint plan with IF.TTT compliance --- diff --git a/NAVIDOCS-WELCOME-ONBOARDING.md b/NAVIDOCS-WELCOME-ONBOARDING.md index c3e3108..4d8ac1c 100644 --- a/NAVIDOCS-WELCOME-ONBOARDING.md +++ b/NAVIDOCS-WELCOME-ONBOARDING.md @@ -44,27 +44,47 @@ Riviera Plaisance Euro Voiles sells 150+ recreational motor boats per year (Jean - **Passive documentation vaults** that owners ignore until emergency/sale - **No daily engagement features** (cameras, maintenance logs, crew contacts) - **No impeccable search** for finding boat equipment/docs quickly +- **After-sales communication scattered** across WhatsApp, email, phone calls with no audit trail ### **The Solution** -**NaviDocs:** A sticky daily-use boat management app that happens to have perfect documentation when you need it. +**NaviDocs:** A sticky daily-use boat management app with document tracking/versioning that happens to integrate seamlessly into Riviera Plaisance's after-sales workflow. **Key Features:** -1. **Inventory tracking** - prevent forgotten value at resale -2. **Camera monitoring** - "is my boat OK?" -3. **Maintenance log** - service reminders -4. **Contact management** - one-tap call marina/mechanic -5. **Expense tracking** - annual spend visibility -6. **Impeccable search** - structured results, NO long lists +1. **Document tracking & versioning** (core value prop) - warranties, manuals, service records with IF.TTT traceability +2. **Inventory tracking** - prevent forgotten value at resale +3. **WhatsApp group integration** - boat-specific chat with owner, after-sales, captain, stakeholders +4. **AI agent in group chat** - answers questions, posts updates, logs conversations (IF.TTT compliance) +5. **Camera monitoring** - "is my boat OK?" +6. **Maintenance log** - service reminders +7. **Contact management** - one-tap call marina/mechanic +8. **Expense tracking** - annual spend visibility +9. **Impeccable search** - structured results, NO long lists ### **Your Mission** -Build the **intelligence dossier** that convinces Riviera Plaisance (specifically: Sylvain, the sales agent) to **include NaviDocs with every boat sale**. +Build the **intelligence dossier** that makes NaviDocs so compelling that Riviera Plaisance (specifically: Sylvain, the sales agent) **includes NaviDocs by default with every boat sale**. + +**The Sales Process Context:** +- Sylvain sits with buyer listing boat options +- Buyer asks: "Do I really need that?" +- Sylvain decides: "Yes" or "No" or "You should have it by default" +- **Goal:** NaviDocs becomes a "you should have it by default" item + +**The After-Sales Workflow:** +- When boat is sold → WhatsApp group created for that boat +- Group members: Owner, Riviera after-sales, captain, other stakeholders +- **NaviDocs tenant joins the group** as AI agent: + - Logs all chats (IF.TTT audit trail) + - Answers questions ("Where's the tender warranty?") + - Posts updates ("Maintenance service due in 2 weeks") + - Document versioning notifications ("New manual uploaded for autopilot") **Why this matters:** -- **Business impact:** 150+ boats/year × €15/month = €27K annual recurring revenue (starter case) +- **Business impact:** 150+ boats/year × €15/month × 12 months = €27K ARR (Year 1) - **Owner value:** €30K-€50K saved over 10 years through inventory tracking -- **Broker value:** Sticky engagement = higher customer retention +- **Broker value:** After-sales engagement reduces support burden + IF.TTT compliance for warranty claims +- **IF.TTT dogfooding:** We're using our own traceability standards in production ---