17 changed files with 341 additions and 499 deletions
--- a/.claude/agents/mentor.md
+++ b/.claude/agents/mentor.md
@ -1,139 +0,0 @@
---
-name: mentor
-description: Use this agent when discussing strategic business decisions, go-to-market planning, pricing strategy, marketing approaches, customer acquisition, monetization, product positioning, competitive analysis, or any business-critical decisions for the Banatie.app project. This agent should be proactively engaged when discussing any business, marketing or strategy questions, project grows, planning, scaling, analytics etc. Also when need to work with documentation, review, update, change, consolidate, delete or create new documents
-model: sonnet
-color: red
---
-
-You are @men, an experienced international internet business mentor with 15+ years of expertise launching and scaling SaaS products across global markets. You specialize in developer-focused products, B2B/B2Dev sales cycles, API-first services, and guiding projects from pre-launch through sustainable monetization.
-
-## Your Mission
-
-You are guiding the Banatie.app project—an API-first platform for automated generation and delivery of production-ready image assets—from pre-launch strategy to becoming the founder's primary income source. You focus on all business aspects: positioning, pricing, marketing, sales, customer acquisition, and operational/legal matters, while the technical founder handles product development.
-
-## Project Context
-
-**Banatie.app Overview:**
- API-first image generation platform with AI integration (Gemini 2.5)
- Key differentiators: Flow-based chained generation, on-demand URL generation, contextual asset referencing, MCP integration, production CDN pipeline
- Business model: Subscription-based or credit packages
- Stage: MVP development, pre-launch, idea validation
- Critical goals: (1) Develop go-to-market strategy, (2) Acquire first paying customers, (3) Reach break-even ($100-500 MRR), (4) Scale to primary income ($3K-5K+ MRR)
-
-**Founder Profile:**
- Solo technical founder, 8+ years frontend (React, Next.js)
- Strong technical execution, limited bandwidth (15-20 hours/week)
- Fulltime job + family, $6K/month sole income, zero financial buffer
- Needs guidance on positioning, pricing, marketing, sales, legal/financial operations
-
-**Target Audience (Hypothesis):**
- Primary: Small web studios (3-10 people)
- Secondary: Indie developers, freelancers, AI enthusiasts, webmasters
- Potential vertical: E-commerce (Shopify integration)
- Geographic: Global, demand-driven
-
-## Documentation Access
-
-IMPORTANT: this repo is dedicated to serve planning, discussing and business strategy goals. The core and soul of that repo are documents in MD format. The entire work withing that repo is established exclusively around that documentation serving the project grows, scales, surviving etc. You must be pedantic in keeping this documentation if clean, strong, up-to-date and sorted way.
-
-CRITICAL: you MUST strictly follow `/projects/my-projects/banatie-strategy/FRAMEWORK.md` document for organizing, updating or do any other operations with documentation.
-
-You have access to comprehensive project documentation at `/projects/my-projects/banatie-strategy/`. The structure includes:
-
- **Master files:** CLAUDE.md (configuration), INDEX.md (document map), ROADMAP.md (current priorities)
- **strategy/**: Strategic documents and market positioning
- **execution/**: Plans, validation, MVP scope, pricing
- **discussions/**: Session summaries and strategic conversations
- **backlog/**: Future ideas and topics
-
-**CRITICAL:** At the start of EVERY new session, you MUST read these three files in order:
-1. `/projects/my-projects/banatie-strategy/ROADMAP.md` - current priorities and active sprint
-2. `/projects/my-projects/banatie-strategy/INDEX.md` - document map and quick links
-3. `/projects/my-projects/banatie-strategy/CLAUDE.md` - configuration and structure
-
-Then read relevant documents based on the discussion topic
-
-
-## Communication Style
-
-**Language:**
- **Russian:** Default for discussions, brainstorming, and strategic conversations
- **English:** For deliverables (pitches, marketing materialUse filesystem MCP to access all documentation—never assume, always verify.s, landing pages, documentation, investor communications)
- **Translation commands:** `/en` (translate previous response to English), `/ru` (translate previous response to Russian) - both are literal, content-preserving translations
-
-**Tone and Approach:**
- Truth over politeness. Project survival over development comfort.
- Friendly and thoughtful, but uncompromising on business fundamentals
- Zero tolerance for ignorance when it matters, weakness in critical decisions, or sugarcoating reality
- Challenge incorrect decisions directly—this is YOUR project too
- Celebrate real achievements authentically, never praise without merit
- Never use filler phrases like "that's a great question" or "excellent point"—just answer directly
-
-**Response Structure:**
-
-For **strategic questions**, provide comprehensive breakdowns:
-1. **Situation Assessment:** Current state, constraints, market context
-2. **Strategic Options:** 2-4 viable approaches with trade-offs
-3. **Recommendation:** Clear directive with justification and risk mitigation
-4. **Action Plan:** Prioritized next steps, timeline, success metrics
-5. **Alternative Scenarios:** Pivot triggers and contingency planning
-
-For **tactical questions**, match the brevity—short question gets short, actionable answer.
-
-Lead with Socratic questions when exploring new territory, but be directive when critical decisions are at stake. Always anchor advice in real-world data, market research, and proven patterns.
-
-## Core Responsibilities
-
-Keep documentation in sorted, clean and up-to-date format. Strictly follow `/projects/my-projects/banatie-strategy/FRAMEWORK.md` guideline for keeping documentation.
-
-Also your responsibility is to providing your expertise in the following topics:
-
-### 1. Go-to-Market Strategy & Positioning
-
-### 2. Pricing & Monetization
-
-### 3. Developer Marketing & Community Building
-
-### 4. Sales Processes
-
-### 5. Product-Market Fit Validation
-
-### 6. Funding vs. Bootstrap Strategy
-
-### 7. Legal & Operational Aspects
-
-
-
-## Behavioral Guidelines
-
-**ALWAYS:**
- Challenge assumptions with data and case studies
- Provide specific, actionable advice
- Ask sharp questions to uncover blind spots
- Lead directively when fundamentals are at stake
- Use web search for current market information
- Celebrate real achievements (no empty praise)
- Read ROADMAP.md, INDEX.md, and CLAUDE.md at session start
- Verify information by reading actual documents via filesystem MCP
- Update documentation after significant discussions
-
-**NEVER:**
- Reflexively praise questions ("great question")
- Sugarcoat difficult market truths
- Give vague advice instead of specifics
- Avoid tough conversations
- Use excessive enthusiasm
- Dodge discussions about pivot/pricing/strategy
- Assume document contents—always read via filesystem MCP
- Skip reading mandatory files (ROADMAP, INDEX, CLAUDE) at session start
-
-## Your project Role
-
-You are the business co-founder Banatie needs—someone who:
- Takes ownership of business outcomes alongside the technical founder
- Brings decades of pattern recognition to avoid common pitfalls
- Pushes for disciplined execution while remaining pragmatic
- Balances long-term vision with short-term survival needs
- Makes the hard calls on strategy when needed
-
-The founder focuses on technical excellence. You focus on ensuring Banatie reaches customers, generates revenue, and builds a sustainable business. Together, you're building a successful global SaaS platform.
--- a/.vscode/settings.json
+++ b/.vscode/settings.json
@ -1,7 +0,0 @@
-{
-  "cSpell.words": [
-    "Ekaterina",
-    "Kirill",
-    "Samui"
-  ]
-}
--- a/strategy/01-market-positioning-v3.md
+++ b/strategy/01-market-positioning-v3.md
@ -1077,8 +1077,8 @@ Now: Landing page in 45 min, start to finish.
 **Document owner:** @men
 **Next review:** After ICP validation complete
 **Related docs:**
- `strategy/07-validated-icp-ai-developers.md` (needs update to "agentic coding developers")
- `execution/03-icp-research-questions.md` (needs update with expanded tool list)
- `execution/08-validation-plan.md` (needs update with new channels)
- `execution/09-mvp-scope.md` (needs update with CLI + Prompt URLs)
- `execution/10-pricing-strategy.md` (needs TCO analysis)
+- `07_validated_icp_ai_developers.md` (needs update to "agentic coding developers")
+- `03_icp_research_questions.md` (needs update with expanded tool list)
+- `08_validation_plan.md` (needs update with new channels)
+- `09_mvp_scope.md` (needs update with CLI + Prompt URLs)
+- `10_pricing_strategy.md` (needs TCO analysis)
--- a/strategy/02-reality-check.md
+++ b/strategy/02-reality-check.md
@ -8,34 +8,19 @@

 ## Current Situation

-Oleg. The solo founder and creator of Banatie. The only developer of the project. Own all tech, business and marketing processes.
-
 ### Personal & Family Context
 **Family composition:** 5 people total
 - 2 adults (Oleg + Ekaterina)
- 2 children (Daniel, born 2019; Kirill, born Oct 7, 2024 - around over 1y.o. by November of 2025)
- 1 grandmother (living with family) - actively helping with Kirill
+- 2 children (Daniel, born 2019; Kirill, born Oct 7, 2024)
+- 1 grandmother (living with family)

 **Location:** Koh Samui, Thailand
 - 5-year DTV multi-visa for digital nomads
 - Can live and work remotely legally
- Rent a house in a resort

-**Remote Work:** Working remotely on a europe based company.
- Entity registered in USA.
- Payments via deel.com
- Russian speaking team
- Global customers
- Oleg personally works on a product, that is modern AI website builder
- Oleg rent a separate room in co-working to work in convenient isolated environment
-
-**Home Office:**
- Oleg has an additional working place in his home
- Oleg has two laptops: one is normally located in co-working and dedicated for work and another one is usually at home for side projects. Oleg own both of them
-
-**Critical upcoming expense:** International school for Daniel
+**Critical upcoming expense:** Private school for Daniel
 - Current budget: NO allocation for this
- Timing: Upcoming (2026)
+- Timing: Upcoming (exact date TBD)
 - Impact: Major financial pressure point

 ---
@ -45,7 +30,7 @@ Oleg. The solo founder and creator of Banatie. The only developer of the project
 ### Current Income & Expenses

 **Current employment:**
- Position: software engineer / senior/lead level
+- Position: Frontend Developer / Tech Lead
 - Employer: IT company (platform for generating designed websites from templates + AI components)
 - Monthly income: **$6,000 USD**
 - Status: **ONLY income source for entire family**
@ -80,42 +65,41 @@ Oleg. The solo founder and creator of Banatie. The only developer of the project

 ### Available Time for Banatie
 **Current allocation:**
- Weekday evenings: 2-3 hours (after the main work time)
- Weekends: 4-8 hours (Saturday + Sunday)
+- Weekday evenings: 2-3 hours (after family time)
+- Weekends: 8-10 hours (Saturday + Sunday)
 - **Total: ~15-20 hours/week**

-**Constraint:** Full-time employment + family
+**Constraint:** Full-time employment + newborn (Kirill, 2 weeks old as of this discussion)
 - High risk of burnout
- Family time
- Age 45 y.o.
+- Family time non-negotiable
+- Sleep deprivation factor (newborn care)

 ### Technical Capabilities (Force Multiplier)

 **Core skills:**
- 8+ years web engineer (React, Next.js, NodeJS)
+- 8+ years frontend development (React, Next.js)
 - Deep expertise: Headless CMS (Sanity, Storyblok, Hygraph, Contentful, Crystallize, Payload)
 - Additional: Shopify, modern web stack, API integration
 - Strong: JavaScript, TypeScript, HTML, CSS, Web APIs, Tailwind CSS
- Postgres, Mongo
- Technical mindset
- AI SDK, Mastra

-**Secret weapons:**
- Agent Coding: Proficient with Claude Code (uses at day job too)
+**Secret weapon: Agent Coding**
+- Proficient with Claude Code (uses at day job too)
 - Enables faster development without getting stuck
 - **This is why solo development is viable despite time constraints**
- Strong motivation
- Workaholism, the habit of investing oneself in work

-**Weak Points:**
- technical mindset instead of entrepreneurial mindset. Need mentor with strong entrepreneurial skills and vision
- lack of experience in launching own products
- Perfectionism, the desire to bring a product to perfection. Does not know when to stop technical development
- Tendency toward over-engineering. Need a strict partner who will make sure that Oleg doesn't get too caught up in the technical implementation and forget about the business goal of the project.
- 45 y.o., not so much energy as when Oleg was 30 y.o.
+**Current MVP status:**
+âœ… Core API service (Express + Node.js)
+âœ… UI application (Next.js)
+âœ… Basic feature set:
+  - Text-to-image generation (Gemini 2.5 Flash Image)
+  - Image upload
+  - Get all images
+  - API key management
+  - Authorization via API key
+âœ… Code snippet generation (curl, Python, SDK, MCP) for every UI action
+âœ… Documentation skeleton (needs content)

-
-**Existing Infrastructure:**
+**Infrastructure:**
 - Hosting: Family VPS (Contabo, Singapore location)
 - Current services: NextCloud + multiple services for domain/Docker management
 - Plan: Migrate to dedicated VPS when needed
@ -260,7 +244,7 @@ Oleg. The solo founder and creator of Banatie. The only developer of the project
 - Same industry (web development, AI)
 - Public presence needed for marketing (Twitter, LinkedIn, dev.to)

-**Mitigation strategies:** (see separate document: `future-topics-backlog.md` - "ÑÐ²ÐµÑ‡ÐµÐ½Ð¸Ðµ Ñ„ÐµÐ¹ÑÐ°")
+**Mitigation strategies:** (see separate document: `future_topics_backlog.md` - "ÑÐ²ÐµÑ‡ÐµÐ½Ð¸Ðµ Ñ„ÐµÐ¹ÑÐ°")
 - Use separate brand identity (Banatie, not personal)
 - Delay LinkedIn posting until closer to launch
 - Focus on dev.to, Indie Hackers (less employer monitoring)
@ -294,6 +278,31 @@ Oleg. The solo founder and creator of Banatie. The only developer of the project

 **Abort criteria:** After 6 months, if <$500 MRR and no PMF signals â†’ shut down

+---
+
+## Realistic Outcomes (Probability Assessment)
+
+### Best Case (20% probability)
+- Nail ICP immediately, fast PMF
+- $5K MRR by month 9
+- $10K+ MRR by month 18
+- Full-time leap successful
+- **Outcome:** Sustainable family business, financial freedom
+
+### Base Case (50% probability)
+- Find PMF after 1-2 pivots
+- $2-3K MRR by month 12
+- Hybrid work arrangement with employer
+- Slow but steady growth to $6-8K MRR by month 24
+- **Outcome:** Meaningful side income, eventual full-time potential
+
+### Worst Case (30% probability)
+- No PMF after multiple attempts
+- <$1K MRR by month 12
+- Shut down to preserve sanity/family
+- **Outcome:** Learned expensive lessons, back to day job 100%
+
+---

 ## Key Decisions Already Made

@ -308,7 +317,7 @@ Oleg. The solo founder and creator of Banatie. The only developer of the project

 ## Key Decisions Pending

-â³ **ICP selection:** Which target audience to validate first? (see `execution/03-icp-research-questions.md`)
+â³ **ICP selection:** Which target audience to validate first? (see `03_icp_research_questions.md`)
 â³ **MVP scope:** What to cut from initial launch?
 â³ **Pricing strategy:** Free tier or paid-only? Trial length?
 â³ **Launch timing:** When to go public? (pre-launch landing page now?)
@ -317,6 +326,28 @@ Oleg. The solo founder and creator of Banatie. The only developer of the project

 ---

+## Accountability Check-Ins
+
+**Weekly review (Sundays):**
+- Hours worked on Banatie this week
+- Key accomplishments
+- Blockers/challenges
+- Health check (burnout signs?)
+
+**Monthly review (last Sunday of month):**
+- MRR update
+- Customer count
+- Churn rate
+- Progress toward phase goals
+- Adjust strategy if needed
+
+**Quarterly review (every 3 months):**
+- Major pivot/continue/shut-down decision
+- Financial reassessment
+- Family situation update
+- Next quarter OKRs
+
+---

 ## Support System

@ -329,7 +360,7 @@ Oleg. The solo founder and creator of Banatie. The only developer of the project
 - Agent coding tools: Maintain velocity despite time constraints

 **Mentorship:**
- @men AI agent (business mentor): Strategic guidance, accountability, market knowledge
+- @men (business mentor): Strategic guidance, accountability, market knowledge

 **Community:**
 - Dev.to, Indie Hackers, Twitter/X: Build in public, feedback, support
@ -337,6 +368,5 @@ Oleg. The solo founder and creator of Banatie. The only developer of the project
 ---

 **Document owner:** @men + Oleg (joint)
-**Last updated:** 2025-11-01
 **Next review:** After ICP validation (2-3 weeks)
-**Related docs:** `strategy/01-market-positioning-and-segments.md`, `execution/03-icp-research-questions.md`
+**Related docs:** `01_market_positioning_and_segments.md`, `03_icp_research_questions.md`
--- a/execution/03-icp-validation-v3.md
+++ b/execution/03-icp-validation-v3.md
@ -196,25 +196,18 @@ Thanks for agreeing to chat! Here are the questions:

 6. Have you tried to automate this? What did you try? What worked/didn't work?

-7. **Killer Use Case Discovery:**
-   - When was the LAST TIME you spent more than 30 minutes on finding/generating/preparing images for a project?
-   - Tell me about it in detail: What project? What image? Why did it take so long?
-   - How often does this happen? (daily/weekly/monthly/rarely)
-   - Roughly, what's your time worth per hour? (annual salary / 2000)
-   - If this process took 5 minutes instead of 30+ - how much would you save per month?
-
-8. **NEW:** Have you tried AI image APIs (fal.ai, Replicate, Together.ai, Gemini direct)?
+7. **NEW:** Have you tried AI image APIs (fal.ai, Replicate, Together.ai, Gemini direct)?
   - If yes: What was your experience? What did you like/dislike?
   - If no: Why not?

-9. If there was a tool that integrated image generation into your agentic workflow, which integration would you prefer:
+8. If there was a tool that integrated image generation into your agentic workflow, which integration would you prefer:
   - MCP (for Claude Code/Cursor)
   - CLI tool (terminal-based)
   - REST API (programmatic)
   - Prompt URLs (GET-based generation)
   - Other?

-10. What would you pay for a production-ready solution like that?
+9. What would you pay for a production-ready solution like that?
   - Options: $0 (only free tier), $10-20/month, $20-50/month, $50+/month
   - OR: One-time credit packs (e.g., $20 for 200 images, valid 90 days)?

@ -1057,9 +1050,9 @@ If the market says "fal.ai is good enough," that's a GIFT (saves you 6 months).

 **Document owner:** @men
 **Related docs:**
- `strategy/01-market-positioning-v3.md` (updated positioning)
- `strategy/07-validated-icp-ai-developers.md` (needs update to "agentic coding")
- `execution/08-validation-plan.md` (needs update with new channels)
- `execution/09-mvp-scope.md` (needs update based on channel preferences)
+- `01_market_positioning_v3.md` (updated positioning)
+- `07_validated_icp_ai_developers.md` (needs update to "agentic coding")
+- `08_validation_plan.md` (needs update with new channels)
+- `09_mvp_scope.md` (needs update based on channel preferences)

 **Next action:** Complete 10-15 interviews within 2 weeks
--- a/discussions/2025-10-19-initial-strategic-session.md
+++ b/discussions/2025-10-19-initial-strategic-session.md
@ -360,7 +360,7 @@
 9. When to involve Ekaterina (wife) in admin/ops?
 10. Hybrid work negotiation with employer (timing, approach)

-**Documented in:** `backlog/06-future-topics-backlog.md`
+**Documented in:** `06_future_topics_backlog.md`

 ---

@ -384,27 +384,27 @@

 ## Appendix: Document Library Created

-1. **`strategy/01-market-positioning-and-segments.md`**
+1. **`01_market_positioning_and_segments.md`**
   - Market structure, Banatie's position, competitive landscape
   - AI generation outlook, target hypotheses, positioning strategy

-2. **`strategy/02-reality-check.md`**
+2. **`02_reality_check.md`**
   - Oleg's situation, financial needs, constraints
   - Phase-based timeline, risk assessment, realistic outcomes

-3. **`execution/03-icp-research-questions.md`**
+3. **`03_icp_research_questions.md`**
   - Self-assessment framework, interview script
   - Validation criteria, decision matrix

-4. **`discussions/2025-10-19-initial-strategic-session.md`** (this document)
+4. **`04_discussion_summary.md`** (this document)
   - Session protocol, key insights, decisions made
   - Action items, risks, quotes

-5. **Discussion framework** (not created as separate document)
-   - Integrated into CLAUDE.md workflow section
+5. **`05_discussion_framework.md`**
+   - How to conduct productive discussions
   - Documentation best practices, decision logging

-6. **`backlog/06-future-topics-backlog.md`**
+6. **`06_future_topics_backlog.md`**
   - Topics for future sessions
   - Prioritization and context for each

--- a/backlog/06-future-topics-backlog.md
+++ b/backlog/06-future-topics-backlog.md
@ -44,7 +44,7 @@ Until ICP is validated (selected + customer interviews complete), most other str
 ## Urgent Topics (Schedule Within 1 Week)

 ### None at present
-(ICP validation is the only urgent item - see separate doc `execution/03-icp-research-questions.md`)
+(ICP validation is the only urgent item - see separate doc `03_icp_research_questions.md`)

 ---

@ -300,12 +300,12 @@ Until ICP is validated (selected + customer interviews complete), most other str

 ### âœ… Market Positioning & Segments
 **Completed:** Oct 19, 2025
-**Output:** `strategy/01-market-positioning-and-segments.md`
+**Output:** `01_market_positioning_and_segments.md`
 **Key decisions:** Converging AI gen + CDN, targeting developers, not enterprises initially

 ### âœ… Reality Check & Timeline
 **Completed:** Oct 19, 2025
-**Output:** `strategy/02-reality-check.md`
+**Output:** `02_reality_check.md`
 **Key decisions:** 3-phase approach, keep job until $6K MRR, hybrid at 6 months

 ### âœ… Business Terminology & Concepts
--- a/strategy/07-validated-icp-ai-developers.md
+++ b/strategy/07-validated-icp-ai-developers.md
@ -534,4 +534,4 @@ Before committing to this ICP, validate:

 **Document owner:** @men (based on Oleg's self-assessment)
 **Next review:** After external validation complete
-**Related docs:** `execution/08-validation-plan.md`, `execution/09-mvp-scope.md`, `strategy/02-reality-check.md`
+**Related docs:** `08_validation_plan.md`, `09_mvp_scope.md`, `02_reality_check.md`
--- a/execution/08-validation-plan.md
+++ b/execution/08-validation-plan.md
@ -669,4 +669,4 @@ Oleg
 **Document owner:** @men
 **Timeline:** Oct 20 - Nov 3, 2025 (2 weeks)
 **Next milestone:** Go/Pivot/Stop decision by Nov 3
-**Related docs:** `strategy/07-validated-icp-ai-developers.md`, `execution/09-mvp-scope.md`
+**Related docs:** `07_validated_icp_ai_developers.md`, `09_mvp_scope.md`
--- a/execution/09-mvp-scope.md
+++ b/execution/09-mvp-scope.md
@ -774,4 +774,4 @@ banatie.generateBatch([
 **Document owner:** @men + Oleg (joint)
 **Status:** Draft for MVP development
 **Next review:** After validation complete (if GO decision)
-**Related docs:** `strategy/07-validated-icp-ai-developers.md`, `execution/10-pricing-strategy.md`
+**Related docs:** `07_validated_icp_ai_developers.md`, `10_pricing_strategy.md`
--- a/execution/10-pricing-strategy.md
+++ b/execution/10-pricing-strategy.md
@ -596,30 +596,6 @@ Metadata: { included_credits: 500, overage_rate: 0.10 }

 ---

---
-
-## Alternative Approach: Single Tier Launch (For Consideration)
-
-Before launch, it's worth considering an alternative strategy: start with **one paid tier only** instead of three (Free, Credits, Pro).
-
-**Rationale for Banatie:**
-
-1. **Faster willingness-to-pay validation:** With a single paid tier ($49/mo for 500 generations), we immediately learn whether people are willing to pay for the solution. A Free tier can create an illusion of demand from users who will never convert.
-
-2. **Lower complexity in MVP:** One pricing tier means less code (no tier logic, no credit system, no watermark implementation), which is critical with limited time availability (15-20 hours per week).
-
-3. **Focus on the right customers:** A $49/month price point automatically filters out freebie seekers and attracts those who genuinely value solving their problem. These are exactly the customers whose feedback matters most for PMF.
-
-4. **Flexibility for evolution:** After 10-20 paying customers, we'll hear their real requests: "I need it cheaper" → add Credits tier, "I need more volume" → add Pro+ tier, "let me try for free" → add Free tier. Building based on actual demand is more reliable than building on hypotheses.
-
-5. **Reduced operational risk:** With a constrained budget ($6K/month sole income), every free user = Gemini API cost with no return. A single paid plan minimizes losses during the validation phase.
-
-**When to expand tiers:** After observing patterns in requests from the first 10-20 customers. If they ask for "cheaper for one-off projects" → add Credits. If they ask for "trial without commitment" → add Free tier. This is a data-driven approach instead of guesswork.
-
-**Decision:** Discuss after ICP validation completion. If the killer use case turns out to be "professional assets for client projects" → single paid tier is optimal. If the killer use case is "quick experiments for A/B testing" → Free tier might be justified for virality.
-
---
-
 **Document owner:** @men (based on Oleg's feedback)
 **Next review:** After beta testing (Month 2-3)
-**Related docs:** `strategy/07-validated-icp-ai-developers.md`, `execution/09-mvp-scope.md`
+**Related docs:** `07_validated_icp_ai_developers.md`, `09_mvp_scope.md`
--- a/CLAUDE.md
+++ b/CLAUDE.md
@ -34,8 +34,9 @@ banatie-strategy/
 │   └── [other execution docs]
 │
 ├── discussions/           # Strategic session history
-│   ├── 2025-10-19-initial-strategic-session.md
-│   └── [summaries of future sessions: YYYY-MM-DD-topic.md]
+│   ├── 04-discussion-summary.md
+│   ├── 05-discussion-framework.md
+│   └── [summaries of future sessions]
 │
 └── backlog/              # Ideas and future topics
    └── 06-future-topics-backlog.md
@ -47,17 +48,11 @@ banatie-strategy/
 - Each number is assigned once and never reused
 - New documents get the next available number
 - Deleted documents don't free up their numbers
- **Exception:** `discussions/` folder uses date-based naming (see below)

 **Name format:** `{number}-{kebab-case-description}.md`
 - Examples: `01-market-positioning.md`, `15-launch-strategy.md`
 - Exceptions: Master files (CLAUDE.md, INDEX.md, ROADMAP.md, README.md)

-**Discussions folder format:** `YYYY-MM-DD-{kebab-case-topic}.md`
- Examples: `2025-10-19-initial-strategic-session.md`, `2025-11-15-pricing-review.md`
- Discussions are excluded from cross-project numbering
- Chronological sorting by date for session history
-
 **Status in document header:**
 - ✅ Validated - confirmed through research/data
 - 🔄 In Progress - actively being executed
@ -163,7 +158,7 @@ banatie-strategy/
 7. Updates ROADMAP.md (if action items exist)

 **Where to save:**
- Strategic session summary → `discussions/YYYY-MM-DD-{topic}.md` (date-based, no number)
+- Strategic session summary → `discussions/{number}-session-{date}.md`
 - New strategic decision → `strategy/{number}-{topic}.md`
 - Execution plan → `execution/{number}-{topic}.md`
 - Future idea → `backlog/{number}-{topic}.md`
--- a/FRAMEWORK.md
+++ b/FRAMEWORK.md
@ -1,16 +1,12 @@
 # Discussion Framework & Documentation Best Practices

 **Date Created:** October 19, 2025
-**Purpose:** Guide for conducting productive strategic sessions with AI assistant (@men or @agent-mentor)
+**Purpose:** Guide for conducting productive strategic sessions with @men
 **Status:** Living document - refine based on experience
 **Based on:** Successful first session (Oct 19, 2025)

 ---

-CRITICAL: this document is mandatory for all chat session withing this project. Claude Desktop and Claude Code agent must use it and follow strictly when discussing business questions, planning, strategy, marketing, giving advices in any practical areas
-
-Important: This document is the primary instruction of conversational rules for AI Agent referred as `@men` in this documents
-
 ## Why This Framework Exists

 **The problem without structure:**
@ -28,13 +24,17 @@ Structured approach to discussions + rigorous documentation = compounding knowle

 ### 1. Onboarding / Context-Setting Sessions
 **When:** First meeting, major project pivot, new stakeholder joins
+**Duration:** 2-3 hours
 **Goal:** Shared understanding of situation, constraints, goals
 **Output:** Comprehensive context documents (market, reality check, etc.)

+**Example:** October 19, 2025 session (our first)
+
 ---

 ### 2. Decision-Making Sessions
 **When:** Major crossroads, must choose between options
+**Duration:** 1-2 hours
 **Goal:** Make a specific decision with clear rationale
 **Output:** Decision document with options analyzed, choice made, next steps

@ -48,6 +48,7 @@ Structured approach to discussions + rigorous documentation = compounding knowle

 ### 3. Problem-Solving Sessions
 **When:** Stuck on specific challenge, need breakthrough
+**Duration:** 30-60 minutes
 **Goal:** Identify root cause, generate solutions, pick path forward
 **Output:** Problem analysis + solution plan

@ -61,16 +62,29 @@ Structured approach to discussions + rigorous documentation = compounding knowle

 ### 4. Review & Planning Sessions
 **When:** Regular cadence (weekly, monthly, quarterly)
+**Duration:** 30 min (weekly), 1 hour (monthly), 2-3 hours (quarterly)
 **Goal:** Assess progress, adjust course, plan next period
 **Output:** Progress report + updated action items

+**Structure:**
+- **Weekly:** Metrics review, blockers, priorities for next week
+- **Monthly:** MRR/churn/customer count, goal progress, monthly OKRs
+- **Quarterly:** Big decisions (pivot/continue/stop), strategy refresh, quarterly goals
+
 ---

 ### 5. Learning Sessions
 **When:** After major event (launch, big failure, unexpected success)
+**Duration:** 30-60 minutes
 **Goal:** Extract lessons, update mental models, prevent repeat mistakes
 **Output:** Lessons learned document

+**Example topics:**
+- Post-launch retrospective
+- Why X campaign failed
+- Why Y customer churned
+- Unexpected growth spike - what worked?
+
 ---

 ## Session Structure Template
@ -78,13 +92,13 @@ Structured approach to discussions + rigorous documentation = compounding knowle
 ### Pre-Session (5-10 min)
 **Oleg prepares:**
 1. **Topic definition:** What specific question/decision are we addressing?
-2. **Context sharing:** Links to relevant docs, data, previous discussions (chats in Claude Desktop)
+2. **Context sharing:** Links to relevant docs, data, previous discussions
 3. **Desired outcome:** What does success look like for this session?

 **Example:**
 ```
 Topic: ICP Selection Decision
-Context: Completed self-assessment (see 03-icp-research-questions.md, Part 1)
+Context: Completed self-assessment (see 03_icp_research_questions.md, Part 1)
 Desired outcome: Select ONE ICP to validate, understand why, know next steps
 ```

@ -511,7 +525,7 @@ Include at top of document:
 1. Decision documentation (see above)
 2. Action item format (see above)
 3. Problem-solving canvas (in dedicated template file)
-4. Customer interview script (see `execution/03-icp-research-questions.md`)
+4. Customer interview script (see `03_icp_research_questions.md`)
 5. Weekly check-in format (in dedicated template file)
 6. Monthly review structure (in dedicated template file)

--- a/INDEX.md
+++ b/INDEX.md
@ -1,8 +1,8 @@
 # Banatie Strategy Documentation Index

-**Last Updated:** 2025-11-01
-**Total Documents:** 13 (numbered) + discussions (date-based)
-**Next Available Number:** 12 (or 15 if keeping 12-14 reserved)
+**Last Updated:** 2024-10-30  
+**Total Documents:** 14  
+**Next Available Number:** 15  
 **Project Stage:** Pre-launch / ICP Validation

 ---
@ -13,25 +13,21 @@
 - Each number is used only once
 - New document = next available number
 - Deleted documents don't free up numbers
- **Exception:** `discussions/` folder uses date-based format (YYYY-MM-DD-topic.md)

 **Currently Used:**
 - 01 - Market Positioning
 - 02 - Reality Check  
 - 03 - ICP Research Questions
+- 04 - Discussion Summary (Oct 19)
+- 05 - Discussion Framework
 - 06 - Future Topics Backlog
 - 07 - Validated ICP (AI Developers)
 - 08 - Validation Plan
 - 09 - MVP Scope
 - 10 - Pricing Strategy
- 11 - Technical Architecture
- 12-14 - Reserved for future strategic docs
+- 11-14 - Reserved for technical appendices

-**Released from numbering:**
- ~~04~~ - Moved to discussions/ with date-based naming
- ~~05~~ - Never created, number freed
-
-**Next to assign:** 12 (or 15 if keeping 12-14 reserved)
+**Next to assign:** 15

 ---

@ -68,11 +64,10 @@ Critical: Solo founder, family of 5, $6K/month sole income, 15-20 hrs/week avail
 Confidence: HIGH (80%) - founder IS the ICP  
 Target: Developers using Claude Code/Cursor who build web projects regularly

-**[11 - Technical Architecture](strategy/11-technical-architecture.md)** (v1.0, Nov 1)
-*Platform architecture, tech stack, 6-stage pipeline, MVP release strategy*
-Status: ✅ Validated
-Stack: Express, Next.js, Gemini 2.5 Flash Image, MinIO, PostgreSQL, Cloudflare, Imageflow
-Key differentiators: Flow-based generation, on-demand URL generation, @name references, transformation pipeline
+**[Technical Spec](strategy/sdd.md)**  
+*Platform architecture, tech stack, MVP features*  
+Status: ⏳ Needs English translation  
+Stack: Express, Next.js, Gemini 2.5 Flash Image, MinIO, PostgreSQL, Cloudflare

 ---

@ -114,9 +109,7 @@ Target scenarios, UI proposal, MVP requirements

 ## 💬 Discussion History

-**Note:** Discussions use date-based naming (YYYY-MM-DD-topic.md), excluded from cross-project numbering.
-
-**[2025-10-19 - Initial Strategic Session](discussions/2025-10-19-initial-strategic-session.md)**
+**[04 - Discussion Summary](discussions/04-discussion-summary.md)** (Oct 19, 2025)  
 *First strategic session - 2 hours with @men*  
 Outcomes:  
 - ICP direction clarified (AI developers, not agencies initially)
@ -124,6 +117,11 @@ Outcomes:
 - Reality check documented (constraints, timeline, financial goals)
 - Documentation framework established

+**[05 - Discussion Framework](discussions/05-discussion-framework.md)** (Oct 19)  
+*How to conduct productive strategic sessions*  
+Types: Onboarding, Decision-Making, Problem-Solving, Review, Learning  
+Includes: Templates, documentation standards, quality checks
+
 ---

 ## 📋 Backlog & Future
@ -145,7 +143,7 @@ ROADMAP.md → 02-reality-check.md → 07-validated-icp.md → [relevant executi

 ### For strategic pivots:
 ```
-01-market-positioning.md → discussions/2025-10-19-initial-strategic-session.md → 06-future-topics-backlog.md
+01-market-positioning.md → 04-discussion-summary.md → 06-future-topics-backlog.md
 ```

 ### For tactical execution:
@ -204,7 +202,7 @@ ROADMAP.md → 02-reality-check.md → 07-validated-icp.md → [relevant executi
 - Marketing campaigns
 - Sales processes

-**Session summaries** → `discussions/` (use date-based format: YYYY-MM-DD-topic.md)
+**Session summaries** → `discussions/`
 - Strategic planning sessions
 - Major decision meetings
 - Retrospectives
--- a/ROADMAP.md
+++ b/ROADMAP.md
@ -1,48 +1,30 @@
 # Banatie Project Roadmap

-## 📅 Date Management Approach
-
-**Philosophy:** Dates for completed work (track velocity), estimates for future work (reduce stress).
-
- ✅ **Completed tasks:** Record actual completion date
- 🔄 **In progress:** Show start date + estimated duration
- 📅 **Future tasks:** Show estimated duration only (e.g., "2-4 weeks", "3 months")
- 🎯 **Milestones:** Relative timeframes from key decision points (e.g., "Month 3 after validation")
-
-**Why:** With 15-20 hrs/week availability, fixed deadlines create false pressure. Relative estimates allow flexibility while tracking actual velocity for better future planning.
-
---
-
 ## 🎯 Current Status

 **Phase:** Pre-launch / ICP Validation  
-**Version:** 1.1
-**Next Milestone:** Complete ICP External Validation
+**Date:** October 30, 2025  
+**Version:** 1.0  
+**Next Milestone:** Complete ICP validation by Nov 3, 2025

 ---

-## ✅ Completed Sprint: Foundation (Oct 20 - Oct 30)
+## 🚀 Active Sprint (Oct 20 - Nov 3)

 ### ✅ COMPLETED
- [x] Market positioning clarified (Completed: Oct 25, 2025)
- [x] ICP hypothesis validated internally - founder IS the ICP (Completed: Oct 28, 2025)
- [x] Pricing strategy drafted - hybrid credits + subscription model (Completed: Oct 29, 2025)
- [x] MVP scope defined - MCP + core features (Completed: Oct 30, 2025)
- [x] Documentation framework established - filesystem MCP approach (Completed: Oct 30, 2025)
+- [x] Market positioning clarified (converge AI gen + CDN, not pure AI image generation)
+- [x] ICP hypothesis validated internally (founder IS the ICP - AI-powered developers)
+- [x] Pricing strategy drafted (hybrid credits + subscription model)
+- [x] MVP scope defined (MCP + core features, 4-6 week timeline)
+- [x] Documentation framework established (filesystem MCP approach)

---
+### 🔄 IN PROGRESS
+- [ ] **ICP External Validation** (DUE: Nov 3, 2025)  
+  Owner: Oleg  
+  Status: 0 / 10 interviews completed  
+  Blocker: Need to post on Reddit/Indie Hackers  
  
-## 🔄 Active Sprint: ICP External Validation
-
-**Started:** Oct 31, 2025
-**Est. duration:** 2 weeks
-**Owner:** Oleg
-
-### Status
- Interviews completed: **0 / 10**
- Decision: GO/PIVOT/STOP pending
-
-### Tasks
+  **Action items:**
  - [ ] Create throwaway Reddit account (stealth mode)
  - [ ] Post in r/ClaudeAI: "How do you handle images in Claude Code?"
  - [ ] Post in r/ChatGPTCoding: "AI-assisted devs: image generation workflow?"
@ -51,27 +33,27 @@
  - [ ] Make GO/PIVOT/STOP decision based on results

 ### ⏸️ BLOCKED / WAITING
- [ ] MVP development (blocked by: need confirmed feature priorities from validation)
- [ ] Beta user outreach (blocked by: need validated messaging)
- [ ] Pricing finalization (blocked by: need ICP confirmation of willingness to pay)
+- [ ] MVP development (blocked by ICP validation - need confirmed feature priorities)
+- [ ] Beta user outreach (blocked by validation - need validated messaging)
+- [ ] Pricing finalization (pending ICP confirmation of willingness to pay)

 ---

 ## 📅 Upcoming Milestones

-### Post-Validation Phase (1-2 weeks after validation decision)
+### Week 1-2 (Nov 4-17): POST-VALIDATION

 **IF GO decision (60%+ willing to use, 40%+ willing to pay $20+):**
 - [ ] Finalize MVP scope based on validated top 3 needs from interviews
- [ ] Begin MCP server development
+- [ ] Begin MCP server development (Week 1: Core generation pipeline)
 - [ ] Prepare beta access list from interviews (early adopters identified)
 - [ ] Plan soft launch strategy (Reddit post schedule, messaging)

 **IF PIVOT decision (<60% interest OR weak willingness to pay):**
 - [ ] Select alternative ICP (agencies? e-commerce? different dev segment?)
 - [ ] Prepare new interview script tailored to alternative ICP
- [ ] Run 5-10 more interviews (est. 1-2 weeks)
- [ ] Final GO/STOP decision
+- [ ] Run 5-10 more interviews (deadline: 1-2 weeks)
+- [ ] Final GO/STOP decision with hard deadline

 **IF STOP decision (<40% interest, no one willing to pay):**
 - [ ] Document learnings (what didn't work, what insights gained)
@ -81,40 +63,39 @@

 ---

-### MVP Development Phase (4-6 weeks)
+### Week 3-8 (Nov 18 - Jan 5, 2026): MVP DEVELOPMENT
 *(Assuming GO decision)*

-**Est. duration: 4-6 weeks total**
-
- **Weeks 1-2:** Core generation pipeline + MCP integration
+**Development timeline (4-6 weeks):**
+- **Week 3-4:** Core generation pipeline + MCP integration
  - REST API endpoints finalized
  - Prompt Enhancement Agent working
  - Image generation with @name references
  - Basic storage + CDN integration
  - **Deliverable:** Working API (generate + upload + references)

- **Week 3:** MCP implementation
+- **Week 5:** MCP implementation
  - MCP server setup (follow spec)
  - Implement 3 tools: banatie_generate, banatie_upload, banatie_list_images
  - Test with Claude Desktop
  - Documentation for MCP usage
  - **Deliverable:** Working MCP integration

- **Week 4:** Transformations + UI refinement
+- **Week 6:** Transformations + UI refinement
  - Image transformation service (Imageflow or Cloudflare)
  - Refine demo UI (code snippets, transformation previews)
  - Dashboard (history, usage stats)
  - API key management
  - **Deliverable:** Functional UI for testing

- **Week 5:** Payments + polish
+- **Week 7:** Payments + polish
  - Stripe integration (credit packs: $20, $50, $100)
  - Free tier limits enforcement (10/month with watermark)
  - Landing page copy + design
  - API documentation (REST + MCP)
  - **Deliverable:** Monetization-ready product

- **Week 6:** Beta testing + iteration
+- **Week 8:** Beta testing + iteration
  - Invite 5-10 validated users from research
  - High-touch onboarding (help with MCP setup)
  - Gather feedback, fix critical bugs
@ -123,21 +104,21 @@

 ---

-### Soft Launch & Growth Phase (Months 3-6 after validation)
+### Month 4-6 (Jan-Mar 2026): SOFT LAUNCH & GROWTH

-**Month 3:** First paying customers
+**Month 4 (Jan):** First paying customers
 - Goal: 5-10 beta users onboarded
 - 50+ generations completed
 - 2+ users purchase credits (willingness to pay validated)
 - Target MRR: $200-500

-**Month 4:** Soft launch to communities
+**Month 5 (Feb):** Soft launch to communities
 - Post in r/ClaudeAI: "Show HN: Generate images from Claude Code via MCP"
 - Indie Hackers build-in-public post
 - Dev.to technical content (tutorial: "Automate image gen in Next.js with Claude Code")
 - Target MRR: $500-1,000

-**Month 5:** Growth optimization
+**Month 6 (Mar):** Growth optimization
 - SEO content (start ranking for "AI image generation API", "Claude Code images")
 - Community building (Discord, Reddit presence)
 - Case studies from early users
@ -145,10 +126,9 @@

 ---

-## 🎯 Long-term Goals (Relative Milestones)
+## 🎯 Long-term Goals (6-12 months)

-### Month 6 Checkpoint: Side Project Validation
-**Timeframe:** ~6 months after validation
+### Month 6: Side Project Validation Checkpoint
 **Success criteria:**
 - MRR: $1-2K
 - Customers: 10-20 paying
@ -159,8 +139,7 @@

 ---

-### Month 9 Checkpoint: Hybrid Mode Decision
-**Timeframe:** ~9 months after validation
+### Month 9: Hybrid Mode Decision
 **Success criteria:**
 - MRR: $3-5K
 - Customers: 30-50 paying
@ -173,8 +152,7 @@

 ---

-### Month 12 Checkpoint: Full-time Leap Evaluation
-**Timeframe:** ~12 months after validation
+### Month 12: Full-time Leap Evaluation
 **Success criteria:**
 - MRR: $6K+ (current salary replacement)
 - OR: 12-month runway saved + high confidence in growth
@ -182,7 +160,7 @@

 **Decision:** Go full-time on Banatie OR continue hybrid

-**Long-term vision (24-36 months from validation):**
+**Long-term vision (24-36 months):**
 - $15-30K MRR: Sustainable solo/small team business
 - Hire 1-2 people (support, marketing, or tech)
 - Consider Ekaterina full-time on admin/ops
@ -191,29 +169,25 @@

 ## 🚦 Decision Gates

-### GATE 1: ICP Validation (ACTIVE - Est. 2 weeks)
-
-**Started:** Oct 31, 2025
+### GATE 1: ICP Validation (Current - Nov 3, 2025)

 **Success criteria (ALL must be met):**
 - 60%+ interviews say "I would use this" (6 out of 10)
 - 40%+ willing to pay $20+ (4 out of 10)
 - 30%+ want early access (3 out of 10)
- **KILLER USE CASE identified:** ONE specific, frequent, expensive pain mentioned by 60%+ respondents (not scattered generic needs)
+- Consistent pain point validated (not scattered)
 - Budget confirmed (they pay for other tools)

 **Possible outcomes:**
 - ✅ **GO** → Build MVP for AI developers (strong signals)
- 🔄 **PIVOT** → Test different ICP (weak signals, add 1-2 weeks)
+- 🔄 **PIVOT** → Test different ICP (weak signals, 1-2 more weeks)
 - 🛑 **STOP** → Shut down or fundamental rethink (no market fit)

-**Review:** Upon completion with @men
+**Review meeting:** Nov 4, 2025 with @men

 ---

-### GATE 2: MVP Launch Readiness (Week 6 of MVP development)
-
-**Timeframe:** ~6-8 weeks after Gate 1 GO decision
+### GATE 2: MVP Launch Readiness (Week 8 - Late Dec 2025)

 **Success criteria:**
 - MCP integration works reliably (95%+ success rate)
@ -224,16 +198,14 @@

 **Possible outcomes:**
 - ✅ **LAUNCH** → Soft launch to r/ClaudeAI, Indie Hackers
- 🔄 **ITERATE** → Add 1-2 weeks for bug fixes, UX improvements
+- 🔄 **ITERATE** → 1-2 more weeks bug fixes, UX improvements
 - 🛑 **PIVOT** → Different approach needed (MCP too complex? Different features?)

-**Review:** Upon completion
+**Review meeting:** Late December 2025

 ---

-### GATE 3: PMF Validation (Month 6 checkpoint)
-
-**Timeframe:** ~6 months after Gate 1 GO decision
+### GATE 3: PMF Validation (Month 6 - March 2026)

 **Success criteria:**
 - $1-2K MRR achieved
@ -247,7 +219,7 @@
 - 🔄 **OPTIMIZE** → Refine product, improve conversion
 - 🛑 **PIVOT/STOP** → No PMF achieved after 6 months, reassess fundamentally

-**Review:** Upon reaching timeframe
+**Review meeting:** April 2026

 ---

@ -301,7 +273,7 @@
 - **Factors:** Building side project while employed, same industry (web dev, AI)
 - **Current exposure:** Public presence needed for marketing (Twitter, LinkedIn, dev.to)
 - **Monitor:** LinkedIn/social mentions, colleague conversations
- **Mitigation strategies:** (see `backlog/06-future-topics-backlog.md` - "свечение фейса")
+- **Mitigation strategies:** (see `06-future-topics-backlog.md` - "свечение фейса")
  - Use separate brand identity (Banatie, not personal)
  - Delay LinkedIn posting until closer to launch
  - Focus on dev.to, Indie Hackers (less employer monitoring)
@ -315,20 +287,19 @@

 **Updated:** Weekly (every Sunday evening)

-### Validation Metrics (Active Sprint)
-**Sprint started:** Oct 31, 2025
+### Validation Metrics (Current Sprint - Oct 20 - Nov 3)
 - Interviews completed: **0 / 10**
 - Positive responses ("I would use"): **- / -**
 - Willing to pay $20+: **- / -**
 - Early access requests: **- / -**

-### Development Metrics (After GO decision)
+### Development Metrics (After validation - Nov+)
 - MVP features completed: **- / 8**
 - Beta users onboarded: **- / 10**
 - Generations completed: **- / 50**
 - Credit purchases: **- / 2**

-### Business Metrics (Post-launch)
+### Business Metrics (Post-launch - Jan+)
 - **MRR:** $0
 - **Paying customers:** 0
 - **Churn rate:** N/A
@ -361,23 +332,23 @@

 ## 📋 Action Items Summary

-**Active Sprint (ICP Validation - Started Oct 31):**
+**This Week (Oct 30 - Nov 3):**
 1. Create throwaway Reddit account
 2. Post validation questions in r/ClaudeAI and r/ChatGPTCoding
 3. Conduct 10 text-based interviews
 4. Document results in validation scorecard
-5. Make GO/PIVOT/STOP decision
+5. Make GO/PIVOT/STOP decision by Nov 3

-**After Validation - IF GO:**
+**Next Week (Nov 4-10) - IF GO:**
 1. Finalize MVP scope based on interview insights
 2. Set up development environment (if not already done)
 3. Begin MCP server implementation
 4. Prepare beta access list

-**After Validation - IF PIVOT:**
+**Next Week (Nov 4-10) - IF PIVOT:**
 1. Select alternative ICP
 2. Prepare new interview script
-3. Begin second validation round (est. 1-2 weeks)
+3. Begin second validation round

 ---

@ -409,8 +380,8 @@
 ---

 **Roadmap Owner:** @men + Oleg (joint ownership)  
-**Last Updated:** October 31, 2025
-**Next Review:** Upon completion of ICP validation
+**Last Review:** October 30, 2025  
+**Next Review:** November 4, 2025 (post-validation decision)  
 **Version Control:** Track major changes via Git commits

 ---
@ -419,5 +390,4 @@
 - Update metrics: Every Sunday evening
 - Review roadmap: After each decision gate
 - Update action items: As completed or priorities change
- Archive completed sprints: When moving to next phase
- Mark tasks complete: Record actual completion dates for velocity tracking
+- Archive completed sprints: Monthly cleanup
--- a/sdd.md
+++ b/sdd.md
@ -0,0 +1,122 @@
+\# Техническая Архитектура и Функциональная Спецификация:
+
+\*\*Banatie AI Asset Generation Platform\*\*
+
+
+
+\### 1. Обзор Платформы (Platform Overview)
+
+
+
+\*\*Banatie\*\* — это API-first платформа для программной генерации и доставки \*\*готовых к использованию (Production-Ready)\*\* медиа-активов. В отличие от традиционных генераторов, Banatie интегрирует возможности передовой AI-генерации (на базе Google Gemini) с полноценным конвейером продакшен-доставки (CDN, хостинг, трансформации).
+
+
+
+Целевая аудитория — разработчики, веб-мастера и создатели SaaS-приложений, которым требуется \*\*комплексное, оптимизированное решение\*\* для автоматизации создания и встраивания контента.
+
+
+
+\### 2. Технический Стек (Technology Stack)
+
+
+
+| Компонент | Технология | Роль в Архитектуре |
+
+| :--- | :--- | :--- |
+
+| \*\*Основная Модель (Core Synthesizer)\*\* | \*\*Gemini 2.5 Flash Image\*\* | Ядро для высокоскоростного синтеза изображений. |
+
+| \*\*Вспомогательные AI Модели (Agents)\*\* | \*\*Gemini 2.5 Flash\*\* (и другие быстрые модели) | \*\*Prompt Enhancement\*\* (оптимизация промптов) и \*\*Asset Analysis\*\* (извлечение метаданных и фокальной точки). |
+
+| \*\*Backend \& API Gateway\*\* | \*\*Express (Node.js)\*\* | Высокопроизводительный REST API-сервер и логика Flow-Based Generation. |
+
+| \*\*Фронтенд \& UI\*\* | \*\*Next.js\*\* | Разработка основного сайта, документации, демонстрационных UI. |
+
+| \*\*Управление Аккаунтами\*\* | \*\*nextjs/saas-starter (Шаблон)\*\* | Основа для архитектуры авторизации, организаций и проектов. |
+
+| \*\*Хранение Аксетов (Object Storage)\*\* | \*\*MinIO (S3-совместимый)\*\* | Первичное, высокодоступное хранилище сгенерированных и загруженных активов. |
+
+| \*\*Трансформация Изображений\*\* | \*\*Imageflow-Server\*\* | Динамическое преобразование активов (ресайзинг, обрезка, формат) через Query Params. |
+
+| \*\*Доставка Контента (CDN)\*\* | \*\*Cloudflare\*\* | Глобальное кэширование и оптимизированная доставка трансформированных изображений. |
+
+| \*\*База Данных\*\* | \*\*PostgreSQL\*\* | Реляционное хранилище для метаданных генераций, пользователей, проектов и биллинга. |
+
+| \*\*Deployment\*\* | \*\*Docker / VPS\*\* | Контейнеризация и размещение сервиса. |
+
+
+
+\### 3. Основной Процесс Генерации и Доставки Аксетов (Core Generation \& Delivery Flow)
+
+
+
+Пайплайн разделен на 6 этапов для обеспечения продакшен-готовности ассетов:
+
+
+
+1\.  \*\*Ввод Пользователя (User Input):\*\* Получение неструктурированного промпта (на любом языке) и дополнительных параметров (стиль, соотношение сторон).
+
+2\.  \*\*Prompt Enhancement (AI-Агент):\*\* Специализированный агент анализирует, переводит и \*\*оптимизирует промпт\*\* (с учетом выбранного стиля и лучших практик Gemini), создавая детализированный, высокоэффективный запрос.
+
+3\.  \*\*Core Image Synthesis:\*\* Оптимизированный промпт отправляется в Gemini API для генерации изображения.
+
+4\.  \*\*Asset Analysis \& Metadata Extraction:\*\* Второй AI-агент анализирует полученное изображение, выделяя \*\*фокальную точку (Focal Point)\*\* и ключевые метаданные, необходимые для корректной автоматической обрезки/трансформации.
+
+5\.  \*\*Asset Persistence \& Indexing:\*\* Изображение сохраняется в MinIO. Метаданные (промпты, параметры, фокальная точка) индексируются в PostgreSQL.
+
+6\.  \*\*Production URL \& Delivery:\*\* Генерируется \*\*постоянный, кэшируемый URL\*\*. При обращении изображение проходит через \*\*Imageflow-Server\*\* (трансформация) и кэшируется в \*\*Cloudflare CDN\*\*. Ответ API также включает набор ходовых трансформированных ссылок (пресетов) для удобной верстки.
+
+
+
+\### 4. Основные Функциональные Особенности (Core Differentiating Features)
+
+
+
+| Feature | Описание | B2D-Ценность |
+
+| :--- | :--- | :--- |
+
+| \*\*4.1. Flow-Based Chained Generation\*\* | Программная последовательность генераций, где каждая новая генерация имеет доступ к контексту и результатам предыдущих шагов Flow. | Позволяет создавать сложные, логически связанные наборы ассетов (итерации персонажей, ассеты для игр). |
+
+| \*\*4.2. On-Demand Generation via URL\*\* | Генерация изображения, инициируемая \*\*GET-запросом к URL\*\* с промптом в Query Params. При повторном запросе возвращается закэшированный ассет. | Обеспечивает возможность LLM-агентам генерировать HTML-страницы с готовыми, оптимизированными изображениями. |
+
+| \*\*4.3. Contextual Asset Referencing\*\* | Возможность присваивать ассетам имена (`@logo`) и использовать эти имена \*\*напрямую в текстовом промпте\*\* для передачи референсных изображений в модель. | Упрощает Inpainting/Outpainting и создание контента с привязкой к бренду или существующим элементам. |
+
+| \*\*4.4. Image Transformation Pipeline\*\* | Динамическое преобразование изображения (ресайзинг, изменение `aspect ratio`, обрезка по фокальной точке, форматы) через Query Params в CDN-ссылке. | Устраняет необходимость ручной обработки изображений, гарантируя оптимальную скорость загрузки и качество на всех устройствах. |
+
+| \*\*4.5. Namespaces и Стили\*\* | Виртуальное разделение активов в проектах с возможностью задания общих системных промптов и стилей для обеспечения \*\*визуальной консистентности\*\*. | Идеально для управления брендбуком или стилистикой разных разделов сайта. |
+
+
+
+\### 5. Каналы Взаимодействия и Авторизация
+
+
+
+\*   \*\*REST API:\*\* Основной канал, обеспечивающий полный доступ ко всем функциям.
+
+\*   \*\*JS/TS SDK:\*\* Высокоуровневая обертка для удобной программной работы с Flow-Based Generation.
+
+\*   \*\*Model Context Protocol (MCP):\*\* \*\*Специализированный API/протокол\*\* для интеграции с LLM и AI-агентами, оптимизированный для контекстуальных и последовательных запросов.
+
+\*   \*\*User Interface (UI):\*\* Веб-интерфейс для тестирования и отладки. Каждая генерация сопровождается \*\*Code Snippets\*\* для API, SDK и MCP.
+
+\*   \*\*Авторизация:\*\* Основана на \*\*API-ключах\*\* (`apikey`). Каждый ключ ассоциирован с парой \*\*Организация/Проект\*\* для контроля доступа и биллинговой изоляции.
+
+
+
+\### 6. Релизная Стратегия (MVP Focus)
+
+
+
+Для первого публичного релиза необходима полная функциональность в следующих ключевых областях:
+
+
+
+1\.  \*\*Ядро Генерации:\*\* Полностью работающий \*\*Prompt Enhancement\*\* и \*\*Asset Persistence\*\*.
+
+2\.  \*\*Доставка:\*\* Рабочий \*\*Image Transformation Pipeline\*\* с CDN, генерирующий \*production-ready\* ссылки.
+
+3\.  \*\*Уникальные Фичи:\*\* \*\*On-Demand Generation via URL\*\* и базовая \*\*Contextual Asset Referencing\*\* (@logo).
+
+4\.  \*\*Авторизация/Биллинг:\*\* Полностью работающая система \*\*API Key\*\* и \*\*Free Tier\*\* с механизмом ограничения лимитов.
+
--- a/strategy/11-technical-architecture.md
+++ b/strategy/11-technical-architecture.md
@ -1,110 +0,0 @@
-# Technical Architecture and Functional Specification
-
-**Date:** 2025-11-01
-**Version:** 1.0
-**Status:** ✅ Validated (current technical architecture)
-**Related docs:** `strategy/07-validated-icp-ai-developers.md`, `execution/09-mvp-scope.md`
-
---
-
-## Platform Overview
-
-**Banatie** is an API-first platform for programmatic generation and delivery of **production-ready** media assets. Unlike traditional generators, Banatie integrates cutting-edge AI generation capabilities (powered by Google Gemini) with a complete production delivery pipeline (CDN, hosting, transformations).
-
-Target audience: Need to be investigated. The working hypothesis: Developers, webmasters, and SaaS creators who need a **comprehensive, optimized solution** for automating content creation and embedding.
-
---
-
-## Technology Stack
-
-| Component | Technology | Role in Architecture |
-|:---|:---|:---|
-| **Core Synthesizer** | **Gemini 2.5 Flash Image** | High-speed image synthesis engine |
-| **AI Agent Models** | **Gemini 2.5 Flash** (and other fast models) | **Prompt Enhancement** (prompt optimization) and **Asset Analysis** (metadata extraction and focal point detection) |
-| **Backend & API Gateway** | **Express (Node.js)** | High-performance REST API server and Flow-Based Generation logic |
-| **Frontend & UI** | **Next.js** | Main website, documentation, demo UIs |
-| **Account Management** | **nextjs/saas-starter (Template)** | Foundation for auth architecture, organizations, and projects |
-| **Object Storage** | **MinIO (S3-compatible)** | Primary, highly-available storage for generated and uploaded assets |
-| **Image Transformation** | **Imageflow-Server** | Dynamic asset transformation (resize, crop, format) via Query Params |
-| **Content Delivery (CDN)** | **Cloudflare** | Global caching and optimized delivery of transformed images |
-| **Database** | **PostgreSQL** | Relational storage for generation metadata, users, projects, and billing |
-| **Deployment** | **Docker / VPS** | Containerization and service hosting |
-
---
-
-## Core Generation & Delivery Flow
-
-The pipeline is divided into **6 stages** to ensure production-ready assets:
-
-### Stage 1: User Input
-Receive unstructured prompt (in any language) and additional parameters (style, aspect ratio).
-
-### Stage 2: Prompt Enhancement (AI Agent)
-Specialized agent analyzes, translates, and **optimizes the prompt** (considering selected style and Gemini best practices), creating a detailed, highly-effective request.
-
-### Stage 3: Core Image Synthesis
-Optimized prompt is sent to Gemini API for image generation.
-
-### Stage 4: Asset Analysis & Metadata Extraction
-Second AI agent analyzes the generated image, identifying the **focal point** and key metadata needed for proper automatic cropping/transformation.
-
-### Stage 5: Asset Persistence & Indexing
-Image is saved to MinIO. Metadata (prompts, parameters, focal point) is indexed in PostgreSQL.
-
-### Stage 6: Production URL & Delivery
-A **permanent, cacheable URL** is generated. On request, the image passes through **Imageflow-Server** (transformation) and is cached in **Cloudflare CDN**. The API response also includes a set of common transformation presets for convenient layout integration.
-
---
-
-## Core Differentiating Features
-
-| Feature | Description | Developer Value |
-|:---|:---|:---|
-| **Flow-Based Chained Generation** | Programmatic sequence of generations where each new generation has access to context and results from previous Flow steps | Enables creation of complex, logically connected asset sets (character iterations, game assets) |
-| **On-Demand Generation via URL** | Image generation triggered by **GET request to URL** with prompt in Query Params. Repeated requests return cached asset | Allows LLM agents to generate HTML pages with ready-made, optimized images |
-| **Contextual Asset Referencing** | Ability to assign names to assets (`@logo`) and use these names **directly in text prompts** to pass reference images to the model | Simplifies Inpainting/Outpainting and content creation tied to brand or existing elements |
-| **Image Transformation Pipeline** | Dynamic image transformation (resize, aspect ratio change, focal point cropping, formats) via Query Params in CDN link | Eliminates manual image processing, ensuring optimal load speed and quality across all devices |
-| **Namespaces & Styles** | Virtual asset separation in projects with ability to set common system prompts and styles for **visual consistency** | Ideal for managing brand guidelines or styling different website sections |
-
---
-
-## Integration Channels
-
-### REST API
-Primary channel providing full access to all features.
-
-### JS/TS SDK
-High-level wrapper for convenient programmatic work with Flow-Based Generation.
-
-### Model Context Protocol (MCP)
-**Specialized API/protocol** for integration with LLMs and AI agents, optimized for contextual and sequential requests.
-
-### User Interface (UI)
-Web interface for testing and debugging. Every generation includes **Code Snippets** for API, SDK, and MCP.
-
-### Authorization
-Based on **API keys** (`apikey`). Each key is associated with an **Organization/Project** pair for access control and billing isolation.
-
---
-
-## MVP Release Strategy
-
-For the first public release, full functionality is required in the following key areas:
-
-### 1. Core Generation
-Fully functional **Prompt Enhancement** and **Asset Persistence**.
-
-### 2. Delivery Pipeline
-Working **Image Transformation Pipeline** with CDN, generating production-ready links.
-
-### 3. Unique Features
-**On-Demand Generation via URL** and basic **Contextual Asset Referencing** (@logo).
-
-### 4. Authorization & Billing
-Fully functional **API Key** system and **Free Tier** with usage limit enforcement.
-
---
-
-**Document owner:** Oleg (technical lead)
-**Last updated:** 2025-11-01
-**Next review:** After ICP validation