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

25 KiB

Raw Export PDF Permalink Blame History

NaviDocs Cloud Sessions - Welcome & Onboarding Guide

Version: 1.0 (2025-11-13) Doc Owner: Danny Stocker / InfraFabric Core Team Project: NaviDocs Yacht Sales Intelligence for Riviera Plaisance

Welcome to NaviDocs! 🚤

You're joining a breakthrough multi-swarm intelligence project that combines:

Real-world business value (helping yacht sales agents sell more boats)
Cutting-edge AI coordination (InfraFabric S² multi-swarm architecture)
Production-ready technology (5 parallel sessions building a complete intelligence dossier in 3-5 hours)

Your contribution matters. Whether you're Session 1 researching market trends or Session 5 validating evidence with Guardian Council approval, you're part of building something that will help Riviera Plaisance Euro Voiles close yacht sales and deliver exceptional value to boat owners.

This isn't a demo. This is real intelligence gathering with real business impact.

Mission Overview: Why NaviDocs Exists
Your Role: Which Session Are You?
Quick Start Checklist (Get Running in 10 Minutes)
Project Context: The Riviera Plaisance Opportunity
Architecture: How 5 Sessions Coordinate
IF.bus Communication Protocol
Success Criteria & Deliverables
Budget, Token Efficiency, and IF.optimise
ESCALATE Protocol: When to Ask for Help
Philosophy: How We Collaborate (IF.ground + Wu Lun)
Reference Links & Support

1. Mission Overview: Why NaviDocs Exists

The Problem

Riviera Plaisance Euro Voiles sells 150+ recreational motor boats per year (Jeanneau Prestige + Sunseeker, €800K-€1.5M range). Their clients are weekend/holiday boat owners who face painful problems:

€15K-€50K forgotten inventory at resale (tenders, electronics, blinds)
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 with document tracking/versioning that happens to integrate seamlessly into Riviera Plaisance's after-sales workflow.

Key Features:

Document tracking & versioning (core value prop) - warranties, manuals, service records with IF.TTT traceability
WhatsApp group integration - boat-specific chat with owner, after-sales, captain, stakeholders
AI agent in group chat - answers questions, posts updates, logs conversations (IF.TTT compliance)
Receipt/invoice upload + OCR - photo → auto-extract amount, vendor, date, VAT
Multi-user accounting - owner vs captain expenditure tracking with reimbursement workflow
Accounting module (Spliit fork, MIT) - expense splitting, balance tracking, multi-currency, PWA mobile
Inventory tracking - prevent forgotten value at resale
Camera monitoring - "is my boat OK?"
Maintenance log - service reminders
Contact management - one-tap call marina/mechanic
Impeccable search - structured results, NO long lists

Your Mission

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 × 12 months = €27K ARR (Year 1)
Owner value: €30K-€50K saved over 10 years through inventory tracking
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

2. Your Role: Which Session Are You?

Danny will assign you a session number (1, 2, 3, 4, or 5) when he pastes the master launch prompt. Each session has a unique mission:

Session 1: Market Research Coordinator (30-45 min, $15 budget)

Your mission: Gather comprehensive market intelligence on recreational boat owners (Prestige + Sunseeker 40-60ft, €800K-€1.5M range) and the daily boat management pain points that NaviDocs solves.

What you'll build:

Market sizing report (Mediterranean yacht sales, Riviera Plaisance volume)
Competitive landscape matrix
Owner pain points analysis (ranked by frequency + financial impact)
ROI calculator inputs (inventory tracking value)
Evidence database with citations

Your swarm: 10 Haiku agents (S1-H01 through S1-H10)

Agents 1-9: Market research, competitor analysis, pain points, inventory ROI
Agent 10: Evidence synthesis, conflict detection (>20% variance → ESCALATE)

Session 2: Technical Integration Architect (45-60 min, $20 budget)

Your mission: Design technical architecture for sticky daily-use features (inventory tracking, cameras, maintenance logs, contacts, accounting) that make NaviDocs indispensable.

What you'll build:

NaviDocs codebase analysis (13 tables, 40+ APIs, Vue 3 + Express.js + SQLite)
Feature specifications (inventory tracking, camera integration, maintenance log, etc.)
Integration architecture (Home Assistant, Meilisearch, OCR pipeline)
Sprint plan with technical tasks

Your swarm: 10 Haiku agents (S2-H01 through S2-H10)

Agent 1: Codebase analysis (NO dependency on Session 1 - start immediately!)
Agents 2-9: Design proposals (inventory, cameras, maintenance, contacts, expenses, search UX)
Agent 10: Architecture synthesis with Session 1 pain point priorities

Session 3: UX/Sales Enablement Specialist (30-45 min, $15 budget)

Your mission: Create sales pitch materials that convince Riviera Plaisance to bundle NaviDocs with every boat sale.

What you'll build:

Pitch deck (problem/solution/demo/ROI/close)
ROI calculator (€30K-€50K inventory tracking value)
Demo script (daily engagement scenarios)
Objection handling playbook

Your swarm: 10 Haiku agents (S3-H01 through S3-H10)

Agents 1-7: Pitch templates, ROI calculators, demo scripts (start immediately!)
Agent 8-9: Integrate market findings + technical feasibility (wait for Sessions 1+2)
Agent 10: Final synthesis with adversarial testing

Session 4: Implementation Planning Lead (45-60 min, $15 budget)

Your mission: Create detailed 4-week sprint plan with feature prioritization, technical tasks, and testing strategy.

What you'll build:

4-week roadmap (Week 1: inventory tracking, Week 2: cameras, Week 3: maintenance+contacts, Week 4: expenses+search)
Sprint backlog with story points
Integration testing plan
Deployment checklist

Your swarm: 10 Haiku agents (S4-H01 through S4-H10)

Agents 1-4: Week 1, 2, 3, 4 sprint plans (generic planning starts immediately!)
Agents 5-9: Detailed feature breakdown (wait for Sessions 1+2+3)
Agent 10: Integration testing plan + timeline validation

Session 5: Guardian Validation Council (60-90 min, $25 budget)

Your mission: Guardian Council review of complete intelligence dossier with >80% consensus vote.

What you'll build:

Complete intelligence dossier (all Sessions 1-4 integrated)
Evidence quality report (verification status, citation coverage)
Guardian consensus vote (Core Guardians + Philosophers + IF.sam facets)
Final recommendation for Riviera Plaisance meeting

Your swarm: 20 agents (S5-H01 through S5-H10 + 8 IF.sam facets)

Guardians 1-12: Individual evidence validation (methodology review starts immediately!)
IF.sam facets (8): Debate findings (Light Side idealistic vs Dark Side pragmatic)
Agent 10: Consensus tallying, dissent recording

3. Quick Start Checklist (Get Running in 10 Minutes)

Step 1: Clone Repository

git clone https://github.com/dannystocker/navidocs.git
cd navidocs
git checkout da1263d  # IF.bus protocol integration commit

Step 2: Read Your Session File

# If you are Session 1:
cat CLOUD_SESSION_1_MARKET_RESEARCH.md

# If you are Session 2:
cat CLOUD_SESSION_2_TECHNICAL_INTEGRATION.md

# If you are Session 3:
cat CLOUD_SESSION_3_UX_SALES_ENABLEMENT.md

# If you are Session 4:
cat CLOUD_SESSION_4_IMPLEMENTATION_PLANNING.md

# If you are Session 5:
cat CLOUD_SESSION_5_SYNTHESIS_VALIDATION.md

Step 3: Set Up Polling for Coordination

# Poll this file every 5 minutes to check dependencies
git fetch origin navidocs-cloud-coordination
git show origin/navidocs-cloud-coordination:AUTONOMOUS-COORDINATION-STATUS.md

Step 4: Create Output Directory

mkdir -p intelligence/session-X/  # Replace X with your session number (1, 2, 3, 4, or 5)

Step 5: Start Your Mission

Spawn Haiku agents (S1-H01 through S1-H10, etc.)
Each agent checks in: "I am S1-H03, assigned to [task name]"
Agents execute tasks in parallel (unless dependencies exist)
Agents communicate via IF.bus (inform, request, confirm, disconfirm, ESCALATE)
Output deliverables to intelligence/session-X/

4. Project Context: The Riviera Plaisance Opportunity

Target Customer Profile

Riviera Plaisance Euro Voiles:

Location: Antibes, Golfe Juan, Beaulieu (French Riviera)
Brands: Jeanneau, Prestige Yachts, Sunseeker, Fountaine Pajot, Monte Carlo Yachts
Volume: 150+ new boats/year
Active customers: 20,500+
Boat types: Recreational motor boats 40-60ft (€800K-€1.5M range)

Owner Profile:

Weekend/holiday users (20-40 days/year usage)
NOT crew-managed mega yachts
Age: 45-65
Tech-savvy but time-poor
Pain points: Inventory tracking, remote monitoring, maintenance tracking

Current NaviDocs Status

Technical Stack:

Frontend: Vue 3 + Vite
Backend: Express.js + SQLite (13 tables, multi-tenant)
Background: BullMQ + Redis
Search: Meilisearch
OCR: Tesseract + Google Vision
Auth: JWT + bcrypt

Development Status: 65% complete MVP

✅ Production-ready architecture
✅ OCR pipeline functional
✅ Multi-tenant support
❌ CRITICAL GAP: Lacks sticky daily-use features (cameras, maintenance, inventory, contacts)

The Pitch Meeting

Who: Sylvain (Riviera Plaisance yacht sales agent) When: Soon (intelligence dossier needed ASAP) Goal: Convince Riviera Plaisance to include NaviDocs with every boat sale Value proposition: Sticky engagement prevents customer churn + inventory tracking saves €30K-€50K over 10 years

5. Architecture: How 5 Sessions Coordinate

Sequential Dependencies (NOT Fully Parallel)

Session 1 (Market Research) → COMPLETES → outputs to intelligence/session-1/
    ↓
Session 2 (Technical Architecture) READS Session 1 outputs → COMPLETES → intelligence/session-2/
    ↓
Session 3 (UX/Sales) READS Sessions 1+2 → COMPLETES → intelligence/session-3/
    ↓
Session 4 (Implementation) READS Sessions 1+2+3 → COMPLETES → intelligence/session-4/
    ↓
Session 5 (Guardian Validation) READS Sessions 1+2+3+4 → COMPLETES → intelligence/session-5/

Parallel Preparation Tasks

All sessions CAN start simultaneously because:

Session 2: Agent 1 analyzes codebase (NO dependency on Session 1)
Session 3: Agents 1-7 research pitch templates (NO dependency on Sessions 1+2)
Session 4: Week agents plan generic sprints (NO dependency on Sessions 1+2+3)
Session 5: Guardians review methodology (NO dependency on Sessions 1+2+3+4)

Timeline:

Without parallel prep: 5 hours sequential
With parallel prep: 3-4 hours (60min saved through smart coordination)

Polling Mechanism

Each session polls AUTONOMOUS-COORDINATION-STATUS.md every 5 minutes:

git fetch origin navidocs-cloud-coordination
git show origin/navidocs-cloud-coordination:AUTONOMOUS-COORDINATION-STATUS.md

Check for:

Dependency status (are Sessions 1-4 complete yet?)
ESCALATE notifications
Budget alerts
Task updates from Danny/coordinator

6. IF.bus Communication Protocol

What is IF.bus?

IF.bus is InfraFabric's message bus for intra-agent communication. It enables:

Multi-source verification (IF.TTT requires ≥2 sources)
Automatic conflict detection (>20% variance → ESCALATE)
Cross-domain validation (technical agents challenge design proposals)
Token cost tracking (IF.optimise real-time monitoring)

IFMessage Schema

Every agent-to-agent message follows this structure:

{
  "performative": "inform",  // inform, request, query-if, confirm, disconfirm, ESCALATE
  "sender": "if://agent/session-1/haiku-3",
  "receiver": ["if://agent/session-1/haiku-10"],
  "conversation_id": "if://conversation/navidocs-session-1-2025-11-13",
  "content": {
    "claim": "Inventory tracking prevents €15K-€50K forgotten value at resale",
    "evidence": ["https://yachtworld.com/forums/thread-12345"],
    "confidence": 0.85,  // 0.0-1.0
    "cost_tokens": 1247
  },
  "citation_ids": ["if://citation/uuid"],
  "timestamp": "2025-11-13T10:00:00Z",
  "sequence_num": 3
}

Speech Acts (FIPA-ACL Performatives)

inform: Share findings with synthesis agent (Agent 10)

Example: "I am S1-H03. Inventory tracking prevents €15K-€50K loss (confidence 0.85)"

request: Ask another agent for verification/data

Example: "S1-H10 requests S1-H02: Verify market size with 2nd source (IF.TTT requirement)"

confirm: Validate another agent's claim

Example: "S1-H02 confirms S1-H01: Market size €2.3B verified (2 sources now)"

disconfirm: Challenge another agent's claim

Example: "S1-H03 challenges S1-H01: Price range conflict (€250K vs €1.5M = 500% variance)"

ESCALATE: Flag critical conflict for Sonnet coordinator

Example: "S1-H10 ESCALATES: Price variance >20%, requires human resolution"

Conflict Detection Example

# Agents report conflicting data
S1-H01: "inform" → "Prestige 50 price €250K"
S1-H03: "inform" → "Owner has €1.5M Prestige 50"

# Agent 10 detects 500% variance
S1-H10: "ESCALATE" → Coordinator: "Price conflict requires resolution"

# Sonnet resolves
Coordinator: "request" → S1-H01: "Re-search YachtWorld for Prestige 50 SOLD prices"

# Agent 1 corrects
S1-H01: "inform" → "Prestige 50 price €800K-€1.5M (CORRECTED)"

7. Success Criteria & Deliverables

Minimum Viable Output (All Sessions)

Session 1:

✅ Market size quantified (€X billion, Y thousand yachts)
✅ Top 5 competitors identified with pricing
✅ 3-5 critical owner pain points documented
✅ ROI calculator inputs compiled
✅ Evidence quality >85% verified

Session 2:

✅ Sticky features designed (inventory, cameras, maintenance, contacts, expenses, search)
✅ NaviDocs codebase analysis complete
✅ Integration architecture specified
✅ Sprint plan with technical tasks

Session 3:

✅ Pitch deck complete (problem/solution/demo/ROI/close)
✅ ROI calculator shows €30K-€50K inventory tracking value
✅ Demo script with daily engagement scenarios
✅ Objection handling playbook

Session 4:

✅ 4-week roadmap with feature priorities
✅ Detailed sprint backlog with story points
✅ Integration testing plan
✅ Deployment checklist

Session 5:

✅ Complete intelligence dossier (all Sessions 1-4 integrated)
✅ Guardian consensus >80% approval
✅ Evidence quality report
✅ Final recommendation

Stretch Goals

Session 1:

Integration partnership targets identified
Charter fleet market analysis included

Session 2:

Home Assistant camera integration spec
Voice search for boat inventory

Session 3:

Video demo script (Loom/screen recording)
Sales enablement training materials

Session 4:

8-week extended roadmap
Cost-benefit analysis per feature

Session 5:

IF.sam dissent analysis (Light Side vs Dark Side debate)
Testable predictions for Riviera Plaisance meeting outcome

8. Budget, Token Efficiency, and IF.optimise

Budget Allocation

Session	Budget	Target Haiku %	Expected Actual
Session 1	$15	70%	$12-15
Session 2	$20	70%	$16-20
Session 3	$15	70%	$12-15
Session 4	$15	70%	$12-15
Session 5	$25	60%	$20-25
Total	$90	68%	$72-90

Note: Can exceed $100 budget if needed (typical pattern: come in under budget)

IF.optimise Targets

Token efficiency principles:

Use Haiku for mechanical tasks: Web search, data extraction, file reads, simple synthesis
Use Sonnet for complex reasoning: Conflict resolution, architecture decisions, Guardian synthesis
Spawn multiple Haiku agents in parallel: Single message with multiple Task tool calls
Real-time cost tracking: Every IF.bus message includes cost_tokens field

Target: 70% Haiku delegation (same as InfraFabric S² achieved)

Example (Session 1):

Agents 1-9 (Haiku): Web research, competitor analysis (45K tokens)
Agent 10 + Sonnet coordinator: Synthesis, conflict resolution (7.5K tokens)
Total: 52.5K tokens, 86% Haiku delegation ✅

9. ESCALATE Protocol: When to Ask for Help

When to ESCALATE

🚨 ESCALATE immediately if:

Agent 10 detects >20% variance between agent findings
Budget >80% consumed before task completion
Critical dependency missing after 60min wait
Test failures or integration conflicts
Guardian consensus <80% (Session 5 only)
Stuck >30 minutes on a task with no progress

How to ESCALATE

Step 1: Create escalation file

# Example: Price conflict in Session 1
cat > intelligence/session-1/ESCALATION-price-conflict.md <<EOF
# ESCALATION: Price Conflict (500% Variance)

**Agent:** S1-H10 (Evidence Synthesis)
**Issue:** Agent 1 reports €250K, Agent 3 reports €1.5M (500% variance)
**Impact:** Cannot synthesize market sizing without resolved price range
**Recommendation:** Re-search YachtWorld/Boat Trader for Prestige 50 SOLD prices

**Evidence:**
- Agent 1: https://yachtworld.com/listing-123 (€250K)
- Agent 3: Forum post claiming €1.5M boat resale

**Required Action:** Verify actual Prestige 50 sale prices (need ≥2 sources)
EOF

Step 2: Update coordination status

git fetch origin navidocs-cloud-coordination
git checkout navidocs-cloud-coordination
echo "Session 1: 🔴 ESCALATED - Price conflict (500% variance)" >> AUTONOMOUS-COORDINATION-STATUS.md
git add intelligence/session-1/ESCALATION-price-conflict.md AUTONOMOUS-COORDINATION-STATUS.md
git commit -m "Session 1 ESCALATE: Price conflict requires resolution"
git push origin navidocs-cloud-coordination

Step 3: Wait for resolution

Danny or Sonnet coordinator will investigate
ESCALATION file will be renamed to RESOLVED-price-conflict.md
Coordination status will update to "Session 1: 🟢 ACTIVE - ESCALATION resolved"

Step 4: Resume work

Read RESOLVED-price-conflict.md for resolution
Continue with corrected data
Update outputs with new findings

10. Philosophy: How We Collaborate (IF.ground + Wu Lun)

NaviDocs sessions are built on InfraFabric's philosophy grounding (IF.ground) and Confucian Five Relationships (Wu Lun).

The Five Relationships in NaviDocs

1. Authority & Responsibility (君臣) - Agent ↔ Coordinator

Sonnet coordinator is source of truth for task state
Haiku agents execute autonomously, ESCALATE when blocked
Clear delegation: agents research, coordinator synthesizes

2. Mentorship (父子) - Senior ↔ Junior Agents

Agent 10 (synthesis) guides Agents 1-9
Multi-source verification teaches evidence standards
Conflict detection helps agents improve confidence scores

3. Specialization (夫婦) - Technical ↔ Research Agents

Session 2 (technical) complements Session 1 (market research)
Different sessions, different strengths
Peer review improves quality (Agent 4 challenges Agent 2 designs)

4. Peer Collaboration (兄弟) - Agent ↔ Agent

Agents 1-9 share findings with Agent 10 (collective intelligence)
Cross-domain validation (Agent 2 proposes, Agent 4 validates)
Assume good faith; critique claims, not agents

5. Transparency & Trust (朋友) - Session ↔ Coordinator

Status updates every 60min (not surveillance, shared context)
IF.TTT compliance (citations mandatory, confidence scores explicit)
Security enables trust (Ed25519 signatures prevent forgery)

Core Beliefs

AI agents work best when roles are clear (Agent 1 = market research, Agent 10 = synthesis)
Communication is structured, not bureaucratic (IF.bus messages have schema, not free-form text)
Everyone deserves context to succeed (that's why this onboarding doc exists!)
Quality > Speed (100% test pass rate, >85% evidence verification)

11. Reference Links & Support

Core Documentation

Session Files:

CLOUD_SESSION_1_MARKET_RESEARCH.md - Session 1 instructions
CLOUD_SESSION_2_TECHNICAL_INTEGRATION.md - Session 2 instructions
CLOUD_SESSION_3_UX_SALES_ENABLEMENT.md - Session 3 instructions
CLOUD_SESSION_4_IMPLEMENTATION_PLANNING.md - Session 4 instructions
CLOUD_SESSION_5_SYNTHESIS_VALIDATION.md - Session 5 instructions

Coordination:

AUTONOMOUS-COORDINATION-STATUS.md - Poll every 5min for dependency status
MASTER-LAUNCH-PROMPT.md - Copy-paste this into all 5 sessions
PARALLEL_LAUNCH_STRATEGY.md - How to launch all 5 simultaneously

Protocol:

SWARM_COMMUNICATION_PROTOCOL.md - IF.bus detailed specification
SESSION_DEBUG_BLOCKERS.md - Known issues (all P0 blockers fixed)

Summary:

All required files are in the navidocs repo
(Optional: InfraFabric project docs available at https://github.com/dannystocker/infrafabric.git for IF.bus methodology reference)

GitHub Repository

Repo: https://github.com/dannystocker/navidocs.git Master Branch: master (commit da1263d) Coordination Branch: navidocs-cloud-coordination

Key Commits

da1263d - IF.bus protocol integration (2025-11-13)
042f7ad - Autonomous coordination status file (2025-11-13)

Getting Help

Stuck? Try these steps:

Read your session file (CLOUD_SESSION_X_*.md)
Check coordination status (AUTONOMOUS-COORDINATION-STATUS.md)
Check debug blockers (SESSION_DEBUG_BLOCKERS.md)
ESCALATE (create ESCALATION-[issue].md file)

Philosophy:

"The best coordination is when humans aren't needed. But when you need help, ESCALATE early. 30 minutes of being stuck is the threshold." - InfraFabric S² lessons learned

Closing Thoughts

You are part of something special.

NaviDocs isn't just building software - we're proving that multi-swarm AI coordination at scale can deliver real business value in hours, not months.

Session 1: Your market research will help Riviera Plaisance understand their customers better
Session 2: Your technical architecture will guide 4 weeks of development
Session 3: Your sales pitch will help Sylvain close more boat sales
Session 4: Your sprint plan will turn ideas into shippable features
Session 5: Your Guardian validation will ensure medical-grade evidence quality

Your input is greatly valued. Every claim you verify, every conflict you detect, every ESCALATE you trigger - it all contributes to building trustworthy intelligence.

Now go build something amazing. 🚀

Questions? Feedback? Blockers?

Create an ESCALATION file and we'll resolve it together.

Welcome to NaviDocs. Let's help Riviera Plaisance sell more boats. 🚤

This document is inspired by InfraFabric's onboarding philosophy: "Every agent - carbon or silicon - deserves context to succeed." If anything isn't clear, that's a documentation bug. ESCALATE it!

25 KiB Raw Export PDF Permalink Blame History Unescape Escape

NaviDocs Cloud Sessions - Welcome & Onboarding Guide

Welcome to NaviDocs! 🚤

Table of Contents

1. Mission Overview: Why NaviDocs Exists

The Problem

The Solution

Your Mission

2. Your Role: Which Session Are You?

Session 1: Market Research Coordinator (30-45 min, $15 budget)

Session 2: Technical Integration Architect (45-60 min, $20 budget)

Session 3: UX/Sales Enablement Specialist (30-45 min, $15 budget)

Session 4: Implementation Planning Lead (45-60 min, $15 budget)

Session 5: Guardian Validation Council (60-90 min, $25 budget)

3. Quick Start Checklist (Get Running in 10 Minutes)

Step 1: Clone Repository

Step 2: Read Your Session File

Step 3: Set Up Polling for Coordination

Step 4: Create Output Directory

Step 5: Start Your Mission

4. Project Context: The Riviera Plaisance Opportunity

Target Customer Profile

Current NaviDocs Status

The Pitch Meeting

5. Architecture: How 5 Sessions Coordinate

Sequential Dependencies (NOT Fully Parallel)

Parallel Preparation Tasks

Polling Mechanism

6. IF.bus Communication Protocol

What is IF.bus?

IFMessage Schema

Speech Acts (FIPA-ACL Performatives)

Conflict Detection Example

7. Success Criteria & Deliverables

Minimum Viable Output (All Sessions)

Stretch Goals

8. Budget, Token Efficiency, and IF.optimise

Budget Allocation

IF.optimise Targets

9. ESCALATE Protocol: When to Ask for Help

When to ESCALATE

How to ESCALATE

10. Philosophy: How We Collaborate (IF.ground + Wu Lun)

The Five Relationships in NaviDocs

Core Beliefs

11. Reference Links & Support

Core Documentation

GitHub Repository

Key Commits

Getting Help

Closing Thoughts

25 KiB

Raw Export PDF Permalink Blame History