docs: update integrations

CLAUDE.md

@@ -15,7 +15,7 @@
 
 ```
 banatie-strategy/
-├── CLAUDE.md              # This file - AI configuration
+├── CLAUDE.md              # This file - AI configuration and instructions both for Claude Code and Claude Desktop
 ├── INDEX.md               # Map of all documents
 ├── ROADMAP.md             # Current status and priorities
 ├── FRAMEWORK.md           # Discussion framework
@@ -179,6 +179,44 @@ We have a **battle-tested methodology** for conducting collaborative research wi
 
 ---
 
+## Strategy Inbox Check
+
+**When:** At session start, before any other work.
+
+**Location:** `inbox/`
+
+**Process:**
+
+1. **Check inbox folder:**
+```
+   List inbox/ directory
+```
+
+2. **If files found — STOP and announce:**
+   > "📥 Обнаружено входящее от @spy: {filename(s)}. Давай сначала посмотрим что там."
+
+3. **For each file:**
+   - Read and understand the alert
+   - Assess: How does this affect our positioning, pricing, roadmap, assumptions?
+   - Decide: Which strategy docs need updating?
+   - Update relevant files (competitive-analysis, roadmap, reality-check, etc.)
+   - Summarize findings to user:
+     - What happened (facts)
+     - What it means for Banatie (implications)
+     - Suggested actions (if any)
+   - If high-impact: offer to dig deeper ("Это серьёзно. Хочешь покопаю глубже?")
+
+4. **After processing:**
+   - Move file to `inbox/processed/`
+   - Confirm: "Входящие обработаны, продолжаем."
+
+5. **If inbox empty:**
+   - Proceed with session normally, no announcement needed
+
+**Archive:** `inbox/processed/` — keeps history of processed alerts
+
+---
+
 ## 📋 COMMANDS
 
 ### `/review` - Preparation before answering

INDEX.md

@@ -1,6 +1,6 @@
 # Banatie Strategy Documentation Index
 
-**Last Updated:** December 26, 2025
+**Last Updated:** December 30, 2025
 **Total Documents:** 19 (numbered in strategy/execution) + research (prefixed)
 **Next Available Number:** 19
 **Project Stage:** Pre-launch / MVP Development
@@ -88,6 +88,23 @@ Purpose: Guide for strategic sessions with @men
 
 ---
 
+## 🔗 Project Knowledge Files (Always in Context)
+
+These integration documents are stored in Claude Project Knowledge, not on disk.
+They provide @men with navigation maps to related repositories.
+
+**BANATIE-CONTENT-INTEGRATION.md** ⭐ NEW (Dec 29, 2025)  
+*Navigation guide for banatie-content repository*  
+Covers: Multi-agent content system (9 agents), author personas, research folders, content pipeline stages, DataForSEO tools, strategic input channels  
+Purpose: Help @men leverage content system during strategy sessions
+
+**BANATIE-SERVICE-INTEGRATION.md** ⭐ NEW (Dec 30, 2025)  
+*Navigation guide for banatie-service technical repository*  
+Covers: Monorepo structure (apps/landing, apps/api-service, packages/database), API documentation paths, landing page components, production URLs, deployment commands, key technical differentiators  
+Purpose: Help @men find authoritative information about product capabilities
+
+---
+
 ## 📂 Strategy Documents
 
 ### Core Strategic Foundation
@@ -400,5 +417,5 @@ research/seo-keyword-research-*.md → ROADMAP.md (Content Sprint) → blog arti
 ---
 
 **Last maintained by:** @men
-**Version:** 4.1 (SEO research documents added, discussion 2025-12-26 added)
+**Version:** 4.2 (Project Knowledge integration docs added Dec 29-30)
 **Next review:** After Content Marketing Sprint (January 2025)

ROADMAP.md

@@ -19,7 +19,7 @@
 **Sprint:** Production Infrastructure + Testing
 **Focus:** API Testing + SEO Foundation + Content Marketing Prep
 **Next Milestone:** Customer Interviews + Content Marketing
-**Last Updated:** December 26, 2025
+**Last Updated:** December 30, 2025
 
 ---
 
@@ -53,6 +53,18 @@
 
 **See:** [research/seo-keyword-research-placeholder-images.md](research/seo-keyword-research-placeholder-images.md)
 
+### Project Knowledge Integration (Dec 29-30, 2025) ⭐ NEW
+- [x] **BANATIE-CONTENT-INTEGRATION.md** created in Project Knowledge
+  - Navigation map for banatie-content repository
+  - Multi-agent system (9 agents), content pipeline, research structure
+  - Strategic input channels defined (inbox, Perplexity threads)
+- [x] **BANATIE-SERVICE-INTEGRATION.md** created in Project Knowledge
+  - Navigation map for banatie-service technical repository
+  - Monorepo structure, API docs paths, landing components
+  - Production URLs, deployment commands, key differentiators
+
+**Purpose:** Enable @men to find authoritative information across repositories during strategy sessions.
+
 ### Known Issues (Minor)
 - [ ] Healthcheck: containers show "unhealthy" (no curl in images)
 - [ ] Cache permission: landing warns about `.next/cache`
@@ -215,7 +227,7 @@
 **Roadmap Owner:** @men + Oleg
 **Last Updated:** December 26, 2025
 **Next Review:** After ICP validation interviews
-**Version:** 4.1 (DataForSEO integration, SEO foundation added)
+**Version:** 4.2 (Project Knowledge integration docs added Dec 29-30)
 
 **Key Documents:**
 - [research/seo-keyword-research-placeholder-images.md](research/seo-keyword-research-placeholder-images.md) - Keyword research ⭐ NEW

inbox/2025-12-28-nano-banana-market-shift.md

@@ -0,0 +1,192 @@
+# Strategy Alert: Nano Banana Solved Consistency - Market Split into Local vs Cloud
+
+**Date:** 2025-12-28  
+**Type:** Technology Shift + Hypothesis Validation  
+**Urgency:** High
+
+## Summary
+
+Google's Nano Banana (Gemini 2.5 Flash Image, launched May 2025, GA August 2025) achieved enterprise production adoption by solving character consistency - the core pain point our "model selection paralysis" article addresses. Market split into two camps: local models (problem persists) vs cloud APIs (different trade-offs). This validates our workflow-first positioning BUT requires repositioning against cloud dependency trade-off, not just marketplace chaos.
+
+## Details
+
+**Nano Banana Enterprise Adoption (4 months after launch):**
+- Adobe Photoshop - Generative Fill powered by Nano Banana Pro
+- Adobe Firefly - integrated production
+- Figma - building on platform
+- Canva - in production workflows
+- WPP - advertising giant using it
+
+**Consistency Achievement:**
+> "in a whole different league when it comes to consistency" - Reddit testers
+> "addresses core pain point in AI imaging: inconsistency, where rivals like OpenAI's tools often warp details" - Analysis
+
+**Features:**
+- Character/identity consistency across generations
+- Multi-turn conversational editing
+- Multi-image blending
+- Cost: $0.039-0.05/image
+- API-first, production-ready
+
+**Critical Problems After Release:**
+- Over-censorship (false positives in safety filters)
+- Quality degradation vs beta version
+- Cloud dependency (no local option)
+
+**Market Split:**
+
+| Segment | Models | Problem Status | Trade-offs |
+|---------|--------|---------------|------------|
+| **Local** | Flux, SDXL, Chroma | Paralysis PERSISTS | Control vs Complexity |
+| **Cloud** | Nano Banana, Imagen 4 | Choice SOLVED | Simplicity vs Dependency |
+
+## Strategic Implications
+
+**1. Hypothesis Validation ✅**
+
+Our core thesis VALIDATED:
+- Consistency IS the killer feature
+- Workflow integration MATTERS
+- Model choice paralysis REAL (for local users)
+
+**BUT landscape shifted:**
+- Cloud APIs solved choice through curation
+- Problem now LOCAL-specific, not universal
+- New trade-off: control vs convenience
+
+**2. Competitive Landscape Changed**
+
+**BEFORE (our assumption):**
+"Everyone struggles with marketplace chaos (Replicate, fal.ai)"
+
+**AFTER (reality Dec 2025):**
+- **Local users:** still struggle (Flux/SDXL confusion)
+- **Cloud API users:** choice made for them (Nano Banana)
+- **Enterprise:** going cloud (Adobe, Figma, Canva)
+
+**3. Positioning Adjustment Needed**
+
+**CURRENT positioning:**
+"Curated models vs marketplace chaos"
+
+**BETTER positioning:**
+"Developer workflow integration vs cloud dependency"
+
+**Competitors shifted:**
+- **Not just:** Replicate, fal.ai (marketplace)
+- **But also:** Nano Banana, Imagen 4 (cloud curation)
+
+**4. Feature Parity Check**
+
+| Feature | Nano Banana | Banatie |
+|---------|-------------|---------|
+| Character consistency | ✅ Native | ⚠️ @name references |
+| Workflow integration | ❌ No MCP/IDE | ✅ MCP, Claude Code |
+| API-first | ✅ Yes | ✅ Yes |
+| Curated models | ✅ Google chooses | ✅ We choose |
+| Censorship | ❌ Over-filtered | ? Our policy |
+| Cloud dependency | ❌ Required | ❌ Required |
+| Cost | $0.039-0.05/image | ? Our pricing |
+
+**Gap identified:** Nano Banana has NATIVE consistency, we have @name references (manual).
+
+**5. Article/Content Impact**
+
+**"Too Many Models" article:**
+- ✅ Still valid for LOCAL model users
+- ⚠️ Must acknowledge cloud API solution
+- ⚠️ Must reposition Banatie in new landscape
+
+**Target audience shift:**
+- BEFORE: "All developers using AI images"
+- AFTER: "Developers choosing between local chaos vs cloud dependency"
+
+## Recommended Actions
+
+**IMMEDIATE (this week):**
+
+1. **Update "Too Many Models" article:**
+   - Acknowledge Nano Banana game-changer
+   - Reframe: local vs cloud trade-offs
+   - Position Banatie as "third way"
+   - Target: developers wanting workflow integration WITHOUT cloud lock-in
+
+2. **Evaluate @name consistency:**
+   - How does it compare to Nano Banana native consistency?
+   - Demo head-to-head if strong
+   - Improve if weak
+
+3. **Clarify positioning:**
+   - Not "marketplace vs curation"
+   - But "generic APIs vs developer workflow"
+   - Emphasize MCP/Claude Code/Cursor integration
+
+**SHORT-TERM (this month):**
+
+4. **Competitive analysis update:**
+   - Add Nano Banana to competitors.md
+   - Analyze Google's approach
+   - Find our differentiation angle
+
+5. **Consider censorship positioning:**
+   - Nano Banana over-censored
+   - Can we be "developer-friendly" alternative?
+   - What's our content policy?
+
+6. **Pricing strategy:**
+   - Nano Banana: $0.039-0.05/image
+   - Where do we sit?
+   - Workflow value vs raw generation cost
+
+**LONG-TERM (Q1 2025):**
+
+7. **MCP integration priority:**
+   - This is our MOAT vs Nano Banana
+   - They have consistency
+   - We have workflow integration
+   - Double down on developer experience
+
+8. **Consistency feature parity:**
+   - Study Nano Banana's approach
+   - Improve @name or build alternative
+   - Can't be far behind on core feature
+
+9. **Content strategy shift:**
+   - Focus on workflow integration (our strength)
+   - De-emphasize "too many models" (solved for cloud)
+   - Emphasize "coding without context-switching"
+
+## Counter-Arguments to Consider
+
+**"Nano Banana adoption proves cloud wins"**
+
+Counter: Enterprise tolerates dependency for scale, but developers building side projects / startups / custom tools value control and transparency. Different market segments.
+
+**"We're late - Google already solved it"**
+
+Counter: Google solved CONSISTENCY, not WORKFLOW INTEGRATION. Nano Banana requires leaving your IDE/editor. Our MCP integration keeps developers in flow state.
+
+**"Can't compete with Google scale"**
+
+Counter: We're not competing on model quality - we're competing on developer experience. Google makes models, we make workflows. Different value propositions.
+
+## Sources
+
+- Research report: `/banatie-content/research/trends/model-selection-professional-landscape-2025-12-28.md`
+- Google Developers Blog: Nano Banana announcement
+- Reddit: r/StableDiffusion, r/GeminiAI discussions
+- Adobe Blog: Nano Banana Pro in Photoshop/Firefly
+- Professional usage validation: Figma, Canva, WPP integration
+
+## Success Metrics to Watch
+
+- **Nano Banana adoption rate** - is cloud winning?
+- **MCP server adoption** - is workflow integration valued?
+- **Community sentiment** - censorship backlash opportunity?
+- **Pricing pressure** - can we compete at $0.05/image?
+
+---
+
+**Bottom Line:**
+
+Market validated our consistency thesis BUT solved it differently than expected (cloud curation vs our workflow integration). We need to reposition from "curated vs chaos" to "workflow-native vs generic cloud API". Our moat is MCP/IDE integration, not just model selection - double down on that.