neotoma 0.3.0 → 0.3.2

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

@@ -1,130 +0,0 @@
-## Release v1.0.0 — Execution Schedule
-**Note:** This schedule assumes discovery is complete (Week -8 to -5) and go decision made. For discovery planning, see `discovery_plan.md` and related discovery documents.
-**Estimation Methodology:** See `docs/conventions/estimation_methodology.md` for velocity-based estimation approach. Estimates revised Dec 11, 2025 based on v0.1.0 actual velocity (26 FUs in 2-3 days).
-### Batches Overview
-Batching is derived from the dependency graph in `manifest.yaml`. All FUs in the same batch can execute **in parallel**; batches must execute **in order**.
-#### Batch 0 — No Dependencies
-- **Feature Units**:
-  - `FU-100` — File Analysis Service Update
-  - `FU-300` — Design System Implementation
-  - `FU-700` — Authentication UI
-- **Depends On**: _none_
-- **Notes**:
-  - FU-100 is critical-path for ingestion/extraction.
-  - FU-300 and FU-700 can proceed independently in parallel.
-#### Batch 1 — Depend on FU-100
-- **Feature Units**:
-  - `FU-101` — Entity Resolution Service
-  - `FU-102` — Event Generation Service
-- **Depends On**:
-  - `FU-100`
-- **Notes**:
-  - Both require extraction outputs from FU-100.
-  - Can execute in parallel once FU-100 is complete.
-#### Batch 2 — Depend on FU-101 + FU-102
-- **Feature Units**:
-  - `FU-103` — Graph Builder Service
-- **Depends On**:
-  - `FU-101`
-  - `FU-102`
-- **Notes**:
-  - Consolidates Records, Entities, and Events into transactional graph inserts.
-#### Batch 3 — Depend on FU-103 and/or FU-700
-- **Feature Units**:
-  - `FU-105` — Search Service (Deterministic Ranking)
-  - `FU-701` — RLS Implementation
-- **Depends On**:
-  - `FU-103` (for `FU-105`)
-  - `FU-700` (for `FU-701`)
-- **Notes**:
-  - `FU-105` must see stable graph; `FU-701` secures data once auth exists.
-### Suggested Parallelization
-**Assumptions:**
-- All timeline estimates assume Cursor agent execution (not human developers)
-- Cloud agents execute in parallel via Cursor Background Agents API (see `docs/feature_units/standards/multi_agent_orchestration.md`)
-- Execution limits: `max_parallel_fus: 3`, `max_high_risk_in_parallel: 1`
-**With Cloud Agent Parallelization (max 3 agents):**
-**Estimation Methodology:** Based on v0.1.0 actual velocity (26 FUs completed in 2-3 days = ~8-13 FUs/day). Estimates account for existing foundation and agent parallelization.
-**Note:** FU-100, FU-101, FU-102, FU-103, FU-105 are already complete from v0.1.0. Only FU-300, FU-700, and FU-701 require new work.
-- **Phase 1 (Batch 0)** — Estimated: 1 day
-  - Cloud Agents: `FU-100` ✅ (already complete), `FU-300` (0.5 days design system polish), `FU-700` (0.5-1 day auth UI) in parallel
-  - **Bottleneck**: FU-700 (longest in batch)
-  - **Timeline**: Day 0-1
-  - **Note**: FU-100 already complete from v0.1.0 (rule-based extraction implemented)
-- **Phase 2 (Batch 1)** — Estimated: 0 days
-  - Cloud Agents: `FU-101` ✅ (already complete), `FU-102` ✅ (already complete)
-  - **Timeline**: Day 0 (no work needed)
-  - **Note**: Both FUs already complete from v0.1.0
-- **Phase 3 (Batch 2)** — Estimated: 0 days
-  - Sequential: `FU-103` ✅ (already complete)
-  - **Timeline**: Day 0 (no work needed)
-  - **Note**: FU-103 already complete from v0.1.0
-- **Phase 4 (Batch 3)** — Estimated: 1-2 days
-  - Cloud Agents: `FU-105` ✅ (already complete), `FU-701` (1-2 days RLS implementation) in parallel
-  - **Bottleneck**: FU-701 (only work item in batch)
-  - **Timeline**: Day 1-2
-  - **Note**: FU-105 already complete from v0.1.0. FU-701 requires migration, RLS policies, service updates, and MCP action updates.
-**Total Estimated Development Time**: 2-3 days (with cloud agent parallelization)
-**Rationale:** v0.1.0 demonstrated 26 FUs in 2-3 days. v1.0.0 requires only 3 new FUs (FU-300 polish, FU-700 auth UI, FU-701 RLS), with remaining FUs already complete.
-**Overall Timeline** (as of December 12, 2025):
-**Parallel Pre-Development Phase (3-4 weeks):**
-- **Week 0** (Dec 12-19, 2025): Build discovery lead sourcing tools, configure API credentials, begin discovery recruitment
-- **Week 1-4** (Dec 19, 2025 - Jan 9, 2026): **Discovery AND Pre-launch marketing in parallel** (3-4 weeks)
-  
-  **Discovery Activities (parallel):**
-  - Week 1 (Dec 19-26): Execute lead sourcing tools, launch screening survey, begin recruitment
-  - Week 1-3 (Dec 19 - Jan 2): Value discovery interviews (13 participants)
-  - Week 2-3 (Dec 26 - Jan 2): Usability discovery testing (8 participants)
-  - Week 3-4 (Jan 2-9): Business viability discovery interviews (8 participants)
-  
-  **Pre-Launch Marketing Activities (parallel):**
-  - Week 1-4 (Dec 19 - Jan 9): Waitlist building campaigns (Twitter, email, community, content)
-  - Week 2-4 (Dec 26 - Jan 9): Early access beta signups (invite discovery participants + waitlist top users)
-  - Week 3-4 (Jan 2-9): Content teasers (blog posts, demo videos, Twitter threads)
-  - Week 3-4 (Jan 2-9): Feature teaser emails to existing users (if any)
-- **Week 5** (Jan 9-16, 2026): Discovery synthesis + Marketing finalization (1 week)
-  - Discovery synthesis, go/no-go decision, scope refinement
-  - Marketing metrics review, waitlist quality assessment
-  - Finalize pre-launch marketing materials
-**Development Phase (1-2 weeks):**
-- **Week 6** (Jan 16-23, 2026): Development execution (2-3 days with cloud agents) + Cross-release integration testing (3-5 days)
-- **Week 7** (Jan 23-30, 2026): Pre-release sign-off, staging deployment, production deployment (Day 0, adjustable based on testing)
-**Post-Launch Phase:**
-- **Week 7-11** (Jan 30 - Feb 27, 2026): Post-launch marketing and validation (4 weeks)
-**Target Ship Date**: January 23-30, 2026 (Week 7, adjustable based on discovery findings and testing)
-**Note:** Discovery and pre-launch marketing run in parallel (Week 1-4), reducing total pre-development time from 5-6 weeks to 4-5 weeks. Development starts immediately after both complete (Week 6).
-### Checkpoints
-- **Checkpoint 0 (Planning)**: This schedule is generated and approved before execution.
-- **Checkpoint 1 (Mid-Release Review)**:
-  - Configured after **Batch 1** (see `manifest.yaml`).
-  - Occurs once `FU-100`, `FU-101`, and `FU-102` complete and initial integration tests pass.
-- **Checkpoint 2 (Pre-Release Sign-Off)**:
-  - After all batches complete and full integration suite passes.
-### Integration Tests per Batch (High-Level)
-- **After Batch 0** (Day 1):
-  - Basic ingestion smoke tests (FU-100) ✅:
-    - Already validated in v0.1.0
-  - Visual/UI-level checks for design system (FU-300):
-    - Component rendering tests
-    - Responsive layout validation
-  - Basic auth flow tests (sign up / login) for FU-700:
-    - Signup flow
-    - Login flow
-    - Password reset flow
-  **Continuous Discovery**: 2-3 user interviews on upload experience
-- **After Batch 1** (Day 0):
-  - Ingestion → extraction → entity resolution → event generation path ✅:
-    - Already validated in v0.1.0 (IT-001 through IT-011 passing)
-  **Mid-Release Checkpoint (Checkpoint 1)**: Review progress, validate integration
-  **Continuous Discovery**: Prototype testing with 3-5 users on entity/event views
-- **After Batch 2** (Day 0):
-  - Graph integrity ✅:
-    - Already validated in v0.1.0 (IT-004 passing, 0 orphans/cycles)
-  **Continuous Discovery**: 2-3 user interviews on timeline/graph views
-- **After Batch 3** (Day 2-3):
-  - End-to-end flows:
-    - Upload → extraction → graph → search → UI → MCP ✅ (validated in v0.1.0)
-    - Multi-user flows with RLS enforced (new for v1.0.0)
-    - All IT-001 through IT-005 from `integration_tests.md` ✅ (IT-001 through IT-011 already passing)
-  **Continuous Discovery**: Beta testing with discovery participants
-See `integration_tests.md` for detailed test definitions.

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

@@ -1,116 +0,0 @@
-## Release v1.0.0 — Feasibility Validation Plan
-### Purpose
-This document defines the feasibility validation activities for v1.0.0, focused on validating that OCR determinism is achievable with pinned tesseract version and explicit low-confidence handling.
-**Related Documents:**
-- `discovery_plan.md` — Discovery overview and coordination
-- `value_discovery_plan.md` — Value discovery activities
-- `release_plan.md` — Release overview and scope
-### 1. Hypothesis and Assumptions
-**Hypothesis:** "OCR determinism is achievable with pinned tesseract version and explicit low-confidence handling"
-**Assumptions:**
-- Tesseract v5.3.0 produces identical output for identical images
-- PDF rendering to images is deterministic
-- Low-confidence OCR results can be flagged and surfaced to user
-- Rule-based extraction can achieve >85% schema detection accuracy
-- MCP server can provide reliable, structured access to extracted data
-### 2. Validation Method
-**Method**: Technical proof of concept (no participants needed)
-**Timeline**: Week -8 to Week -7
-### 3. Validation Tests
-#### Test 1: OCR Reproducibility Test
-**Description**: Run same PDF through OCR 100 times
-**Success Criteria**: 100% identical text output
-**Measurement**: Text output comparison across runs
-**Test Procedure:**
-1. Select representative PDFs from test corpus
-2. Run each PDF through OCR 100 times
-3. Compare text output across all runs
-4. Verify 100% identical output for each document
-#### Test 2: Low-Confidence Flagging Test
-**Description**: Test low-quality scans with known ground truth
-**Success Criteria**: Low-confidence flags appear where text differs from ground truth
-**Measurement**: Flag accuracy ≥85%
-**Test Procedure:**
-1. Use low-quality scanned documents with known ground truth
-2. Run OCR and flag low-confidence regions
-3. Compare flagged regions to actual differences from ground truth
-4. Calculate flag accuracy (correctly flagged / total differences)
-#### Test 3: Multi-Page Document Test
-**Description**: Test multi-page financial statements, contracts
-**Success Criteria**: Extraction produces identical structured data on repeated runs
-**Measurement**: Structured data comparison across runs
-**Test Procedure:**
-1. Select multi-page documents (financial statements, contracts)
-2. Run extraction 10 times for each document
-3. Compare structured data output across runs
-4. Verify 100% identical structured data for each document
-#### Test 4: Schema Detection Accuracy
-**Description**: Test rule-based schema detection on representative documents
-**Success Criteria**: >85% schema detection accuracy
-**Measurement**: Correct schema type assigned / Total documents
-**Test Procedure:**
-1. Use test corpus with known document types (contracts, receipts, invoices, travel bookings)
-2. Run schema detection on all documents
-3. Compare detected schema to actual document type
-4. Calculate accuracy (correct detections / total documents)
-#### Test 5: MCP Query Performance
-**Description**: Test MCP server query latency and reliability
-**Success Criteria**: P95 query latency < 500ms, 99.9% uptime
-**Measurement**: Query response times, error rates
-**Test Procedure:**
-1. Set up MCP server with test data
-2. Run 1000 queries with varying complexity
-3. Measure response times (P50, P95, P99)
-4. Monitor error rates and uptime
-5. Verify P95 < 500ms and 99.9% uptime
-### 4. Test Corpus
-**Documents Required:**
-- 20+ representative documents (PDFs, images, CSVs)
-- Mix of document types (contracts, receipts, invoices, travel bookings)
-- Mix of quality (high-quality scans, low-quality scans, digital PDFs)
-- Multi-page documents included
-**Test Corpus Selection:**
-- Include edge cases (poor quality scans, unusual formats)
-- Include common document types from Tier 1 ICP workflows
-- Ensure diversity in document structure and content
-### 5. Success Criteria
-- 100% OCR output reproducibility on test corpus (20+ documents, 100 runs each)
-- Low-confidence flagging accuracy ≥85%
-- Extraction determinism verified on representative documents
-- Schema detection accuracy >85%
-- Performance targets met (<5s P95 upload latency, <500ms P95 MCP query latency)
-- MCP server reliability ≥99.9%
-### 6. Timeline
-**Timeline**: Week -8 to Week -7
-**Schedule:**
-- Week -8 (Days 1-2): Set up test environment, prepare test corpus
-- Week -8 (Days 3-4): Run OCR reproducibility tests (Test 1)
-- Week -8 (Days 5-7): Run low-confidence flagging tests (Test 2)
-- Week -7 (Days 1-2): Run multi-page document tests (Test 3)
-- Week -7 (Days 3-4): Run schema detection accuracy tests (Test 4)
-- Week -7 (Days 5-7): Run MCP query performance tests (Test 5), synthesize results
-### 7. Deliverable
-**Deliverable**: `feasibility_validation.md`
-Includes:
-- Test results for each validation test
-- OCR reproducibility results (100% or identify failures)
-- Low-confidence flagging accuracy results
-- Schema detection accuracy results
-- MCP performance metrics
-- Identified issues and blockers
-- Recommendations for implementation
-- Comparison against success criteria
-### 8. Risk Assessment
-**High-Risk Areas:**
-- OCR reproducibility failure would require alternative OCR solution or defer PDF support
-- Schema detection accuracy <85% would require refinement of rule-based extraction
-- MCP performance issues would require optimization or architectural changes
-**Mitigation:**
-- Test early (Week -8) to identify blockers before development starts
-- Have backup plans (alternative OCR engines, different schema detection approach)
-- Document findings clearly to inform implementation decisions
-### 9. Related Documents
-- `discovery_plan.md` — Discovery overview and coordination
-- `value_discovery_plan.md` — Value discovery activities
-- `release_plan.md` — Release overview and scope
-- `pre_mortem.md` — Failure mode analysis (Failure Mode 4: OCR Determinism)

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

@@ -1,263 +0,0 @@
-## v1.0.0 Handle Registration
-### Purpose
-Track registration status for domain names, social media handles, and platform accounts required for v1.0.0 marketing activities.
-### Priority Handles
-**Target Name**: `neotoma` (primary), fallbacks: `neotomaio`, `useneotoma`, `neotomahq`, `neotomaco`
-### 1. Domain Names
-**Priority**: P0 (Required for launch)
-| Domain         | Status       | Owner             | Registrar | Cost         | Notes                         |
-| -------------- | ------------ | ----------------- | --------- | ------------ | ----------------------------- |
-| neotoma.com    | ✗ TAKEN      | Unknown (privacy) | -         | -            | Registered, privacy protected |
-| neotoma.app    | ✗ TAKEN      | Unknown           | -         | -            | Registered, not available     |
-| neotoma.ai     | ✓ AVAILABLE  | -                 | -         | ~$74-89/year | Available for registration    |
-| neotoma.io     | ✓ REGISTERED | Mark Hendrickson  | -         | -            | Already owned                 |
-| getneotoma.com | ✓ AVAILABLE  | -                 | -         | ~$10-15/year | Available for registration    |
-| useneotoma.com | ✓ AVAILABLE  | -                 | -         | ~$10-15/year | Available for registration    |
-**Recommendation**: Use `neotoma.io` as primary domain (already owned). Optionally register `neotoma.ai` for AI-specific positioning.
-**Action Items:**
-- [x] Check availability for all priority domains
-- [x] Primary domain already owned (neotoma.io)
-- [ ] Configure DNS for neotoma.io
-- [ ] Configure email forwarding for neotoma.io
-- [ ] Optionally register neotoma.ai for AI positioning
-- [ ] Set up domain privacy/WHOIS protection (if not already enabled)
-### 2. Social Media Handles
-#### 2.1 Twitter/X (P0)
-**Justification**: Primary marketing platform per `marketing_plan.md`
-| Handle      | Status    | Owner        | Notes                                                    |
-| ----------- | --------- | ------------ | -------------------------------------------------------- |
-| @neotoma    | ✗ TAKEN   | George McCoy | Inactive account (0 following, 3 followers, joined 2007) |
-| @neotomaio  | ? Unknown | -            | Not checked (references .io domain)                      |
-| @useneotoma | ? Unknown | -            | Not checked                                              |
-| @neotomahq  | ? Unknown | -            | Not checked                                              |
-| @neotomaco  | ? Unknown | -            | Not checked                                              |
-| @getneotoma | ✗ TAKEN   | Unknown      | Account exists                                           |
-**Recommendation**: Check and register `@neotomaio` (references owned domain) or `@useneotoma` immediately. Consider reaching out to @neotoma owner to purchase/acquire handle.
-**Action Items:**
-- [ ] Check handle availability
-- [ ] Register primary handle
-- [ ] Complete profile setup (bio, avatar, header image)
-- [ ] Verify account (if possible)
-- [ ] Configure OAuth for marketing automation
-#### 2.2 LinkedIn (P1)
-**Justification**: Secondary platform for High-Context Knowledge Workers segment
-| Type         | Handle/URL         | Status      | Owner            | Notes                         |
-| ------------ | ------------------ | ----------- | ---------------- | ----------------------------- |
-| Company Page | /company/neotoma   | ✓ AVAILABLE | -                | Page doesn't exist, available |
-| Company Page | /company/neotomaio | ? Unknown   | -                | Not checked                   |
-| Personal     | (Mark's existing)  | ✓ Active    | Mark Hendrickson | Use for personal posts        |
-**Recommendation**: Register `/company/neotoma` company page.
-**Action Items:**
-- [ ] Check company page availability
-- [ ] Create company page
-- [ ] Complete company profile (description, logo, cover image, website)
-- [ ] Link to Mark's personal account
-#### 2.3 Instagram (P2)
-**Justification**: Lower priority, but useful for brand consistency
-| Handle      | Status    | Owner | Notes                                                       |
-| ----------- | --------- | ----- | ----------------------------------------------------------- |
-| @neotoma    | ? Unclear | -     | Not publicly accessible (deleted, unregistered, or private) |
-| @neotomaio  | ? Unknown | -     | Not checked                                                 |
-| @useneotoma | ? Unknown | -     | Not checked                                                 |
-**Recommendation**: Attempt to register `@neotoma` first, fallback to `@neotomaio` or `@useneotoma` if unavailable.
-**Action Items:**
-- [ ] Check handle availability
-- [ ] Register primary handle
-- [ ] Complete profile setup
-- [ ] Reserve but defer active use until post-v1.0.0
-#### 2.4 Facebook (P2)
-**Justification**: Low priority, brand consistency only
-| Type | Handle/URL | Status        | Owner | Notes    |
-| ---- | ---------- | ------------- | ----- | -------- |
-| Page | /neotoma   | ☐ Not checked | -     | Primary  |
-| Page | /neotomaio | ☐ Not checked | -     | Fallback |
-**Action Items:**
-- [ ] Check page availability
-- [ ] Create page
-- [ ] Reserve but defer active use until post-v1.0.0
-### 3. Developer Platforms
-#### 3.1 GitHub (P0)
-**Justification**: Already in use, ensure org/repo naming consistency
-| Type         | Handle  | Status       | Owner            | Notes        |
-| ------------ | ------- | ------------ | ---------------- | ------------ |
-| Organization | neotoma | ✓ Registered | Mark Hendrickson | Current org  |
-| Repository   | neotoma | ✓ Registered | neotoma org      | Current repo |
-**Action Items:**
-- [x] Organization registered
-- [ ] Update org profile (bio, website, logo)
-- [ ] Update repo description and README
-- [ ] Add topics/tags for discoverability
-#### 3.2 npm (P1)
-**Justification**: Package distribution (if applicable)
-| Package Name  | Status        | Owner | Notes          |
-| ------------- | ------------- | ----- | -------------- |
-| neotoma       | ☐ Not checked | -     | Primary        |
-| @neotoma/core | ☐ Not checked | -     | Scoped package |
-**Action Items:**
-- [ ] Check package name availability
-- [ ] Register npm organization (@neotoma)
-- [ ] Reserve package names (defer publishing until ready)
-### 4. Community Platforms
-#### 4.1 Reddit (P1)
-**Justification**: Community engagement on AI tool subreddits
-| Type      | Handle      | Status      | Owner | Notes                                          |
-| --------- | ----------- | ----------- | ----- | ---------------------------------------------- |
-| User      | u/neotoma   | ✓ AVAILABLE | -     | Username doesn't exist, available              |
-| User      | u/neotomaio | ? Unknown   | -     | Not checked                                    |
-| Subreddit | r/neotoma   | ? Unknown   | -     | Not checked (subreddit separate from username) |
-**Recommendation**: Register `u/neotoma` username immediately.
-**Action Items:**
-- [ ] Check username availability
-- [ ] Register primary username
-- [ ] Build karma before launch (participate in AI tool communities)
-- [ ] Defer subreddit creation until post-v1.0.0
-#### 4.2 Discord (P1)
-**Justification**: Community server for users
-| Type       | Handle   | Status              | Owner | Notes                  |
-| ---------- | -------- | ------------------- | ----- | ---------------------- |
-| Server     | Neotoma  | ☐ Not created       | -     | Community server       |
-| Vanity URL | /neotoma | ☐ Not available yet | -     | Requires server boosts |
-**Action Items:**
-- [ ] Create Discord server
-- [ ] Set up channels and roles
-- [ ] Configure moderation and rules
-- [ ] Defer active promotion until post-launch
-#### 4.3 Product Hunt (P0)
-**Justification**: Launch day platform
-| Type          | Status        | Owner            | Notes                |
-| ------------- | ------------- | ---------------- | -------------------- |
-| Maker Account | ☐ Not checked | Mark Hendrickson | Use personal account |
-| Product Page  | Not created   | -                | Create on launch day |
-**Action Items:**
-- [ ] Verify Mark's maker account exists
-- [ ] Build maker reputation (hunt/upvote other products)
-- [ ] Prepare product assets (logo, screenshots, video)
-- [ ] Schedule launch date
-#### 4.4 Hacker News (P0)
-**Justification**: Launch day platform ("Show HN")
-| Type         | Status        | Owner            | Notes                |
-| ------------ | ------------- | ---------------- | -------------------- |
-| User Account | ☐ Not checked | Mark Hendrickson | Use personal account |
-**Action Items:**
-- [ ] Verify Mark's HN account exists and is active
-- [ ] Build karma (comment on relevant threads)
-- [ ] Prepare "Show HN" post
-#### 4.5 Indie Hackers (P0)
-**Justification**: Primary launch platform
-| Type         | Status        | Owner            | Notes                |
-| ------------ | ------------- | ---------------- | -------------------- |
-| User Account | ☐ Not checked | Mark Hendrickson | Use personal account |
-| Product Page | Not created   | -                | Create pre-launch    |
-**Action Items:**
-- [ ] Verify Mark's IH account exists
-- [ ] Build reputation (engage in community)
-- [ ] Create product page
-- [ ] Post build-in-public updates
-### 5. Email Services
-**Priority**: P0 (Required for transactional emails)
-| Service         | Handle/Domain      | Status         | Owner | Notes                |
-| --------------- | ------------------ | -------------- | ----- | -------------------- |
-| Email Domain    | @neotoma.io        | Pending config | -     | Primary email domain |
-| Support Email   | support@neotoma.io | Pending config | -     | Support inbox        |
-| No-Reply Email  | noreply@neotoma.io | Pending config | -     | Transactional emails |
-| Marketing Email | Mark's personal    | -              | Mark  | Pre-launch campaigns |
-**Action Items:**
-- [ ] Configure email service (e.g., SendGrid, Postmark)
-- [ ] Set up transactional email templates
-- [ ] Configure SPF, DKIM, DMARC records
-- [ ] Test email deliverability
-### 6. Analytics & Tracking
-**Priority**: P1 (Required for metrics)
-| Service             | Handle/Property      | Status      | Owner | Notes                       |
-| ------------------- | -------------------- | ----------- | ----- | --------------------------- |
-| Google Analytics    | neotoma.com property | Not created | -     | Web analytics               |
-| Plausible Analytics | neotoma.com          | Not created | -     | Privacy-focused alternative |
-**Action Items:**
-- [ ] Choose analytics platform
-- [ ] Create property/site
-- [ ] Configure UTM tracking for marketing campaigns
-- [ ] Set up goal tracking (signups, uploads, activation)
-### 7. Registration Priority Order
-**Phase 1 (Immediate - Week -4 to Week -2):**
-1. Domain name (primary + fallback)
-2. Twitter/X handle
-3. GitHub profile updates
-4. Email configuration
-5. Indie Hackers product page
-**Phase 2 (Pre-Launch - Week -2 to Week 0):**
-6. LinkedIn company page
-7. Product Hunt maker profile
-8. Hacker News account prep
-9. Reddit username
-10. Analytics setup
-**Phase 3 (Post-Launch - Week 1+):**
-11. Discord server
-12. Instagram handle
-13. Facebook page
-14. npm package names
-15. Subreddit (deferred)
-### 8. Budget Estimate
-| Item              | Cost         | Frequency | Notes                |
-| ----------------- | ------------ | --------- | -------------------- |
-| Domain names (x4) | ~$50-200     | Annual    | .com, .app, .ai, .io |
-| Email service     | $0-10        | Monthly   | Free tier initially  |
-| Analytics         | $0           | -         | Use free tiers       |
-| Social media      | $0           | -         | Free accounts        |
-| **Total Year 1**  | **~$50-200** | -         | Domain names only    |
-### 9. Handle Registration Log
-**Format**: `YYYY-MM-DD - [Handle] - [Status] - [Owner] - [Notes]`
-**Availability Check Results (2025-12-11):**
-- neotoma.com - TAKEN (privacy protected)
-- neotoma.app - TAKEN
-- neotoma.ai - **AVAILABLE** (~$74-89/year)
-- neotoma.io - **ALREADY OWNED** (registered)
-- getneotoma.com - **AVAILABLE** (~$10-15/year)
-- useneotoma.com - **AVAILABLE** (~$10-15/year)
-- @neotoma (Twitter) - TAKEN (inactive account, 3 followers)
-- @neotomaio (Twitter) - Not checked
-- @useneotoma (Twitter) - Not checked
-- @getneotoma (Twitter) - TAKEN
-- /company/neotoma (LinkedIn) - **AVAILABLE**
-- @neotoma (Instagram) - Unclear (not publicly accessible)
-- u/neotoma (Reddit) - **AVAILABLE**
-_No registrations completed yet. Update this section as handles are registered._
-### 10. Status
-- **Current Status**: Primary domain owned, social handles ready for registration
-- **Owner**: Mark Hendrickson
-- **Next Steps**:
-  1. ✓ Check domain availability (completed 2025-12-11)
-  2. ✓ Check social handle availability (completed 2025-12-11)
-  3. ✓ Primary domain already owned: `neotoma.io`
-  4. **Configure DNS for `neotoma.io`** (immediate action required)
-  5. **Configure email for `neotoma.io`** (immediate action required)
-  6. **Register Twitter handle: `@neotomaio` or `@useneotoma`** (immediate action required)
-  7. **Register LinkedIn company page: `/company/neotoma`** (immediate action required)
-  8. **Register Reddit username: `u/neotoma`** (immediate action required)
-  9. Attempt Instagram registration: `@neotoma`
-  10. Complete social profile setup (bios, logos, links)
-  11. Optionally register `neotoma.ai` for AI positioning
-### 11. Recommended Registration Package
-**Immediate (This Week):**
-1. ✓ **neotoma.io** - Primary domain (already owned)
-2. **Configure DNS for neotoma.io** - Point to hosting
-3. **Configure email for neotoma.io** - Set up transactional email
-4. **@neotomaio** or **@useneotoma** - Twitter handle (free)
-5. **u/neotoma** - Reddit username (free)
-6. **/company/neotoma** - LinkedIn company page (free)
-**Total Cost**: $0 (primary domain already owned)
-**Optional Registrations:**
-- **neotoma.ai** - AI-specific positioning (~$74-89/year)
-- **useneotoma.com** - Alternative/redirect (~$10-15/year)
-**Optional Acquisition:**
-- Consider reaching out to @neotoma (Twitter) owner to purchase handle
-- Consider reaching out to neotoma.com owner to purchase domain (likely expensive)
-**Phase 2 (After Initial Setup):**
-7. Set up DNS records (SPF, DKIM, DMARC)
-8. Instagram (@neotoma or @neotomaio/@useneotoma fallback)
-9. Product Hunt maker profile setup
-10. Hacker News account prep
-### 11. Related Documents
-- `marketing_plan.md` — Platform prioritization and marketing strategy
-- `pre_launch_marketing_plan.md` — Pre-launch activities requiring handles
-- `post_launch_marketing_plan.md` — Post-launch activities requiring handles
-- `deployment_strategy.md` — Domain and infrastructure configuration

package/docs/releases/archived/aspirational/v1.0.0/implementation_logs/FU-100_implementation_log.md

@@ -1,51 +0,0 @@
-# Implementation Decision Log: FU-100
-**Generated:** 2025-12-14T06:22:10.625Z
-## Overview
-This log documents implementation decisions made for FU-100 and how each requirement from the specification was addressed.
-## Implementation Decisions
-### Decision 1: Rule-based schema detection (regex patterns per schema type)
-**Requirement:** Rule-based schema detection (regex patterns per schema type)
-**Location:** Neotoma MVP Feature Units — Execution Plan > Execution Order and Dependencies > Phase 1: Core Services (Domain Layer) > FU-100: File Analysis Service, line 345
-**Type:** must
-**Category:** implementation
-**Implementation approach:** [To be filled during implementation]
-**Files changed:** [To be filled during implementation]
-**Code references:** [To be filled during implementation]
-**Verification:** [To be filled during compliance check]
-**Status:** ⏳ Pending
-### Decision 2: Rule-based field extraction (regex parsers per schema)
-**Requirement:** Rule-based field extraction (regex parsers per schema)
-**Location:** Neotoma MVP Feature Units — Execution Plan > Execution Order and Dependencies > Phase 1: Core Services (Domain Layer) > FU-100: File Analysis Service, line 346
-**Type:** must
-**Category:** implementation
-**Implementation approach:** [To be filled during implementation]
-**Files changed:** [To be filled during implementation]
-**Code references:** [To be filled during implementation]
-**Verification:** [To be filled during compliance check]
-**Status:** ⏳ Pending
-### Decision 3: PDFDocument fallback (not custom sanitized types)
-**Requirement:** PDFDocument fallback (not custom sanitized types)
-**Location:** Neotoma MVP Feature Units — Execution Plan > Execution Order and Dependencies > Phase 1: Core Services (Domain Layer) > FU-100: File Analysis Service, line 347
-**Type:** must
-**Category:** implementation
-**Implementation approach:** [To be filled during implementation]
-**Files changed:** [To be filled during implementation]
-**Code references:** [To be filled during implementation]
-**Verification:** [To be filled during compliance check]
-**Status:** ⏳ Pending
-### Decision 4: code changes to comply with manifest**
-**Requirement:** code changes to comply with manifest**
-**Location:** Neotoma MVP Feature Units — Execution Plan > Detailed Documentation References, line 1789
-**Type:** must
-**Category:** implementation
-**Implementation approach:** [To be filled during implementation]
-**Files changed:** [To be filled during implementation]
-**Code references:** [To be filled during implementation]
-**Verification:** [To be filled during compliance check]
-**Status:** ⏳ Pending
-## Summary
-- **Total Requirements:** 4
-- **Implemented:** 0
-- **Partially Implemented:** 0
-- **Not Implemented:** 4
-- **Deferred:** 0

package/docs/releases/archived/aspirational/v1.0.0/implementation_logs/FU-101_implementation_log.md

@@ -1,51 +0,0 @@
-# Implementation Decision Log: FU-101
-**Generated:** 2025-12-14T06:22:10.682Z
-## Overview
-This log documents implementation decisions made for FU-101 and how each requirement from the specification was addressed.
-## Implementation Decisions
-### Decision 1: Rule-based schema detection (regex patterns per schema type)
-**Requirement:** Rule-based schema detection (regex patterns per schema type)
-**Location:** Neotoma MVP Feature Units — Execution Plan > Execution Order and Dependencies > Phase 1: Core Services (Domain Layer) > FU-100: File Analysis Service, line 345
-**Type:** must
-**Category:** implementation
-**Implementation approach:** [To be filled during implementation]
-**Files changed:** [To be filled during implementation]
-**Code references:** [To be filled during implementation]
-**Verification:** [To be filled during compliance check]
-**Status:** ⏳ Pending
-### Decision 2: Rule-based field extraction (regex parsers per schema)
-**Requirement:** Rule-based field extraction (regex parsers per schema)
-**Location:** Neotoma MVP Feature Units — Execution Plan > Execution Order and Dependencies > Phase 1: Core Services (Domain Layer) > FU-100: File Analysis Service, line 346
-**Type:** must
-**Category:** implementation
-**Implementation approach:** [To be filled during implementation]
-**Files changed:** [To be filled during implementation]
-**Code references:** [To be filled during implementation]
-**Verification:** [To be filled during compliance check]
-**Status:** ⏳ Pending
-### Decision 3: PDFDocument fallback (not custom sanitized types)
-**Requirement:** PDFDocument fallback (not custom sanitized types)
-**Location:** Neotoma MVP Feature Units — Execution Plan > Execution Order and Dependencies > Phase 1: Core Services (Domain Layer) > FU-100: File Analysis Service, line 347
-**Type:** must
-**Category:** implementation
-**Implementation approach:** [To be filled during implementation]
-**Files changed:** [To be filled during implementation]
-**Code references:** [To be filled during implementation]
-**Verification:** [To be filled during compliance check]
-**Status:** ⏳ Pending
-### Decision 4: code changes to comply with manifest**
-**Requirement:** code changes to comply with manifest**
-**Location:** Neotoma MVP Feature Units — Execution Plan > Detailed Documentation References, line 1789
-**Type:** must
-**Category:** implementation
-**Implementation approach:** [To be filled during implementation]
-**Files changed:** [To be filled during implementation]
-**Code references:** [To be filled during implementation]
-**Verification:** [To be filled during compliance check]
-**Status:** ⏳ Pending
-## Summary
-- **Total Requirements:** 4
-- **Implemented:** 0
-- **Partially Implemented:** 0
-- **Not Implemented:** 4
-- **Deferred:** 0

package/docs/releases/archived/aspirational/v1.0.0/implementation_logs/FU-102_implementation_log.md

@@ -1,51 +0,0 @@
-# Implementation Decision Log: FU-102
-**Generated:** 2025-12-14T06:22:10.739Z
-## Overview
-This log documents implementation decisions made for FU-102 and how each requirement from the specification was addressed.
-## Implementation Decisions
-### Decision 1: Rule-based schema detection (regex patterns per schema type)
-**Requirement:** Rule-based schema detection (regex patterns per schema type)
-**Location:** Neotoma MVP Feature Units — Execution Plan > Execution Order and Dependencies > Phase 1: Core Services (Domain Layer) > FU-100: File Analysis Service, line 345
-**Type:** must
-**Category:** implementation
-**Implementation approach:** [To be filled during implementation]
-**Files changed:** [To be filled during implementation]
-**Code references:** [To be filled during implementation]
-**Verification:** [To be filled during compliance check]
-**Status:** ⏳ Pending
-### Decision 2: Rule-based field extraction (regex parsers per schema)
-**Requirement:** Rule-based field extraction (regex parsers per schema)
-**Location:** Neotoma MVP Feature Units — Execution Plan > Execution Order and Dependencies > Phase 1: Core Services (Domain Layer) > FU-100: File Analysis Service, line 346
-**Type:** must
-**Category:** implementation
-**Implementation approach:** [To be filled during implementation]
-**Files changed:** [To be filled during implementation]
-**Code references:** [To be filled during implementation]
-**Verification:** [To be filled during compliance check]
-**Status:** ⏳ Pending
-### Decision 3: PDFDocument fallback (not custom sanitized types)
-**Requirement:** PDFDocument fallback (not custom sanitized types)
-**Location:** Neotoma MVP Feature Units — Execution Plan > Execution Order and Dependencies > Phase 1: Core Services (Domain Layer) > FU-100: File Analysis Service, line 347
-**Type:** must
-**Category:** implementation
-**Implementation approach:** [To be filled during implementation]
-**Files changed:** [To be filled during implementation]
-**Code references:** [To be filled during implementation]
-**Verification:** [To be filled during compliance check]
-**Status:** ⏳ Pending
-### Decision 4: code changes to comply with manifest**
-**Requirement:** code changes to comply with manifest**
-**Location:** Neotoma MVP Feature Units — Execution Plan > Detailed Documentation References, line 1789
-**Type:** must
-**Category:** implementation
-**Implementation approach:** [To be filled during implementation]
-**Files changed:** [To be filled during implementation]
-**Code references:** [To be filled during implementation]
-**Verification:** [To be filled during compliance check]
-**Status:** ⏳ Pending
-## Summary
-- **Total Requirements:** 4
-- **Implemented:** 0
-- **Partially Implemented:** 0
-- **Not Implemented:** 4
-- **Deferred:** 0