Commit graph

4 commits

Author SHA1 Message Date
Danny Stocker
eeab4b2224 Remove external infrafabric path dependencies from docs
Changed references from absolute paths (/home/setup/infrafabric/) to optional GitHub repo links.

Cloud sessions only need navidocs repo - all required files are included.
InfraFabric repo is optional reference material only.

Generated with Claude Code
2025-11-13 02:52:51 +01:00
Danny Stocker
af0f38af80 Add receipt/invoice upload + multi-user accounting module (Spliit fork)
Agent 6 (Session 2) Updated:
- Receipt/invoice photo upload with OCR (Tesseract + Google Vision)
- Auto-extract: amount, vendor, date, VAT, category
- Multi-user expense tracking:
  - Owner: cash, card, bank (marina fees, insurance, major upgrades)
  - Captain: boat card, boat cash, personal cash to reimburse
  - Reimbursement workflow: submit → OCR → owner approve → mark paid
- Open-source accounting module research:
  - Spliit (MIT, 2.3K stars) - receipt scanning, expense splitting, PWA
  - SplitPro (MIT, 916 stars) - BigInt precision, multi-currency
  - Medici (MIT, 330 stars) - double-entry GL, hierarchical accounts
- WhatsApp integration: '@NaviDocs log expense €45 fuel' → AI creates entry
- IF.TTT compliance: SHA-256 hash + ed25519 signature for receipts
- Export to Excel/CSV for accountant (tax deduction reports)

Research Report: YACHT_ACCOUNTING_RESEARCH.md (15+ repos analyzed)

Recommended: Fork Spliit (MIT) + customize for boat workflows
- Boat card vs personal cash tracking
- Captain reimbursement approval flow
- Multi-currency (€, $, £)
- Mobile-first PWA

🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-13 02:27:32 +01:00
Danny Stocker
c815ef8629 CRITICAL MISSION CORRECTION: NaviDocs makes Riviera include it by default, not helps them sell boats
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 <noreply@anthropic.com>
2025-11-13 02:22:59 +01:00
Danny Stocker
c9c99db138 Add comprehensive onboarding and master launch prompt for all 5 cloud sessions
- NAVIDOCS-WELCOME-ONBOARDING.md: Complete onboarding guide with mission context, role descriptions, IF.bus protocol, success criteria, Wu Lun philosophy
- MASTER-LAUNCH-PROMPT.md: Updated with welcome message and onboarding reference
- Sessions poll navidocs-cloud-coordination branch for AUTONOMOUS-COORDINATION-STATUS.md
- Based on InfraFabric S² multi-swarm coordination (3,563x faster)

🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-13 02:13:53 +01:00