Commit graph

9 commits

Author SHA1 Message Date
Danny Stocker
bdf4e10e9d Sessions 2 & 4: Add helper agents to assist Sessions 1 & 3
**Session 2 Helper Agents (Phase 1 - Start Immediately):**
- Agent 0A: Technical Validation Assistant (verify competitor APIs, check feasibility)
- Agent 0B: Citation Automation (SHA-256 hash generation, URL verification)
- Agent 0C: Web Scraping Assistant (structured data extraction from competitor sites)
- Agent 0D: ROI Calculator Backend (build framework before Session 1 data arrives)

**Session 4 Helper Agents (Phase 1 - Start Immediately):**
- Agent 0A: Research Coordination Dashboard (track Session 1 agent progress in real-time)
- Agent 0B: Citation Quality Checker (pre-validate citations before Session 5)
- Agent 0C: Demo Script Structure (create template with placeholders for Session 1 data)
- Agent 0D: Cross-Session Dependency Tracker (visual dependency graph, critical path analysis)

**Status Updates:**
- Session 2: 🟡 READY → 🟢 ACTIVE (Helper) - 4/15 agents
- Session 4:  COMPLETE → 🟢 ACTIVE (Helper) - 4/14 agents

**InfraFabric S² Pattern:** Transform idle sessions into active helpers, eliminating wait time and accelerating overall project completion.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-13 03:12:59 +01:00
Danny Stocker
cb7ad641cd Fix absolute paths for cloud sessions (no shared filesystem)
**Path Fixes for Multi-Machine Deployment:**

Session 2:
- Changed `/home/setup/navidocs/ARCHITECTURE_INTEGRATION_ANALYSIS.md` → `ARCHITECTURE_INTEGRATION_ANALYSIS.md`
- Changed `/home/setup/navidocs/YACHT_ACCOUNTING_RESEARCH.md` → `YACHT_ACCOUNTING_RESEARCH.md`

Session 5:
- Changed `/home/setup/infrafabric/schemas/citation/v1.0.schema.json` → `schemas/citation/v1.0.schema.json`
- Copied citation schema from infrafabric repo into navidocs repo (no external dependency)
- Fixed example citation paths (absolute → relative)

**Why This Matters:**
Cloud sessions run on separate machines with NO shared filesystem. All paths must be:
1. Relative to git repo root (e.g., `./file.md` not `/home/setup/navidocs/file.md`)
2. Files must exist IN the navidocs repo (not external repos)

**Test Command:**
```bash
git clone https://github.com/dannystocker/navidocs.git
cd navidocs
git checkout navidocs-cloud-coordination
# All referenced files now accessible via relative paths
```

Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-13 02:52:07 +01:00
Danny Stocker
894df54f7d Add VAT/tax tracking + multi-calendar system to NaviDocs
**Session 2 Updates (Agent 3A + Agent 7A):**
- Agent 3A: VAT/Tax Jurisdiction Tracking & Compliance Reminders
  - Non-VAT boat EU exit requirements (FR/ES/IT/global jurisdictions)
  - Jurisdiction rules engine (exit frequency, grace periods, penalties)
  - Compliance dashboard widget with 60/30/14/7 day reminders
  - Multi-jurisdiction support (boat moves between FR/ES/IT marinas)
  - Compliance history with IF.TTT audit trail (customs stamp scans)
  - Integration with calendar system (exit deadlines on Work Roadmap)

- Agent 7A: Multi-Calendar System (4 calendar types, unified UI)
  - Service Calendar (maintenance due dates from Agent 3)
  - Warranty Calendar (expiration dates from Agent 2 inventory)
  - Owner Onboard Calendar (owner trip dates, engagement tracking)
  - Work Roadmap Calendar (planned work + budget signoff workflow)
  - Smart notifications (context-aware: service + owner + fuel alerts)
  - Conflict detection (work vs owner, service vs warranty, exit vs trip)
  - Budget signoff workflow (proposed → approved → complete with actual cost)

**Stakeholder Dashboard Updates:**
- Owner dashboard: Added VAT status widget + calendar widget (this week's events)
- Updated all dashboards with calendar integration
- Section 9: VAT/Tax Jurisdiction Tracking (full spec with wireframes)
- Section 10: Multi-Calendar System (full spec with conflict detection examples)

**Integration Points:**
- Calendar feeds from: Maintenance log, Inventory, VAT compliance, Accounting
- VAT exit deadlines appear on Work Roadmap Calendar (high priority)
- Budget vs actual tracking (Work Roadmap ← Accounting module)
- Owner engagement tracking (Owner trips → After-sales dashboard)

**Key Features:**
- Prevent €300K+ VAT liability (exit deadline reminders)
- Prevent lost warranty claims (expiration alerts 90/60/30 days before)
- Prevent boat unpreparedness (captain sees owner arrival 3+ days ahead)
- Budget transparency (planned €15K vs actual €17K with approval workflow)

Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-13 02:39:22 +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
da1263d1b3 Add IF.bus intra-agent communication protocol to all 5 cloud sessions
- Added IFMessage schema with FIPA-ACL performatives
- Session-specific communication flows (distributed intelligence, peer review, adversarial testing, sequential handoffs, consensus building)
- Automatic conflict detection (>20% variance triggers ESCALATE)
- Multi-source verification (IF.TTT ≥2 sources requirement)
- Token cost tracking (IF.optimise integration)
- PARALLEL_LAUNCH_STRATEGY.md for simultaneous session deployment
- SWARM_COMMUNICATION_PROTOCOL.md comprehensive protocol docs

Based on InfraFabric S² multi-swarm coordination (3,563x faster than git polling)

🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-13 02:03:24 +01:00
Danny Stocker
a5ffcb5769 Add agent identity & check-in protocol to all 5 sessions
Each session now has:
- Agent self-identification system (S1-H01 through S5-H10)
- Check-in protocol (agents announce identity at start)
- Task reference system (agents find instructions by number)
- Dependency tracking (parallel vs sequential execution)

Note: Prestige yachts sell for €1.5M (not €480K) - needs price correction in Session 1

🤖 Generated with Claude Code
2025-11-13 01:27:48 +01:00
Danny Stocker
7787a57ff8 Update Sessions 1-2: pivot to recreational boats + sticky features
Critical market corrections:
- Target: Jeanneau Prestige 40-50ft (€250K-€480K), NOT mega yachts
- Riviera Plaisance: 150+ boats/year, 20,500+ customers
- Owner profile: weekend users (20-40 days/year), NOT crew-managed

New feature priority (sticky daily engagement):
1. Inventory tracking - prevent €15K-€50K forgotten value at resale
2. Camera/monitoring - 'is my boat OK?' peace of mind
3. Maintenance log - service reminders, expense tracking
4. Contact management - one-tap call to marina/mechanic
5. Expense tracking - annual spend visibility
6. Impeccable search - structured faceted results, NO long lists

Documentation features now secondary to daily engagement.

🤖 Generated with Claude Code
2025-11-13 00:57:13 +01:00
Danny Stocker
760fedc138 Add InfraFabric S2 multi-swarm integration plan for yacht sales intelligence
Created 5 cloud session starter prompts applying Epic V4 + S2 methodology:
- Session 1: Market research (10 Haiku agents, $15 budget)
- Session 2: Technical architecture (10 Haiku agents, $20 budget)
- Session 3: UX/Sales enablement (10 Haiku agents, $15 budget)
- Session 4: Implementation planning (10 Haiku agents, $15 budget)
- Session 5: Evidence synthesis + Guardian Council vote (10 Haiku agents, $25 budget)

Total budget: $90 ($10 buffer) across 50 Haiku agents + 5 Sonnet coordinators

Integration plan leverages:
- IF.bus (event-driven architecture)
- IF.swarm (multi-agent orchestration)
- IF.optimise (49.3% validated token cost reduction)
- IF.guard (20-voice Guardian Council consensus)
- IF.TTT (medical-grade evidence with ≥2 sources per claim)

Objective: Prepare Riviera Plaisance yacht sales pitch + 4-week NaviDocs enhancement roadmap (warranty tracking, Home Assistant integration, sale workflow automation)

🤖 Generated with Claude Code (https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-13 00:43:27 +01:00