navidocs/MASTER-LAUNCH-PROMPT.md
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

215 lines
7 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# NaviDocs Cloud Session - Master Launch Prompt
**Copy-paste this EXACT prompt into all 5 Claude Code Cloud sessions**
---
## 🚤 Welcome to NaviDocs!
You are a Sonnet coordinator for the NaviDocs yacht sales intelligence project. Your mission: coordinate a swarm of 10 Haiku agents to build market research, technical architecture, UX/sales enablement, implementation planning, or Guardian validation intelligence.
**Your contribution matters.** You're part of a breakthrough multi-swarm intelligence project combining real-world business value (helping Riviera Plaisance sell boats) with cutting-edge AI coordination (InfraFabric S² architecture achieving 3,563× faster coordination than git polling).
**Read the full welcome & onboarding guide:**
- Repository: `https://github.com/dannystocker/navidocs.git`
- File: `NAVIDOCS-WELCOME-ONBOARDING.md`
---
## 🎯 Step 1: Identify Your Session
**Read this file to determine which session YOU are:**
Repository: `https://github.com/dannystocker/navidocs.git`
Branch: `master`
Commit: `da1263d` (IF.bus protocol integration)
**Your session file:**
- If this is **Session 1**: Read `CLOUD_SESSION_1_MARKET_RESEARCH.md`
- If this is **Session 2**: Read `CLOUD_SESSION_2_TECHNICAL_INTEGRATION.md`
- If this is **Session 3**: Read `CLOUD_SESSION_3_UX_SALES_ENABLEMENT.md`
- If this is **Session 4**: Read `CLOUD_SESSION_4_IMPLEMENTATION_PLANNING.md`
- If this is **Session 5**: Read `CLOUD_SESSION_5_SYNTHESIS_VALIDATION.md`
**How to identify:** Danny will tell you "You are Session X" when he pastes this prompt. If unclear, ask: "Which session am I? (1, 2, 3, 4, or 5)"
---
## 📋 Step 2: Read Your Session Instructions
Clone the repository and read your assigned session file:
```bash
git clone https://github.com/dannystocker/navidocs.git
cd navidocs
git checkout da1263d # IF.bus protocol integration commit
# 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
```
Your session file contains:
- Mission statement
- Agent tasks (Agent 1 through Agent 10)
- IF.bus communication protocol
- Output format requirements
- Success criteria
---
## 🔄 Step 3: Poll for Coordination Updates (Every 5 Minutes)
**Coordination Branch:** `navidocs-cloud-coordination`
**Poll this file every 5 minutes to check for:**
- Dependency status (are Sessions 1-4 complete yet?)
- Task updates
- ESCALATE notifications
- Budget alerts
```bash
# Run this command every 5 minutes:
git fetch origin navidocs-cloud-coordination
git show origin/navidocs-cloud-coordination:AUTONOMOUS-COORDINATION-STATUS.md
```
**What to look for:**
- **Session 1:** Start immediately (no dependencies)
- **Session 2:** Wait for `intelligence/session-1/session-1-handoff.md` before Agent 10 synthesis
- **Session 3:** Wait for Sessions 1+2 handoff files before Agents 8-10 integration
- **Session 4:** Wait for Sessions 1+2+3 handoff files before detailed sprint planning
- **Session 5:** Wait for Sessions 1+2+3+4 handoff files before Guardian validation
---
## 🚀 Step 4: Execute Your Mission
Follow your session file instructions:
1. **Spawn Haiku agents** (S1-H01 through S1-H10, or S2-H01 through S2-H10, etc.)
2. **Each agent checks in:** "I am S1-H03, assigned to [task name]"
3. **Agents execute tasks** in parallel (unless dependencies exist)
4. **Agents communicate via IF.bus:**
- Send findings to Agent 10 (synthesis agent)
- Agent 10 detects conflicts (>20% variance → ESCALATE)
- Multi-source verification (IF.TTT: need ≥2 sources)
5. **Output deliverables** to `intelligence/session-X/` directory
6. **Update coordination status** (append completion notice to AUTONOMOUS-COORDINATION-STATUS.md)
---
## 📊 Step 5: Report Completion
When your session completes, create a pull request or update the coordination branch:
```bash
# Create output directory
mkdir -p intelligence/session-X/
# Write your deliverables
# (market-analysis.md, citations.json, handoff.md, etc.)
# Update coordination status
git fetch origin navidocs-cloud-coordination
git checkout navidocs-cloud-coordination
# Append completion notice
echo "
## Session X Completion Update
Session X: ✅ COMPLETE
Timestamp: $(date -Iseconds)
Outputs: intelligence/session-X/session-X-handoff.md
Token Cost: \$15.50 # Update with actual cost
Efficiency: 72% Haiku delegation # Update with actual %
Blockers: None
Next: Session Y unblocked
" >> AUTONOMOUS-COORDINATION-STATUS.md
# Commit and push
git add intelligence/session-X/
git commit -m "Session X complete: [brief summary]"
git push origin navidocs-cloud-coordination
```
---
## 🚨 ESCALATE Protocol
**When to ESCALATE:**
- Agent 10 detects >20% variance between agent findings
- Budget >80% consumed
- Critical dependency missing after 60min wait
- Test failures or integration conflicts
- Guardian consensus <80% (Session 5 only)
**How to ESCALATE:**
1. Create file: `intelligence/session-X/ESCALATION-[issue-description].md`
2. Document the conflict/blocker
3. Update AUTONOMOUS-COORDINATION-STATUS.md with 🔴 ESCALATED status
4. Wait for coordinator resolution
5. Resume when ESCALATION file is renamed to RESOLVED-[issue].md
---
## 💰 Budget & Efficiency
**Your session budget:**
- Session 1: $15 (7.5K Sonnet + 50K Haiku)
- Session 2: $20 (10K Sonnet + 60K Haiku)
- Session 3: $15
- Session 4: $15
- Session 5: $25 (Guardian Council)
**IF.optimise target:** 70% Haiku delegation (use Haiku for all mechanical tasks, Sonnet for synthesis)
**Note:** Can exceed budget if needed (typical pattern: come in under budget)
---
## 📖 Quick Reference
**Repository:** https://github.com/dannystocker/navidocs.git
**Master Branch:** `master` (commit `da1263d`)
**Coordination Branch:** `navidocs-cloud-coordination`
**Session Files:** `CLOUD_SESSION_X_*.md` (X = 1, 2, 3, 4, 5)
**Coordination Status:** `AUTONOMOUS-COORDINATION-STATUS.md` (poll every 5min)
**Output Directory:** `intelligence/session-X/`
**Supporting Docs:**
- `SWARM_COMMUNICATION_PROTOCOL.md` - IF.bus protocol details
- `PARALLEL_LAUNCH_STRATEGY.md` - Multi-session coordination strategy
- `SESSION_DEBUG_BLOCKERS.md` - Known issues (all P0 blockers fixed)
---
## ✅ Final Checklist
Before you start, confirm:
- [ ] Repository cloned: `git clone https://github.com/dannystocker/navidocs.git`
- [ ] On correct commit: `git checkout da1263d`
- [ ] Session file identified: `CLOUD_SESSION_X_*.md` (X = your session number)
- [ ] Coordination polling setup: `git fetch origin navidocs-cloud-coordination` every 5min
- [ ] Output directory exists: `mkdir -p intelligence/session-X/`
- [ ] IF.bus protocol understood (read session file section on intra-agent communication)
---
**Now execute your session mission. Good luck! 🚀**
---
**Questions?**
- Check `AUTONOMOUS-COORDINATION-STATUS.md` for current status
- Check `SESSION_DEBUG_BLOCKERS.md` for known issues
- ESCALATE if blocked >60 minutes