neotoma 0.3.0 → 0.3.2

package/docs/releases/archived/aspirational/v2.2.0/manifest.yaml

@@ -1,165 +0,0 @@
-release:
-  id: "v2.2.0"
-  name: "Vector Search Scalability"
-  type: "not_marketed" # marketed | not_marketed
-  status: "planning" # planning | in_progress | in_testing | ready_for_deployment | deployed | completed
-  target_date: "TBD" # Set after v2.1.0 completion
-  priority: "P1" # Performance optimization, not blocking
-  owner: "Mark Hendrickson"
-  marketing_required: false
-
-# NOTE: This manifest contains metadata and summaries for workflow automation.
-# Detailed planning documents are in markdown (see release_plan.md for overview).
-
-# WIP and parallelization limits
-execution_limits:
-  max_parallel_fus: 2 # Database changes require careful sequencing
-  max_high_risk_in_parallel: 1 # Only one high-risk FU at a time (index migration)
-
-feature_units:
-  # Phase 1: PostgreSQL RPC Function
-  - id: "FU-930"
-    name: "Vector Search RPC Function"
-    priority: "P0"
-    complexity: "Medium"
-    risk: "Low"
-    dependencies: []
-    description: "PostgreSQL function using native vector operators (<=> distance operator) to leverage vector index for similarity search"
-
-  # Phase 2: HNSW Index Migration
-  - id: "FU-931"
-    name: "HNSW Index Migration"
-    priority: "P0"
-    complexity: "Medium"
-    risk: "Medium"
-    dependencies: ["FU-930"]
-    description: "Migrate from IVFFlat to HNSW index for better scalability (requires pgvector 0.5.0+)"
-
-  # Phase 3: Application Code Updates
-  - id: "FU-932"
-    name: "Application Code Update"
-    priority: "P0"
-    complexity: "Medium"
-    risk: "Low"
-    dependencies: ["FU-930"]
-    description: "Replace JavaScript similarity computation with RPC calls in src/actions.ts and src/server.ts"
-
-  # Phase 4: Documentation Updates
-  - id: "FU-933"
-    name: "Documentation Update"
-    priority: "P0"
-    complexity: "Low"
-    risk: "Low"
-    dependencies: ["FU-931", "FU-932"]
-    description: "Update docs/subsystems/vector_ops.md to reflect HNSW index and RPC function usage"
-
-execution_schedule:
-  detailed_plan: "execution_schedule.md"
-  batches:
-    # Batch 0: RPC function creation (no dependencies)
-    - batch_id: 0
-      feature_units: ["FU-930"]
-      dependencies: []
-
-    # Batch 1: HNSW index migration (depends on RPC function)
-    - batch_id: 1
-      feature_units: ["FU-931"]
-      dependencies: ["FU-930"]
-
-    # Batch 2: Application code updates (depends on RPC function)
-    - batch_id: 2
-      feature_units: ["FU-932"]
-      dependencies: ["FU-930"]
-
-    # Batch 3: Documentation updates (depends on all implementation)
-    - batch_id: 3
-      feature_units: ["FU-933"]
-      dependencies: ["FU-931", "FU-932"]
-
-checkpoints:
-  checkpoint_1_after_batch: 0 # Review after RPC function complete
-  checkpoint_2_after_batch: 1 # Review after HNSW migration complete
-  checkpoint_3_after_batch: 2 # Review after code updates complete
-
-acceptance_criteria:
-  product:
-    - criterion: "Vector search uses indexed queries instead of JavaScript similarity calculation"
-      test: "manual_verification"
-      metric: null
-    - criterion: "Query performance meets benchmarks at scale"
-      test: "tests/integration/vector_search_performance.spec.ts"
-      metric: "query_latency_p95_ms"
-      threshold: 50
-
-  technical:
-    - criterion: "RPC function uses native vector operators"
-      test: "tests/integration/vector_search_rpc.spec.ts"
-      metric: null
-    - criterion: "HNSW index successfully created"
-      test: "manual_verification"
-      metric: null
-    - criterion: "Index usage verified via EXPLAIN ANALYZE"
-      test: "manual_verification"
-      metric: null
-    - criterion: "Network transfer reduced to <100KB per query"
-      test: "tests/integration/vector_search_performance.spec.ts"
-      metric: "network_transfer_kb"
-      threshold: 100
-    - criterion: "Backward compatibility maintained"
-      test: "tests/integration/vector_search_compatibility.spec.ts"
-      metric: null
-
-  business:
-    - criterion: "10-100x query latency improvement at scale"
-      test: "analytics/vector_search_performance"
-      metric: "latency_improvement_factor"
-      threshold: 10
-
-risks:
-  - id: "index_build_time"
-    category: "performance"
-    probability: "medium"
-    impact: "low"
-    mitigation: "HNSW index build is one-time operation; run during low-traffic window"
-  - id: "pgvector_version"
-    category: "dependency"
-    probability: "low"
-    impact: "high"
-    mitigation: "Verify pgvector 0.5.0+ before migration; fallback to IVFFlat if needed"
-  - id: "memory_increase"
-    category: "infrastructure"
-    probability: "high"
-    impact: "medium"
-    mitigation: "HNSW uses ~4x more memory than IVFFlat; monitor and scale if needed"
-  - id: "backward_compatibility"
-    category: "integration"
-    probability: "low"
-    impact: "medium"
-    mitigation: "RPC function maintains same result structure as current code"
-
-notes: |
-  This release addresses vector search scalability issues identified in the current implementation.
-  
-  Key improvements:
-  - Replace JavaScript similarity computation with PostgreSQL native operators
-  - Migrate from IVFFlat to HNSW index for better scalability
-  - Reduce network transfer by computing similarity in database
-  - Enable scaling to 10M+ records without performance degradation
-  
-  Current issues:
-  - Index not used (full table scans)
-  - Network transfer of full records with embeddings (MB per query)
-  - O(n) similarity calculations in JavaScript
-  - IVFFlat degrades beyond 100k records
-  
-  Expected improvements:
-  - Query latency: <10ms vs current ~1000ms at 100k records
-  - Network transfer: <100KB vs current ~1.5MB per query
-  - Scalability: 10M+ records vs current 100k limit
-  
-  Success criteria:
-  - All vector searches use indexed queries
-  - 10-100x query latency improvement
-  - Network transfer < 100KB per query
-  - Backward compatibility maintained
-

package/docs/releases/archived/aspirational/v2.2.0/status.md

@@ -1,283 +0,0 @@
-## Release v2.2.0 — Status Tracking
-### Current Status
-**Release Status**: `planning`
-**Last Updated**: [To be updated during implementation]
-**Progress**:
-- [ ] FU-930: Vector Search RPC Function
-- [ ] FU-931: HNSW Index Migration
-- [ ] FU-932: Application Code Update
-- [ ] FU-933: Documentation Update
-**Completion**: 0/4 Feature Units (0%)
-### Feature Unit Status
-#### FU-930: Vector Search RPC Function
-**Status**: `pending`
-**Priority**: P0
-**Assigned**: [To be assigned]
-**Started**: [Date]
-**Completed**: [Date]
-**Tasks**:
-- [ ] Create migration file
-- [ ] Implement RPC function with native vector operators
-- [ ] Add function documentation
-- [ ] Test RPC function correctness
-- [ ] Test type filtering
-- [ ] Test similarity threshold
-- [ ] Test limit parameter
-**Blockers**: None
-**Notes**: Foundation for subsequent batches. Must complete before index migration or code updates.
-#### FU-931: HNSW Index Migration
-**Status**: `pending`
-**Priority**: P0
-**Assigned**: [To be assigned]
-**Dependencies**: FU-930 (RPC function must exist)
-**Started**: [Date]
-**Completed**: [Date]
-**Tasks**:
-- [ ] Verify pgvector version (0.5.0+ required)
-- [ ] Create migration file
-- [ ] Implement migration with version check
-- [ ] Schedule index build during low-traffic window
-- [ ] Monitor index build (time, memory)
-- [ ] Verify index existence
-- [ ] Verify index usage via EXPLAIN ANALYZE
-- [ ] Measure query latency improvement
-**Blockers**: Requires FU-930 completion
-**Notes**: High-risk operation (index migration). Run during maintenance window. Monitor memory usage.
-#### FU-932: Application Code Update
-**Status**: `pending`
-**Priority**: P0
-**Assigned**: [To be assigned]
-**Dependencies**: FU-930 (RPC function must exist)
-**Started**: [Date]
-**Completed**: [Date]
-**Tasks**:
-- [ ] Update src/actions.ts (executeRetrieveRecords function)
-- [ ] Update src/server.ts (retrieveRecords method)
-- [ ] Update error handling
-- [ ] Preserve result formatting and logging
-- [ ] Unit tests for RPC integration
-- [ ] Integration tests for vector search
-- [ ] Verify backward compatibility
-- [ ] Performance benchmarks (latency, network transfer)
-- [ ] Code review
-**Blockers**: Requires FU-930 completion
-**Notes**: Replace JavaScript similarity calculation with RPC calls. Maintain backward compatibility.
-#### FU-933: Documentation Update
-**Status**: `pending`
-**Priority**: P0
-**Assigned**: [To be assigned]
-**Dependencies**: FU-931 (index), FU-932 (code)
-**Started**: [Date]
-**Completed**: [Date]
-**Tasks**:
-- [ ] Update docs/subsystems/vector_ops.md
-- [ ] Replace IVFFlat references with HNSW
-- [ ] Update index creation SQL
-- [ ] Update similarity search code examples
-- [ ] Document HNSW parameters and trade-offs
-- [ ] Update scalability characteristics
-- [ ] Update performance expectations
-- [ ] Verify documentation accuracy
-- [ ] Test code examples
-**Blockers**: Requires FU-931 and FU-932 completion
-**Notes**: Final step. Update all vector search documentation to reflect new architecture.
-### Checkpoints
-#### Checkpoint 1: After FU-930 (RPC Function)
-**Date**: [Date]
-**Status**: `pending`
-**Review Items**:
-- [ ] RPC function implementation correct
-- [ ] Test results satisfactory (all functional tests pass)
-- [ ] No performance issues
-- [ ] Ready to proceed to index migration
-**Decision**: [ ] GO / [ ] NO-GO
-**Notes**: [To be filled during review]
-#### Checkpoint 2: After FU-931 (HNSW Index)
-**Date**: [Date]
-**Status**: `pending`
-**Review Items**:
-- [ ] Index migration successful
-- [ ] Index usage verified via EXPLAIN ANALYZE
-- [ ] Performance meets expectations (P95 < 50ms)
-- [ ] No memory issues
-- [ ] Ready to proceed to code updates
-**Decision**: [ ] GO / [ ] NO-GO
-**Notes**: [To be filled during review]
-#### Checkpoint 3: After FU-932 (Code Updates)
-**Date**: [Date]
-**Status**: `pending`
-**Review Items**:
-- [ ] Code changes correct and tested
-- [ ] Integration tests passing (100% pass rate)
-- [ ] Performance benchmarks met (P95 < 50ms, <100KB transfer)
-- [ ] Backward compatibility verified
-- [ ] Ready to proceed to documentation
-**Decision**: [ ] GO / [ ] NO-GO
-**Notes**: [To be filled during review]
-#### Final Checkpoint: After FU-933 (Documentation)
-**Date**: [Date]
-**Status**: `pending`
-**Review Items**:
-- [ ] All Feature Units complete
-- [ ] All acceptance criteria met
-- [ ] Documentation accurate and complete
-- [ ] Test execution report reviewed
-- [ ] Rollback procedures tested
-- [ ] Ready for production deployment
-**Decision**: [ ] GO / [ ] NO-GO
-**Notes**: [To be filled during review]
-### Decision Log
-#### Decision 1: Use HNSW Index Instead of IVFFlat
-**Date**: [Date when release was planned]
-**Decision**: Migrate from IVFFlat to HNSW index for better scalability
-**Rationale**:
-- IVFFlat degrades beyond 100k records
-- HNSW provides better recall and latency at scale
-- HNSW scales to 10M+ records without parameter tuning
-- Memory trade-off acceptable (4x more memory, modern infrastructure can handle)
-**Impact**:
-- Requires pgvector 0.5.0+
-- One-time index rebuild (run during maintenance window)
-- Expected 10-100x query latency improvement
-**Status**: Approved
-#### Decision 2: Use PostgreSQL RPC Function Instead of JavaScript Similarity
-**Date**: [Date when release was planned]
-**Decision**: Replace JavaScript similarity computation with PostgreSQL native operators
-**Rationale**:
-- Current implementation bypasses vector index (full table scans)
-- Network transfer of embeddings is expensive (MB per query)
-- JavaScript similarity calculation is O(n)
-- PostgreSQL native operators use index automatically
-**Impact**:
-- Requires RPC function implementation
-- Code changes in src/actions.ts and src/server.ts
-- Expected 15x reduction in network transfer
-**Status**: Approved
-#### Decision 3: Not Marketed Release (Silent Deployment)
-**Date**: [Date when release was planned]
-**Decision**: Deploy as performance optimization without marketing activities
-**Rationale**:
-- Internal performance improvement, not user-facing feature
-- No new functionality, just optimization
-- Users will benefit from improved performance without changes to API
-**Impact**:
-- No marketing required
-- No user communication needed (transparent improvement)
-- Deploy during normal maintenance window
-**Status**: Approved
-### Risk Register
-#### Risk 1: pgvector Version Incompatibility
-**Probability**: Low
-**Impact**: High
-**Mitigation**:
-- Version check in migration script
-- Fallback to IVFFlat if HNSW not supported
-- Document pgvector version requirement
-**Status**: Mitigated
-#### Risk 2: Index Build Time
-**Probability**: Medium
-**Impact**: Low
-**Mitigation**:
-- Schedule during low-traffic window
-- Monitor index build progress
-- Estimate build time based on record count
-**Status**: Mitigated
-#### Risk 3: Memory Increase
-**Probability**: High
-**Impact**: Medium
-**Mitigation**:
-- Monitor memory usage during and after migration
-- Scale infrastructure if needed (HNSW uses ~4x more memory)
-- Have infrastructure scaling plan ready
-**Status**: Monitoring required
-#### Risk 4: Performance Regression
-**Probability**: Low
-**Impact**: High
-**Mitigation**:
-- Thorough performance testing before deployment
-- Monitor query latency after deployment
-- Have rollback plan ready (recreate IVFFlat index)
-**Status**: Mitigated
-### Issues and Blockers
-**Current Issues**: None
-**Resolved Issues**: [To be updated during implementation]
-### Test Results
-**Test Execution Status**: Not started
-**Test Categories**:
-- Functional Tests: 0/4 passed
-- Performance Benchmarks: 0/5 passed
-- Index Verification: 0/3 passed
-- Backward Compatibility: 0/3 passed
-- Load Tests: 0/2 passed
-- Rollback Tests: 0/2 passed
-**Total**: 0/19 tests passed (0%)
-**Deployment Blockers**: All tests must pass before deployment
-### Performance Metrics
-**Baseline** (before v2.2.0):
-- Query Latency P95: ~1000ms (100k records, JavaScript similarity)
-- Network Transfer: ~1.5MB per query
-- Scalability Limit: 100k records (IVFFlat degradation)
-**Target** (after v2.2.0):
-- Query Latency P95: <50ms (10-100x improvement)
-- Network Transfer: <100KB per query (15x reduction)
-- Scalability: 10M+ records (HNSW)
-**Actual** (to be measured):
-- Query Latency P95: [TBD]
-- Network Transfer: [TBD]
-- Improvement Factor: [TBD]x
-### Deployment Plan
-**Deployment Type**: Rolling deployment (no downtime)
-**Deployment Window**: [To be scheduled]
-**Steps**:
-1. **Pre-Deployment**:
-   - [ ] All Feature Units complete
-   - [ ] All tests passing
-   - [ ] Final checkpoint approved
-   - [ ] Rollback plan ready
-2. **Deployment**:
-   - [ ] Deploy RPC function migration (FU-930)
-   - [ ] Deploy HNSW index migration (FU-931) during low-traffic window
-   - [ ] Monitor index build completion
-   - [ ] Deploy code updates (FU-932)
-   - [ ] Verify functionality
-3. **Post-Deployment**:
-   - [ ] Monitor query latency (target: P95 < 50ms)
-   - [ ] Monitor network transfer (target: <100KB)
-   - [ ] Monitor memory usage
-   - [ ] Monitor error rate (should remain stable)
-   - [ ] Verify index usage via EXPLAIN ANALYZE samples
-4. **Rollback** (if needed):
-   - [ ] Revert code changes
-   - [ ] Drop HNSW index, recreate IVFFlat
-   - [ ] Verify functionality restored
-**Deployment Duration**: ~2-4 hours (including index build)
-**Monitoring Duration**: 7 days post-deployment
-### Next Steps
-**Immediate**:
-1. Assign Feature Units to implementers
-2. Begin FU-930 (RPC Function) implementation
-3. Schedule maintenance window for FU-931 (index migration)
-**Short-Term**:
-1. Complete FU-930 and checkpoint review
-2. Complete FU-931 and checkpoint review
-3. Complete FU-932 and checkpoint review
-4. Complete FU-933 and final checkpoint
-**Long-Term**:
-1. Deploy to production
-2. Monitor performance for 7 days
-3. Document lessons learned
-4. Close release
-### Notes and Observations
-[To be updated during implementation]
-### Related Documentation
-- `manifest.yaml` — Release metadata and Feature Units
-- `release_plan.md` — Release overview and specifications
-- `execution_schedule.md` — Batch execution plan
-- `integration_tests.md` — Test specifications
-**Status Legend**:
-- `planning`: Release in planning phase
-- `in_progress`: Feature Units being implemented
-- `in_testing`: Build complete, manual test execution in progress
-- `ready_for_deployment`: All tests passed (automated + manual), ready to deploy
-- `deployed`: Deployed to production
-- `completed`: Post-deployment monitoring complete, release closed

package/docs/releases/compliance_reports/all_fus_compliance_summary.md

@@ -1,112 +0,0 @@
-# All Feature Units Compliance Summary
-**Generated:** 2025-12-14T06:22:11.460Z  
-**Total FUs Validated:** 26
-## Executive Summary
-- **Overall Compliance Rate:** 69.4%
-- **Total Requirements Checked:** 121
-- **Total Passed:** 84
-- **Total Failed:** 37
-- **Fully Compliant FUs:** 0 (0.0%)
-- **FUs with Gaps:** 26
-- **Validation Errors:** 0
-## Per-FU Compliance Status
-| FU ID | Name | Release | Requirements | Passed | Failed | Compliance | Status | Report |
-|-------|------|---------|--------------|--------|--------|------------|--------|--------|
-| FU-000 | Database Schema v1.0 | v0.1.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-000_compliance.md) |
-| FU-002 | Configuration Management | v0.1.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-002_compliance.md) |
-| FU-050 | Event-Sourcing Foundation | v0.1.0 | 10 | 4 | 6 | 40.0% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-050_compliance.md) |
-| FU-051 | Repository Abstractions | v0.1.0 | 8 | 5 | 3 | 62.5% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-051_compliance.md) |
-| FU-052 | Reducer Versioning | v0.1.0 | 7 | 3 | 4 | 42.9% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-052_compliance.md) |
-| FU-053 | Cryptographic Schema Fields | v0.1.0 | 6 | 5 | 1 | 83.3% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-053_compliance.md) |
-| FU-054 | Hash Chaining Schema Fields | v0.1.0 | 6 | 4 | 2 | 66.7% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-054_compliance.md) |
-| FU-055 | Observation Storage Layer | v0.1.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-055_compliance.md) |
-| FU-056 | Enhanced Reducer Engine | v0.1.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-056_compliance.md) |
-| FU-057 | Schema Registry Service | v0.1.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-057_compliance.md) |
-| FU-058 | Observation-Aware Ingestion | v0.1.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-058_compliance.md) |
-| FU-059 | Relationship Types | v0.1.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-059_compliance.md) |
-| FU-061 | MCP Actions for Observations | v0.1.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-061_compliance.md) |
-| FU-100 | File Analysis Service Update | v1.0.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v1.0.0/compliance_reports/FU-100_compliance.md) |
-| FU-101 | Entity Resolution Service | v1.0.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v1.0.0/compliance_reports/FU-101_compliance.md) |
-| FU-102 | Event Generation Service | v1.0.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v1.0.0/compliance_reports/FU-102_compliance.md) |
-| FU-103 | Graph Builder Service | v1.0.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v1.0.0/compliance_reports/FU-103_compliance.md) |
-| FU-104 | Embedding Service | v0.1.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-104_compliance.md) |
-| FU-105 | Search Service (Deterministic) | v1.0.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v1.0.0/compliance_reports/FU-105_compliance.md) |
-| FU-200 | MCP Server Core | v0.1.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-200_compliance.md) |
-| FU-201 | MCP Action — store_record | v0.1.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-201_compliance.md) |
-| FU-202 | MCP Action — retrieve_records | v0.1.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-202_compliance.md) |
-| FU-203 | MCP Action — update_record | v0.1.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-203_compliance.md) |
-| FU-204 | MCP Action — delete_record | v0.1.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-204_compliance.md) |
-| FU-205 | MCP Action — upload_file | v0.1.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-205_compliance.md) |
-| FU-206 | MCP Action — get_file_url | v0.1.0 | 4 | 3 | 1 | 75.0% | ⚠️ Gaps | [View](docs/releases/v0.1.0/compliance_reports/FU-206_compliance.md) |
-## Top Compliance Issues
-1. **code changes to comply with manifest****
-   - Occurrences: 21 FU(s)
-   - Affected: FU-000, FU-002, FU-055, FU-056, FU-057, FU-058, FU-059, FU-061, FU-100, FU-101, FU-102, FU-103, FU-105, FU-200, FU-201, FU-202, FU-203, FU-204, FU-205, FU-206, FU-104
-2. **Events MUST be append-only (never updated or deleted)**
-   - Occurrences: 1 FU(s)
-   - Affected: FU-050
-3. **Reducers MUST be pure functions (no side effects, no I/O)**
-   - Occurrences: 1 FU(s)
-   - Affected: FU-050
-4. **Event schema MUST include all future fields (crypto, hash) even if unused**
-   - Occurrences: 1 FU(s)
-   - Affected: FU-050
-5. **Event validation MUST reject invalid events before storage**
-   - Occurrences: 1 FU(s)
-   - Affected: FU-050
-6. **MUST NOT skip event validation**
-   - Occurrences: 1 FU(s)
-   - Affected: FU-050
-7. **MUST NOT write directly to `records` table (only via materialized view refresh)**
-   - Occurrences: 1 FU(s)
-   - Affected: FU-050
-8. **Domain logic MUST use repository interfaces (no direct storage access)**
-   - Occurrences: 1 FU(s)
-   - Affected: FU-051
-9. **Repository implementations MUST be swappable (same interface, different backend)**
-   - Occurrences: 1 FU(s)
-   - Affected: FU-051
-10. **MUST NOT introduce non-determinism**
-   - Occurrences: 1 FU(s)
-   - Affected: FU-051
-## Validation Errors
-_No validation errors._
-## Individual Reports
-- [FU-000 — Database Schema v1.0](docs/releases/v0.1.0/compliance_reports/FU-000_compliance.md)
-- [FU-002 — Configuration Management](docs/releases/v0.1.0/compliance_reports/FU-002_compliance.md)
-- [FU-050 — Event-Sourcing Foundation](docs/releases/v0.1.0/compliance_reports/FU-050_compliance.md)
-- [FU-051 — Repository Abstractions](docs/releases/v0.1.0/compliance_reports/FU-051_compliance.md)
-- [FU-052 — Reducer Versioning](docs/releases/v0.1.0/compliance_reports/FU-052_compliance.md)
-- [FU-053 — Cryptographic Schema Fields](docs/releases/v0.1.0/compliance_reports/FU-053_compliance.md)
-- [FU-054 — Hash Chaining Schema Fields](docs/releases/v0.1.0/compliance_reports/FU-054_compliance.md)
-- [FU-055 — Observation Storage Layer](docs/releases/v0.1.0/compliance_reports/FU-055_compliance.md)
-- [FU-056 — Enhanced Reducer Engine](docs/releases/v0.1.0/compliance_reports/FU-056_compliance.md)
-- [FU-057 — Schema Registry Service](docs/releases/v0.1.0/compliance_reports/FU-057_compliance.md)
-- [FU-058 — Observation-Aware Ingestion](docs/releases/v0.1.0/compliance_reports/FU-058_compliance.md)
-- [FU-059 — Relationship Types](docs/releases/v0.1.0/compliance_reports/FU-059_compliance.md)
-- [FU-061 — MCP Actions for Observations](docs/releases/v0.1.0/compliance_reports/FU-061_compliance.md)
-- [FU-100 — File Analysis Service Update](docs/releases/v1.0.0/compliance_reports/FU-100_compliance.md)
-- [FU-101 — Entity Resolution Service](docs/releases/v1.0.0/compliance_reports/FU-101_compliance.md)
-- [FU-102 — Event Generation Service](docs/releases/v1.0.0/compliance_reports/FU-102_compliance.md)
-- [FU-103 — Graph Builder Service](docs/releases/v1.0.0/compliance_reports/FU-103_compliance.md)
-- [FU-105 — Search Service (Deterministic)](docs/releases/v1.0.0/compliance_reports/FU-105_compliance.md)
-- [FU-200 — MCP Server Core](docs/releases/v0.1.0/compliance_reports/FU-200_compliance.md)
-- [FU-201 — MCP Action — store_record](docs/releases/v0.1.0/compliance_reports/FU-201_compliance.md)
-- [FU-202 — MCP Action — retrieve_records](docs/releases/v0.1.0/compliance_reports/FU-202_compliance.md)
-- [FU-203 — MCP Action — update_record](docs/releases/v0.1.0/compliance_reports/FU-203_compliance.md)
-- [FU-204 — MCP Action — delete_record](docs/releases/v0.1.0/compliance_reports/FU-204_compliance.md)
-- [FU-205 — MCP Action — upload_file](docs/releases/v0.1.0/compliance_reports/FU-205_compliance.md)
-- [FU-206 — MCP Action — get_file_url](docs/releases/v0.1.0/compliance_reports/FU-206_compliance.md)
-- [FU-104 — Embedding Service](docs/releases/v0.1.0/compliance_reports/FU-104_compliance.md)
-## Recommendations
-**26 Feature Unit(s) have specification compliance gaps** that should be addressed to ensure implementation matches documented requirements.
-### Priority Actions:
-1. Review individual compliance reports for FUs with gaps
-2. Address common issues appearing across multiple FUs
-3. Update implementation to match specification requirements
-4. Re-run validation after fixes
-### Most Common Issues:
-1. code changes to comply with manifest**... (21 FUs affected)
-2. Events MUST be append-only (never updated or deleted)... (1 FUs affected)
-3. Reducers MUST be pure functions (no side effects, no I/O)... (1 FUs affected)
-**Note:** This report validates that code implementation matches documented specifications. It does not validate functional correctness or test coverage.