neotoma 0.3.0 → 0.3.2

package/docs/releases/archived/aspirational/v1.0.0/pre_launch_marketing_plan.md

@@ -1,748 +0,0 @@
-## Release v1.0.0 — Build-in-Public Content Plan
-
-### Purpose
-This document defines build-in-public content activities for v1.0.0 during the build phase (dogfooding-first approach). Focus is on technical thought leadership, community engagement, and reactive content to industry announcements, plus a developer preview release during dogfooding with precision disclaimers.
-
-**Key Changes from Original Pre-Launch Marketing Plan:**
-- ❌ **Removed**: Waitlist building, early access beta, formal pre-launch marketing
-- ✅ **Added**: Build-in-public content, reactive content to industry announcements, MCP ecosystem engagement
-- ✅ **Added**: Developer preview release during dogfooding with precision disclaimers
-- ✅ **Reframed**: Technical thought leadership instead of product marketing
-- ✅ **Timeline**: Week 0-12 (during build), not Week -4 to Week 0 (before build)
-- ✅ **Approach**: Building for personal use (ateles integration), sharing learnings
-
-**Related Documents:**
-- `marketing_plan.md` — Marketing overview and coordination
-- `post_launch_marketing_plan.md` — Post-launch marketing activities (deferred until after dogfooding)
-- `marketing_segments_plan.md` — User segment definitions
-- `marketing_metrics_plan.md` — Metrics and tracking
-- `marketing_dogfooding_analysis.md` — Analysis of pre-launch marketing for dogfooding-first approach
-- `visibility_timing_analysis.md` — Visibility timing risk and build-in-public strategy
-
-### 1. Build-in-Public Overview
-- **Timeline**: Week 0-12 (during build + dogfooding)
-- **Strategy**: Strategic build-in-public content (technical thought leadership, not product marketing)
-- **Goals**: Technical credibility, thought leadership positioning, community engagement, visibility during industry announcements
-- **Developer Preview**: Release during dogfooding once core invariants are stable
-- **No Waitlist or Beta**: Just sharing learnings and preview access, not marketing
-- **Approach**: Building for personal use (ateles integration), sharing what I'm learning
-### 2. Build-in-Public Content Strategy
-
-#### 2.1 Overview
-- **Timeline**: Week 0-12 (ongoing during build + dogfooding)
-- **Channels**: Personal Twitter/X (@markymark), Personal LinkedIn, Personal Website/Blog, Indie Hackers, Hacker News
-- **Target Segments**: AI-Native Individual Operators, High-Context Knowledge Workers, MCP ecosystem
-- **Platform Priority**: P0 platforms (Twitter, Indie Hackers, Hacker News) for technical content; aligns with AI-Native Individual Operators segment
-- **Strategy**: Authentic build-in-public content (technical learnings, not product marketing)
-- **No Waitlist/Beta**: Just sharing, not marketing
-#### 2.2 Personal Twitter/X Account (@markymark)
-**Timeline**: Week 0-12 (ongoing during build)
-**Profile Setup** (Week 0):
-- [ ] Update bio: "Building Neotoma — Privacy-first truth layer for AI memory | MCP integration | Building for ateles integration"
-- [ ] Pin tweet: Build-in-public announcement (no waitlist link, just sharing journey)
-- [ ] Add Neotoma website link in bio (if website exists)
-- [ ] Add location/company info if relevant
-
-**Weekly Posting Schedule** (Flexible, reactive to industry announcements):
-**Regular Content** (Weekly):
-- **Monday**: Technical thread — "Why deterministic extraction matters" (4-5 tweets)
-- **Wednesday**: Architecture thread — "How I'm building Neotoma: Records → Entities → Events" (6-7 tweets)
-- **Friday**: Build-in-public update — Progress update, screenshots, learnings from ateles integration
-
-**Reactive Content** (When industry announcements happen):
-- **Within 24-48 hours**: Respond to industry announcements (OpenAI, Anthropic, Google, MCP ecosystem)
-- **Technical analysis**: "Here's what [competitor] announced, here's why it doesn't solve [problem]"
-- **Positioning**: "I'm building Neotoma to solve [problem] differently"
-- **No CTA**: Just thought leadership, not marketing
-
-**Content Themes**:
-- Problem/solution framing (from personal experience)
-- Technical deep-dives (determinism, MCP, entity resolution)
-- Build-in-public updates (ateles integration learnings)
-- Privacy-first positioning
-- Architecture decisions (why I'm making specific choices)
-- Reactive content (responding to industry announcements)
-**Daily Engagement**:
-- Reply to comments on threads (within 24 hours)
-- Engage with MCP ecosystem discussions (value-first, not promotional)
-- Retweet/share relevant AI memory discussions
-- Answer questions about Neotoma/MCP authentically
-- Monitor industry announcements (OpenAI, Anthropic, Google, MCP ecosystem)
-
-**Thread Structure Template** (Build-in-Public):
-1. Hook tweet (problem/insight from building)
-2. Problem expansion (2-3 tweets)
-3. How I'm solving it (1-2 tweets)
-4. Technical details (2-3 tweets)
-5. What I'm learning (1-2 tweets)
-6. Engagement question (no CTA, just discussion)
-#### 2.3 Personal Website/Blog
-**Timeline**: Week 0-12 (ongoing during build)
-**Website Setup** (Week 0):
-- [ ] Create/update personal website landing page with Neotoma section
-- [ ] Add "Building Neotoma" section to homepage
-- [ ] Create blog section (if not exists)
-- [ ] **No waitlist signup form** (building for personal use, not ready for external users)
-- [ ] Add Neotoma logo/branding
-- [ ] Set up analytics (Google Analytics or Plausible)
-
-**Blog Content Schedule** (Flexible, reactive to learnings):
-**Technical Deep-Dives** (Monthly, ~2-3 posts):
-- [ ] **Post 1**: "Why I'm Building Neotoma: The Problem with AI Memory"
-  - Personal story (ateles integration use case)
-  - Problem statement (from building experience)
-  - Why existing solutions don't work
-  - What I'm building to solve it
-  - **No CTA**: Just sharing learnings
-  - ~1500 words
-
-- [ ] **Post 2**: "Deterministic Extraction: Why It Matters for Personal Data"
-  - Technical deep-dive on determinism vs. ML-based extraction
-  - Why reproducibility matters (from building experience)
-  - Examples and use cases (from ateles integration)
-  - **No CTA**: Just technical insights
-  - ~2000 words
-
-- [ ] **Post 3**: "Building a Truth Layer: Neotoma's Architecture"
-  - Four-layer truth model (Document → Entity → Observation → Snapshot)
-  - Entity resolution (how I'm implementing it)
-  - Timeline generation (architectural decisions)
-  - MCP integration (patterns I'm discovering)
-  - **No CTA**: Just architectural insights
-  - ~2500 words
-
-- [ ] **Post 4**: "Privacy-First AI Memory: Why User Control Matters"
-  - Privacy-first architecture (why I'm building it this way)
-  - Comparison with provider-controlled models
-  - User control benefits (from building perspective)
-  - **No CTA**: Just thought leadership
-  - ~1500 words
-
-**Reactive Content** (When industry announcements happen):
-- Respond to competitor announcements with technical analysis
-- "Why [competitor approach] doesn't solve [problem]" posts
-- **No CTA**: Just thought leadership
-**Blog Post Promotion**:
-- Share each post on Twitter/X with thread summary
-- Share on LinkedIn with professional framing
-- Share on Indie Hackers (if relevant)
-- Share on Hacker News (if technical enough)
-- Include in email newsletter (if exists)
-- **No waitlist CTAs**: Just sharing technical content
-**SEO Optimization**:
-- Target keywords: "AI memory", "MCP integration", "deterministic extraction", "privacy-first AI"
-- Internal linking between posts
-- External links to MCP docs, relevant resources
-- Meta descriptions optimized
-- Open Graph tags for social sharing
-#### 2.4 Personal LinkedIn Account
-**Timeline**: Week 0-12 (ongoing during build)
-**Profile Setup** (Week 0):
-- [ ] Update headline: "Building Neotoma | Privacy-First Truth Layer for AI Memory | Building for ateles integration"
-- [ ] Add Neotoma to experience section
-- [ ] Update "About" section to mention Neotoma (building for personal use)
-- [ ] Add Neotoma website link (if website exists)
-- [ ] Add skills: MCP, AI Memory, Privacy-First Architecture
-
-**Weekly Posting Schedule** (Flexible, ~2 posts/month):
-- **Technical posts**: "Deterministic vs. ML-Based Extraction: A Technical Comparison"
-- **Thought leadership**: "Why Privacy-First Architecture Matters for AI Tools"
-- **Build-in-public**: "What I'm Learning Building Neotoma for My Ateles Integration"
-- **Architecture insights**: "MCP Integration Patterns I'm Discovering"
-- **No beta or waitlist announcements**: Developer preview release is the only announcement during dogfooding
-**Post Format**:
-- Professional tone
-- 300-500 words
-- Include relevant hashtags (#AI #MCP #Privacy #Tech #BuildInPublic)
-- Link to blog post (no waitlist links)
-- Engage with comments
-**Engagement Strategy**:
-- Comment thoughtfully on AI/tech posts
-- Share relevant industry news with Neotoma angle (thought leadership)
-- Engage with High-Context Knowledge Workers segment
-- Join relevant LinkedIn groups
-- **No promotional content**: Just technical insights and learnings
-#### 2.5 Indie Hackers Personal Account
-**Timeline**: Week 0-12 (ongoing during build)
-**Profile Setup** (Week 0):
-- [ ] Verify Indie Hackers account exists
-- [ ] Update profile with Neotoma info
-- [ ] Create product page for Neotoma (optional, can defer)
-- [ ] Add Neotoma logo, description, website link (if website exists)
-- [ ] **No waitlist link**: Building for personal use, not ready for external users
-
-**Weekly Posting Schedule** (Weekly progress updates):
-- **Monday**: Build-in-public post — "Week X: Building Neotoma for Ateles Integration"
-  - What I built this week
-  - Challenges faced
-  - Learnings (determinism, MCP integration, entity resolution)
-  - Screenshots/demos (if available)
-  - **No waitlist link**: Just sharing progress
-**Post Format**:
-- Build-in-public style
-- Honest about challenges
-- Share progress (technical milestones, not user metrics)
-- Include screenshots/demos (if available)
-- Engage with community comments
-- **No waitlist/beta mentions**: Just sharing journey
-
-**Community Engagement**:
-- Comment on other builders' posts
-- Answer questions in community
-- Share learnings and insights
-- Support other indie hackers
-- **No promotional content**: Just authentic build-in-public sharing
-#### 2.6 Hacker News Personal Account
-**Timeline**: Week 0-12 (ongoing during build)
-**Account Setup** (Week 0):
-- [ ] Verify HN account exists and is active
-- [ ] Build karma by commenting thoughtfully on relevant threads
-- [ ] Identify relevant "Ask HN" threads to engage with
-
-**Ongoing Engagement** (Week 0-12):
-- Comment on AI memory discussions
-- Share insights on MCP, deterministic extraction (from building experience)
-- Answer questions authentically (not promotional)
-- Build reputation as helpful community member
-- **Show HN when developer preview is ready**: Post during dogfooding with precision disclaimers
-**Comment Strategy**:
-- Provide value, not promotion
-- Share technical insights when relevant (from building experience)
-- Answer questions authentically
-- Build karma and reputation
-- Avoid promotional comments
-- **No product pitches**: Just helpful technical contributions
-#### 2.7 Cross-Platform Promotion
-**Website → Social**:
-- Share blog posts on Twitter/X with thread summary
-- Share blog posts on LinkedIn with professional framing
-- Share blog posts on Indie Hackers if relevant
-- Include social share buttons on blog posts
-**Social → Website**:
-- Link to blog posts in Twitter threads
-- **No waitlist links**: Just technical content
-- Include website link in all social bios (if website exists)
-- Drive traffic from social to website (for technical content)
-**Social → Social**:
-- Cross-post between Twitter/X and LinkedIn (adapted for platform)
-- Share Indie Hackers posts on Twitter/X
-- Share Twitter threads on LinkedIn (if relevant)
-**Email → All**:
-- If email newsletter exists, include blog posts
-- Share social media updates
-- Drive to website (for technical content, not waitlist)
-#### 2.8 Personal Brand Leverage
-**Existing Network**:
-- Leverage existing Twitter/X followers
-- Leverage LinkedIn connections
-- Leverage personal website/blog audience (if exists)
-- Leverage Indie Hackers community relationships
-**Authenticity**:
-- Share personal journey building Neotoma
-- Be honest about challenges
-- Show behind-the-scenes development
-- Build trust through transparency
-**Consistency**:
-- Consistent messaging across platforms
-- Consistent branding (Neotoma logo, colors)
-- Consistent posting schedule
-- Consistent voice and tone
-**Note**: All social media activities use personal accounts (see `marketing_plan.md` Section 2.6 for personal vs. company account strategy)
-#### 2.3 Goals
-- Technical credibility
-- Community engagement
-- Developer preview framing and expectation setting
-- Actionable feedback from preview users
-#### 2.4 Metrics
-| Metric                    | Target | Tracking                          |
-| ------------------------- | ------ | --------------------------------- |
-| Social engagement rate    | 3%     | Twitter analytics, blog analytics |
-| Demo video views          | 500    | YouTube/Twitter video views       |
-| Preview feedback items    | 10     | Manual tracking                   |
-| Preview inquiry messages  | 20     | Manual tracking                   |
-### 3. Reactive Content to Industry Announcements
-
-#### 3.1 Overview
-- **Timeline**: Week 0-12 (reactive, as announcements happen)
-- **Strategy**: Respond to industry announcements within 24-48 hours
-- **Goal**: Capture visibility during industry announcement windows (3-5x engagement)
-
-#### 3.2 Monitoring
-- **Set up alerts**: OpenAI, Anthropic, Google, MCP ecosystem announcements
-- **Monitor channels**: Twitter, LinkedIn, GitHub, Discord, Reddit
-- **Track competitors**: Supermemory.ai, MemCP, Mem0, provider memory features
-
-#### 3.3 Response Framework
-**When Industry Announcement Happens:**
-1. **Immediate Analysis** (Day 1):
-   - What did they announce?
-   - What problem does it solve?
-   - What problem does it NOT solve? (your opportunity)
-   - How does Neotoma approach it differently?
-
-2. **Content Creation** (Day 1-2):
-   - Technical thread on Twitter (5-7 tweets)
-   - Blog post (if significant announcement)
-   - Community engagement (comments, discussions)
-
-3. **Positioning**:
-   - "I'm building Neotoma to solve [problem they didn't solve]"
-   - "Here's why [their approach] doesn't work for [use case]"
-   - "Here's how I'm approaching it differently"
-
-4. **No CTA**:
-   - Just thought leadership, not marketing
-   - No waitlist, no beta, no product pitch
-   - Just valuable insights
-
-#### 3.4 Example Response Timeline
-- **Day 1, 10am**: OpenAI announces structured memory
-- **Day 1, 2pm**: Your Twitter thread: "OpenAI's memory is provider-controlled. I'm building Neotoma for user-controlled, deterministic memory. Here's why it matters..."
-- **Day 2**: Blog post: "Why Provider-Controlled Memory Doesn't Solve the Privacy Problem"
-- **Day 3**: Community engagement: Comments on relevant discussions, answer questions
-
-**Result**: High visibility during industry announcement window, establishes thought leadership
-
-#### 3.5 Goals
-- Capture visibility during industry announcement windows
-- Establish thought leadership positioning
-- Technical credibility
-- Community engagement
-
-#### 3.6 Metrics
-| Metric                          | Target | Tracking                                    |
-| ------------------------------- | ------ | ------------------------------------------- |
-| Industry announcement responses | 3-5    | Manual tracking (announcements responded to) |
-| Engagement on reactive content  | 3-5x   | Twitter analytics (vs. scheduled content)    |
-| Community mentions              | 20     | Manual tracking (Discord, Reddit mentions)  |
-### 4. MCP Ecosystem Engagement
-
-#### 4.1 Timeline and Targets
-- **Timeline**: Week 0-12 (ongoing during build)
-- **Target Ecosystem**: MCP community, AI tool communities, relevant technical communities
-- **Platforms**: Twitter/X, LinkedIn, Reddit, Discord, GitHub
-- **Target Segments**: AI-Native Individual Operators, MCP developers, AI tool users
-
-#### 4.2 Engagement Strategy
-**Approach**: Value-first engagement, not promotional spam
-**Activities**:
-1. **Monitor MCP Ecosystem**
-   - Follow MCP-related accounts on Twitter
-   - Join relevant Discord servers (AI tool communities, MCP communities)
-   - Monitor Reddit communities (r/ChatGPT, r/ClaudeAI, r/Cursor, r/MCP)
-   - Track GitHub repositories for MCP memory tools
-   - Monitor MCP directory updates
-
-2. **Authentic Engagement**
-   - Comment thoughtfully on MCP-related posts (provide value, not promotion)
-   - Answer questions in Discord/Reddit where relevant
-   - Share insights about MCP integration patterns (from building experience)
-   - Build reputation as helpful community member
-
-3. **Technical Contributions**
-   - Share MCP integration patterns you're discovering
-   - Answer questions about MCP server development
-   - Contribute to MCP ecosystem discussions
-   - **No product pitches**: Just technical insights
-
-4. **Content Sharing**
-   - Share technical blog posts/tweets in relevant discussions
-   - Reference Neotoma when discussing MCP integration patterns (from building experience)
-   - Provide technical insights when users ask about MCP development
-
-#### 4.3 Goals
-- Ecosystem visibility (MCP community awareness)
-- Community engagement (helpful contributions)
-- Technical credibility (MCP integration expertise)
-- **No waitlist signups**: Just community engagement
-
-#### 4.4 Metrics
-| Metric                          | Target | Tracking                                    |
-| ------------------------------- | ------ | ------------------------------------------- |
-| MCP ecosystem engagements       | 50     | Manual tracking (comments, replies, shares) |
-| Community mentions              | 20     | Manual tracking (Discord, Reddit mentions)  |
-| Technical contributions         | 10     | Manual tracking (helpful answers, insights) |
-### 5. Personal Network Engagement (Optional)
-
-#### 5.1 Timeline and Targets
-- **Timeline**: Week 0-12 (optional, low priority)
-- **Targets**: Friends, professional contacts, former colleagues, industry connections
-- **Platforms**: GitHub, Twitter/X, LinkedIn
-- **Goal**: Share build-in-public journey, not ask for support
-
-#### 5.2 GitHub Stars (Optional, Low Priority)
-**Timeline**: Week 0-12 (optional)
-**Targets**:
-- Friends and family in tech
-- Former colleagues and coworkers
-- Professional network contacts
-- Industry connections (developers, founders, investors)
-
-**Engagement Strategy** (Not Outreach):
-1. **Share Build-in-Public Updates** (Ongoing)
-   - Include GitHub link in build-in-public posts
-   - Share progress updates with network
-   - **No explicit ask**: Just sharing journey
-
-2. **Social Media Sharing** (Ongoing)
-   - Post build-in-public updates on Twitter/X
-   - Share on LinkedIn with professional framing
-   - Include GitHub link in posts
-   - **No explicit ask**: Just sharing progress
-**Social Media Post Template** (No Explicit Ask):
-```
-Building Neotoma for my ateles integration - a privacy-first truth layer for AI memory 🧠
-Sharing progress and learnings as I build: https://github.com/neotoma/neotoma
-#BuildInPublic #AI #MCP
-```
-
-**Goals**:
-- Share build-in-public journey with network
-- Build awareness (not explicit support requests)
-- **No waitlist/beta**: Just sharing progress
-
-**Metrics** (Low Priority):
-| Metric                    | Target | Tracking                      |
-| ------------------------- | ------ | ----------------------------- |
-| Network engagement        | N/A    | Social media analytics        |
-| Network awareness         | N/A    | Manual tracking               |
-#### 5.3 Social Media Follows Outreach
-**Timeline**: Week -4 to Week 0
-**Targets**:
-- Friends and family
-- Professional contacts
-- Former colleagues
-- Industry connections
-- Alumni networks
-**Outreach Strategy**:
-1. **Twitter/X Follows** (@markymark)
-   - Personal messages asking friends to follow @markymark
-   - Share Neotoma updates and build-in-public content
-   - Ask for retweets/shares of important threads
-   - Include in email signatures and LinkedIn profile
-2. **LinkedIn Follows**
-   - Update LinkedIn profile with Neotoma info
-   - Post about building Neotoma
-   - Ask professional network to follow for updates
-   - Share build-in-public posts
-3. **Cross-Platform Promotion**
-   - Link Twitter/X in LinkedIn posts
-   - Link LinkedIn in Twitter/X bio
-   - Include social links in email signatures
-   - Add social links to personal website
-**Message Templates**:
-**Personal Message (Twitter/X)**:
-```
-Hey [Name],
-I'm building Neotoma and sharing updates on Twitter. Would love if you'd follow @markymark for build-in-public updates!
-- Mark
-```
-**LinkedIn Post**:
-```
-I'm building Neotoma - a privacy-first truth layer for AI memory.
-Follow along for build-in-public updates and insights on AI memory, MCP integration, and privacy-first architecture.
-#BuildInPublic #AI #MCP
-```
-**Goals**:
-- Increase Twitter/X followers from personal network
-- Increase LinkedIn connections/engagement
-- Build audience for launch day announcements
-- Create early supporters and advocates
-**Metrics**:
-| Metric                              | Target | Tracking                      |
-| ----------------------------------- | ------ | ----------------------------- |
-| Twitter/X followers from network    | 30     | Twitter analytics             |
-| LinkedIn connections from network   | 20     | LinkedIn analytics            |
-| Network engagement rate             | 5%     | Social media analytics        |
-| Network to waitlist conversion rate | 5%     | UTM tracking (network source) |
-#### 5.4 Outreach Schedule
-**Week -4**:
-- Send personal messages to close contacts (GitHub stars + social follows)
-- Update LinkedIn profile with Neotoma info
-- Update email signature with Neotoma links
-**Week -3**:
-- Send email to professional network (GitHub stars + social follows)
-- Post on LinkedIn asking for follows
-- Share Twitter/X handle in professional communications
-**Week -2**:
-- Follow-up with contacts who haven't responded
-- Post on Twitter/X asking for GitHub stars
-- Share build-in-public updates with network
-**Week -1**:
-- Final push for GitHub stars before launch
-- Remind network about upcoming launch
-- Ask for launch day support (shares, upvotes)
-**Week 0**:
-- Launch day: Ask network for Product Hunt upvotes, HN upvotes
-- Share launch announcement with network
-- Thank network for early support
-#### 5.5 Best Practices
-**Do**:
-- Personalize messages (use names, reference relationship)
-- Explain what Neotoma is and why it matters
-- Make it easy (include direct links)
-- Thank people for support
-- Follow up with updates
-**Don't**:
-- Spam or send bulk messages
-- Be pushy or aggressive
-- Ask for too much (one ask per message)
-- Forget to thank supporters
-- Over-promote (balance with value)
-**Follow-Up**:
-- Thank people who star/follow
-- Share updates with supporters
-- Keep network informed of progress
-- Ask for feedback from network
-- Convert network supporters to beta testers
-### 6. MCP Directory Listings (Deferred)
-
-#### 6.1 Timeline and Targets
-- **Timeline**: **Deferred until after dogfooding validation** (Week 12+)
-- **Rationale**: Product must work for ateles integration before submitting to directories
-- **Target Directories** (Prepare for post-dogfooding):
-  - **Primary MCP Directories**:
-    - [Model Context Protocol Directory](https://model-context-protocol.com/) — Official MCP directory
-    - [Open MCP Directory](https://www.openmcpdirectory.com/) — Comprehensive daily-updated listing
-    - [MCP Store](https://www.mcpstore.site/) — Curated MCP servers and clients
-    - [MCP Ecosystem Directory](https://mcpez.com/) — 11,790+ MCP servers repository
-    - [MCP Index](https://mcpindex.net/) — Curated collection with real-time updates
-    - [MCP Curator](https://www.mcpcurator.com/) — 846+ MCP tools organized by category
-    - [MCP Directory](https://directorymcp.com/) — Centralized resource listing
-    - [MCP Server Directory](https://www.mcpdirectory.info/) — Browse/search/filter platform
-    - [MCP Server Directory](https://mcpserverdirectory.org/) — 2,500+ MCP resources
-    - [FindMCPs](https://findmcps.com/) — Comprehensive discovery platform
-
-#### 6.2 Preparation (During Build Phase)
-**Week 0-12** (Optional preparation):
-- Research submission requirements for each directory
-- Prepare Neotoma MCP server listing materials (for future use)
-- Ensure MCP server is functional and documented (for ateles integration)
-- Test MCP integration with Claude Desktop, Cursor, ChatGPT (for ateles integration)
-
-#### 6.3 Submission Strategy (Post-Dogfooding)
-**Week 12+** (After dogfooding validation, if proceeding):
-- Submit to MCP directories (now that product is validated)
-- Update listings with working product information
-- Monitor directory traffic/referrals
-#### 6.4 Submission Requirements (For Post-Dogfooding)
-**Common Requirements**:
-- MCP server name and description
-- Category/classification
-- Features and capabilities
-- Website/GitHub links
-- Documentation link
-- Installation/setup instructions
-- Example use cases
-- Tags/keywords
-
-**Neotoma-Specific Materials** (Prepare during build):
-- **Description**: "Privacy-first deterministic truth layer that transforms personal documents into structured memory for AI agents via MCP. Features schema-first extraction, entity resolution, timeline generation, and cross-platform access (ChatGPT, Claude, Cursor)."
-- **Key Features**:
-  - Privacy-first architecture (user-controlled, no provider access)
-  - Deterministic schema-first extraction
-  - Entity resolution across documents
-  - Timeline generation from date fields
-  - MCP integration (ChatGPT, Claude, Cursor)
-  - Dual-path ingestion (file uploads + agent interactions)
-- **Use Cases**: Personal document memory, invoice/receipt tracking, contract management, cross-platform AI memory
-- **Tags**: privacy-first, deterministic, entity-resolution, timelines, mcp-integration, personal-data, memory
-
-#### 6.5 Goals (Post-Dogfooding)
-- Increase visibility in MCP ecosystem
-- Generate referral traffic from directory listings
-- Establish Neotoma as recognized MCP server
-- Build backlinks for SEO
-- Reach AI-Native Individual Operators discovering MCP tools
-
-#### 6.6 Metrics (Post-Dogfooding)
-| Metric                      | Target | Tracking                             |
-| --------------------------- | ------ | ------------------------------------ |
-| Directory listings approved | 8      | Manual tracking (submission status)  |
-| Directory referral traffic  | 100    | Website analytics (referral sources) |
-| Directory to signup rate    | 2%     | UTM tracking (directory source)      |
-### 7. Technical Content (Build-in-Public)
-
-#### 7.1 Timeline and Formats
-- **Timeline**: Week 0-12 (ongoing during build)
-- **Formats**: Blog posts (on personal website), demo videos (optional), Twitter threads, LinkedIn posts
-- **Distribution**: Personal accounts and website
-- **Focus**: Technical thought leadership, not product marketing
-
-#### 7.2 Content Pieces
-**Blog Posts** (on personal website, flexible schedule):
-- "Why I'm Building Neotoma: The Problem with AI Memory" (from building experience)
-- "Deterministic Extraction: Why It Matters for Personal Data" (technical deep-dive)
-- "Building a Truth Layer: Neotoma's Architecture" (architectural decisions)
-- "Privacy-First AI Memory: Why User Control Matters" (thought leadership)
-- "MCP Integration Patterns: Lessons from Building Neotoma" (technical insights)
-- **Developer Preview Announcement**: Short announcement with precision disclaimers and explicit mutation guarantees
-- **Why Neotoma Exists**: Separate post that frames the problem and constraints, no feature list
-
-**Demo Videos** (Optional, if time permits):
-- **Title**: "Building Neotoma: Ateles Integration Progress"
-- **Length**: 2-3 minutes
-- **Content**: Screen recording showing ateles integration, MCP query workflow
-- **Platforms**: YouTube (unlisted initially), Twitter/X, LinkedIn, embed on website
-- **Timeline**: Flexible, when significant progress made
-- **No product pitch**: Just showing what you're building
-
-**Twitter Threads** (Weekly):
-- "The problem with semantic search" (from building experience)
-- "How I'm building Neotoma (architecture)" (technical insights)
-- "Privacy-first architecture explained" (thought leadership)
-- "MCP integration patterns I'm discovering" (technical learnings)
-
-**LinkedIn Posts** (Monthly):
-- Professional versions of blog posts
-- Thought leadership content
-- Technical insights from building
-#### 7.3 Content Distribution Strategy
-**Blog Posts**:
-- Publish on personal website
-- Share on Twitter/X with thread summary
-- Share on LinkedIn with professional framing
-- Share on Indie Hackers (if relevant)
-- Include in email newsletter (if exists)
-- Add to website blog archive
-- **No waitlist CTAs**: Just technical content
-
-**Demo Videos** (If created):
-- Upload to YouTube (unlisted initially, make public when ready)
-- Share on Twitter/X with thread
-- Share on LinkedIn
-- Embed on website (if website exists)
-- Embed in blog posts
-- Share on Indie Hackers
-- **No product pitch**: Just showing what you're building
-
-**Twitter Threads**:
-- Post on @markymark
-- Pin important threads (technical insights, not marketing)
-- Cross-post summary to LinkedIn
-- Link to blog posts for deeper dive
-- **No waitlist CTAs**: Just technical content
-
-**LinkedIn Posts**:
-- Post on personal LinkedIn account
-- Share blog post links
-- Professional framing
-- Engage with comments
-- **No promotional content**: Just technical insights
-
-#### 7.4 Goals
-- Technical credibility
-- Thought leadership positioning
-- Community engagement
-- Visibility during industry announcements
-- **No waitlist conversion**: Just sharing learnings
-
-#### 7.5 Metrics
-| Metric                    | Target                                 | Tracking                                 |
-| ------------------------- | -------------------------------------- | ---------------------------------------- |
-| Blog post views           | 2000 (across all posts)                | Website analytics                        |
-| Demo video views          | 500 (if created)                       | YouTube analytics, Twitter analytics     |
-| Content shares            | 50 (organic shares)                    | Social share counts                      |
-| Twitter thread engagement | 3% engagement rate                     | Twitter analytics                        |
-| LinkedIn post engagement  | 2% engagement rate                     | LinkedIn analytics                       |
-| **No waitlist metrics**: Just content engagement
-### 8. Success Criteria
-
-**Build-in-Public Content**:
-- Technical credibility established (thought leadership positioning)
-- Community engagement (MCP ecosystem, relevant discussions)
-- Visibility during industry announcements (reactive content gets 3-5x engagement)
-- No premature commitments (no waitlist/beta expectations)
-
-**Content Performance**:
-- ≥2000 blog post views (across all posts)
-- ≥500 demo video views (if created)
-- ≥50 content shares (organic)
-- ≥3% Twitter/X engagement rate
-- ≥2% LinkedIn engagement rate
-
-**MCP Ecosystem Engagement**:
-- ≥50 MCP ecosystem engagements (comments, replies, shares)
-- ≥20 community mentions (Discord, Reddit)
-- ≥10 technical contributions (helpful answers, insights)
-
-**Reactive Content**:
-- ≥3-5 industry announcement responses (within 24-48 hours)
-- 3-5x engagement on reactive content (vs. scheduled content)
-
-**Personal Brand**:
-- Increase Twitter/X followers by 10% (from existing base)
-- Increase LinkedIn connections by 5% (from existing base)
-- Establish Neotoma as recognized project in AI memory space
-- Build reputation as helpful community member
-
-**No Waitlist/Beta Metrics**: Just content engagement and community participation
-### 9. Agent-Based Automation (Optional)
-
-#### 9.1 Content Generation Automation
-**Strategy**: Use AI agents (Claude/ChatGPT via MCP or direct API) to generate content drafts based on build-in-public schedule.
-**Agent Workflow**:
-1. **Weekly Schedule Reading**
-   - Agent reads build-in-public content plan
-   - Identifies content needs for upcoming week (Twitter threads, blog posts, LinkedIn posts)
-   - Creates content generation tasks
-
-2. **Content Generation**
-   - Agent generates content drafts following templates and brand guidelines
-   - Uses build progress data for context
-   - Outputs platform-specific formats (Twitter threads, blog posts, LinkedIn posts)
-   - **No waitlist CTAs**: Just technical content
-
-3. **Content Review** (Human-in-the-loop)
-   - Review generated content for quality and brand voice
-   - Approve or request revisions
-   - Store approved content for publishing
-
-**Agent Instructions**:
-- Follow brand voice: technical, authentic, privacy-first, build-in-public
-- Lead with defensible differentiators (privacy-first, deterministic, cross-platform)
-- Use thread structure templates (no CTAs)
-- **No waitlist links**: Just technical content
-- Maintain consistency across platforms
-
-**Content Templates for Agents**:
-- Twitter thread template (5-7 tweets, hook → problem → how I'm solving it → technical details → what I'm learning)
-- Blog post template (1500-2500 words, intro → body → conclusion, no CTA)
-- LinkedIn post template (300-500 words, professional tone, no CTA)
-- Build-in-public update template (honest, progress, learnings)
-
-**MVP Approach**:
-- Use Claude/ChatGPT directly (via MCP or web interface) to generate content drafts
-- Provide agent with build progress and technical learnings
-- Review and approve generated content before publishing
-- Manual publishing (automated publishing in post-MVP)
-
-**Time Savings**:
-- Content generation: ~70% time reduction (from 15 hours/month to ~5 hours/month)
-- Agent generates drafts, human reviews and publishes
-- Focus human time on review, refinement, and community engagement
-
-#### 9.2 Scheduling Automation (Post-MVP)
-**Future**: Automated scheduling and publishing agents (see `marketing_automation_plan.md`)
-### 10. Budget
-- **Total**: $0 (organic only)
-- **Time Investment**: ~10-15 hours/month (build-in-public content, not marketing)
-  - Agent content generation: ~2 hours (prompting, reviewing, refining)
-  - Twitter/X threads: ~3 hours (agent drafts + review + publishing)
-  - Blog posts: ~4 hours (agent drafts + review + editing + publishing, monthly)
-  - Demo video: ~3 hours (optional, if time permits)
-  - LinkedIn posts: ~1 hour (agent drafts + review + publishing, monthly)
-  - Indie Hackers posts: ~1 hour (weekly updates)
-  - Website updates: ~2 hours (setup, optimization)
-  - Community engagement: ~3 hours (MCP ecosystem, relevant discussions)
-  - Reactive content: ~2-3 hours per industry announcement (as needed)
-  - MCP directory preparation: ~1 hour (optional, for post-dogfooding)
-- **Agent Costs**: ~$10-20/month (Claude/ChatGPT API for content generation)
-### 11. Related Documents
-- `marketing_plan.md` — Marketing overview and coordination
-- `post_launch_marketing_plan.md` — Post-launch marketing activities (deferred until after dogfooding)
-- `marketing_segments_plan.md` — User segment definitions
-- `marketing_metrics_plan.md` — Metrics and tracking
-- `marketing_dogfooding_analysis.md` — Analysis of pre-launch marketing for dogfooding-first approach
-- `visibility_timing_analysis.md` — Visibility timing risk and build-in-public strategy
-- `approach_comparison.md` — Discovery-first vs. dogfooding-first comparative analysis