neotoma 0.3.0 → 0.3.2

package/docs/releases/v0.1.0/integration_tests.md

@@ -1,316 +0,0 @@
-## Release v0.1.0 — Cross-FU Integration Tests
-### 1. Purpose
-Define the **integration test suite** for Release `v0.1.0` (Internal MCP Release). These tests:
-- Span multiple Feature Units.
-- Validate the full Truth Layer pipeline via MCP (ingestion → extraction → entities → events → graph → search).
-- Are required to pass before release approval.
-- Validate determinism and graph integrity.
-### 2. Test Matrix (High-Level)
-| ID     | Name                                | Batches Covered    | FUs Involved                                                   |
-| ------ | ----------------------------------- | ------------------ | -------------------------------------------------------------- |
-| IT-001 | File Upload → Extraction → Query    | 1, 2, 3, 4, 6      | FU-100, FU-101, FU-102, FU-103, FU-105, FU-205                 |
-| IT-002 | Entity Resolution Validation        | 1, 2, 3, 6         | FU-100, FU-101, FU-103, FU-205                                 |
-| IT-003 | Timeline Event Validation           | 1, 2, 3, 6         | FU-100, FU-102, FU-103, FU-205                                 |
-| IT-004 | Graph Integrity Validation          | 3, 6               | FU-103, FU-205                                                 |
-| IT-005 | Determinism Validation              | 1, 2, 3, 4, 6      | FU-100, FU-101, FU-102, FU-103, FU-105, FU-205                 |
-| IT-006 | MCP Action Validation               | 5, 6               | FU-200, FU-201, FU-202, FU-203, FU-204, FU-206                 |
-| IT-007 | Event-Sourcing Validation           | 0.5, 0.6, 5        | FU-050, FU-051, FU-052, FU-053, FU-054, FU-201, FU-203, FU-204 |
-| IT-008 | Observation Architecture Validation | 0.7, 0.8, 6.5, 6.6 | FU-055, FU-056, FU-057, FU-058, FU-059, FU-061                 |
-| IT-009 | Multi-Source Entity Resolution      | 0.7, 0.8, 6.5, 6.6 | FU-055, FU-056, FU-058, FU-061                                 |
-| IT-010 | Reducer Determinism Validation      | 0.8, 6.5           | FU-056, FU-058                                                 |
-| IT-011 | Relationship Types Validation       | 0.8, 6.6           | FU-059, FU-061                                                 |
-### 3. Test Definitions
-#### IT-001: File Upload → Extraction → Query Flow
-**Goal:** Verify that file upload via MCP triggers full pipeline (extraction → entities → events → graph → search).
-**Preconditions:**
-- System running with all Batch 1-6 FUs deployed.
-- MCP server accessible from test client.
-- Test files available (PDF invoice, receipt, statement).
-**Steps:**
-1. Call MCP `upload_file` action with PDF file path.
-2. Wait for ingestion to complete.
-3. Call MCP `retrieve_records` with filters (type, properties).
-4. Inspect response:
-   - Extracted fields present and correct.
-   - Entities resolved and linked.
-   - Events generated with correct timestamps.
-5. Call `retrieve_records` with search terms.
-6. Verify deterministic ranking (same query → same order).
-**Expected Results:**
-- Correct schema type assigned.
-- Fields extracted deterministically.
-- Entities and events created and linked in graph.
-- Search results deterministic and correct.
-**Machine-Checkable:**
-- `upload_file` returns record with `id`, `type`, `properties`.
-- `retrieve_records` returns records with deterministic ordering.
-- Graph integrity queries return 0 orphans.
-**test:** "tests/integration/release/v0.1.0/it_001_file_upload_extraction_query.test.ts"
-#### IT-002: Entity Resolution Validation
-**Goal:** Verify that entity resolution produces canonical IDs across multiple documents.
-**Preconditions:**
-- System running with FU-100, FU-101, FU-103, FU-205 deployed.
-- Test files with entity name variations (e.g., "Acme Corp" and "ACME CORP").
-**Steps:**
-1. Upload document 1 containing "Acme Corp" via `upload_file`.
-2. Upload document 2 containing "ACME CORP" via `upload_file`.
-3. Query both records via `retrieve_records`.
-4. Extract entity IDs from both records.
-5. Verify both records link to same entity_id.
-**Expected Results:**
-- Same entity name (normalized) → same entity_id.
-- Both records link to same entity in graph.
-- Entity ID is deterministic hash-based.
-**Machine-Checkable:**
-- Query: `SELECT entity_id FROM record_entities WHERE record_id IN (...) GROUP BY entity_id HAVING COUNT(*) > 1` returns expected entity.
-- Entity ID format: `ent_{sha256(type:normalized_name)}`.
-**test:** "tests/integration/release/v0.1.0/it_002_entity_resolution.test.ts"
-#### IT-003: Timeline Event Validation
-**Goal:** Verify that date fields in documents generate timeline events correctly.
-**Preconditions:**
-- System running with FU-100, FU-102, FU-103, FU-205 deployed.
-- Test file with date fields (e.g., invoice with `date_issued`, `date_due`).
-**Steps:**
-1. Upload document with date fields via `upload_file`.
-2. Query events via graph (or retrieve record and inspect events).
-3. Verify:
-   - Events generated for each date field.
-   - Event timestamps correct (ISO 8601).
-   - Events linked to source record.
-   - Events ordered chronologically.
-**Expected Results:**
-- Date fields → events generated.
-- Event IDs deterministic (hash-based).
-- Timeline ordering correct.
-**Machine-Checkable:**
-- Query: `SELECT COUNT(*) FROM events WHERE source_record_id = '{record_id}'` returns expected count.
-- Events sorted by `event_timestamp` ASC.
-**test:** "tests/integration/release/v0.1.0/it_003_timeline_events.test.ts"
-#### IT-004: Graph Integrity Validation
-**Goal:** Verify that graph insertion maintains integrity (no orphans, no cycles).
-**Preconditions:**
-- System running with FU-103, FU-205 deployed.
-- Multiple test files for upload.
-**Steps:**
-1. Upload multiple documents via `upload_file`.
-2. Query graph integrity:
-   - Count orphan events (events without source_record).
-   - Count orphan entities (entities without records).
-   - Detect cycles in graph.
-3. Verify all inserts were transactional (all-or-nothing).
-**Expected Results:**
-- 0 orphan nodes.
-- 0 cycles.
-- All inserts transactional.
-**Machine-Checkable:**
-- Query: `SELECT COUNT(*) FROM events WHERE record_id NOT IN (SELECT id FROM records)` = 0
-- Query: `SELECT COUNT(*) FROM record_entities WHERE entity_id NOT IN (SELECT id FROM entities)` = 0
-- Cycle detection query returns empty.
-**test:** "tests/integration/release/v0.1.0/it_004_graph_integrity.test.ts"
-#### IT-005: Determinism Validation
-**Goal:** Verify that same input produces identical output (100% deterministic).
-**Preconditions:**
-- System running with all FUs deployed.
-- Test file for repeated uploads.
-**Steps:**
-1. Upload same file 100 times via `upload_file`.
-2. For each upload, record:
-   - Record ID (should be same due to deduplication or different due to timestamps)
-   - Schema type (must be identical)
-   - Extracted fields (must be identical)
-   - Entity IDs (must be identical)
-   - Event IDs (must be identical)
-3. Run same query 100 times via `retrieve_records`.
-4. Verify query results identical (same order, same records).
-**Expected Results:**
-- Same file → same extraction (100% deterministic).
-- Same query → same order (100% deterministic).
-- Entity IDs stable across uploads.
-**Machine-Checkable:**
-- Property-based test: 100 runs, assert all outputs identical (modulo timestamps/IDs).
-- Query determinism test: 100 runs, assert same order.
-**test:** "tests/integration/release/v0.1.0/it_005_determinism.test.ts"
-#### IT-006: MCP Action Validation
-**Goal:** Verify that all 6 core MCP actions function correctly.
-**Preconditions:**
-- System running with all MCP FUs deployed.
-- MCP server accessible from test client.
-**Steps:**
-1. **store_record**: Create record via `store_record`, verify response.
-2. **retrieve_records**: Query records via `retrieve_records`, verify filters work.
-3. **update_record**: Update record via `update_record`, verify changes.
-4. **delete_record**: Delete record via `delete_record`, verify deletion.
-5. **upload_file**: Upload file via `upload_file`, verify record created.
-6. **get_file_url**: Get signed URL via `get_file_url`, verify URL accessible.
-**Expected Results:**
-- All 6 actions return structured responses.
-- Error handling works (invalid input → error envelope).
-- Actions behave deterministically.
-**Machine-Checkable:**
-- Each action has unit and integration tests.
-- Error cases tested (validation errors, not found, etc.).
-**test:** "tests/integration/release/v0.1.0/it_006_mcp_actions.test.ts"
-#### IT-007: Event-Sourcing Validation
-**Goal:** Verify that event-sourcing foundation is operational (events emitted, reducers applied, historical replay functional).
-**Preconditions:**
-- System running with FU-050, FU-051, FU-052, FU-053, FU-054, FU-201, FU-203, FU-204 deployed.
-- MCP server accessible from test client.
-**Steps:**
-1. Create record via `store_record` MCP action.
-2. Verify event emitted to `state_events` table with correct schema (event_type, payload, timestamp, record_id, reducer_version).
-3. Verify state reconstructed via reducer matches direct DB state in `records` table.
-4. Update record via `update_record` MCP action.
-5. Verify `RecordUpdated` event emitted with correct payload.
-6. Verify state reconstructed via reducer matches updated DB state.
-7. Delete record via `delete_record` MCP action.
-8. Verify `RecordDeleted` event emitted.
-9. Test historical replay: get record state at timestamp before update.
-10. Verify reducer versioning: check reducer_version field in events.
-11. Verify cryptographic fields (if implemented): check signer_public_key, signature fields.
-12. Verify hash chaining (if implemented): check previous_event_hash, event_hash fields.
-**Expected Results:**
-- All state changes emit events to `state_events` table.
-- Reducers reconstruct state correctly (matches direct DB state).
-- Historical replay functional (can view record state at any timestamp).
-- Event schema includes all required fields (reducer_version, crypto/hash fields if implemented).
-**Machine-Checkable:**
-- Query: `SELECT COUNT(*) FROM state_events WHERE record_id = '{record_id}'` returns expected count.
-- Query: `SELECT * FROM state_events WHERE record_id = '{record_id}' ORDER BY timestamp` returns chronological events.
-- Reducer test: Apply reducers to events, verify reconstructed state matches `records` table.
-- Historical replay test: Get record state at timestamp T, verify matches expected state.
-**test:** "tests/integration/release/v0.1.0/it_007_event_sourcing.test.ts"
-#### IT-008: Observation Architecture Validation
-**Goal:** Verify that observation layer is operational (observations created, snapshots computed, provenance tracked).
-**Preconditions:**
-- System running with FU-055, FU-056, FU-057, FU-058, FU-059, FU-061 deployed.
-- MCP server accessible from test client.
-- Test file with entities (e.g., invoice with vendor).
-**Steps:**
-1. Upload document via `upload_file` MCP action.
-2. Verify observations created for each entity:
-   - Query `observations` table for entity_id.
-   - Verify observation contains correct fields, schema_version, source_record_id.
-3. Verify snapshot computed:
-   - Query `entity_snapshots` table for entity_id.
-   - Verify snapshot contains merged fields from observations.
-   - Verify provenance maps fields to observation_ids.
-4. Query entity snapshot via `get_entity_snapshot` MCP action.
-5. Verify response includes snapshot, provenance, observation_count.
-6. Query observations via `list_observations` MCP action.
-7. Verify response includes all observations for entity.
-**Expected Results:**
-- Observations created during ingestion.
-- Snapshots computed by reducers with provenance.
-- MCP actions return correct snapshot and observation data.
-- Provenance traces fields to observations and documents.
-**Machine-Checkable:**
-- Query: `SELECT COUNT(*) FROM observations WHERE entity_id = '{entity_id}'` returns expected count.
-- Query: `SELECT * FROM entity_snapshots WHERE entity_id = '{entity_id}'` returns snapshot with provenance.
-- MCP action `get_entity_snapshot` returns snapshot with provenance mapping.
-**test:** "tests/integration/release/v0.1.0/it_008_observation_architecture.test.ts"
-#### IT-009: Multi-Source Entity Resolution
-**Goal:** Verify that multiple observations about same entity merge correctly via reducers.
-**Preconditions:**
-- System running with FU-055, FU-056, FU-058, FU-061 deployed.
-- Two test files about same entity from different sources.
-**Steps:**
-1. Upload document 1 about entity (e.g., invoice from vendor) via `upload_file`.
-2. Verify observation 1 created with fields and source_priority.
-3. Upload document 2 about same entity (e.g., contract with vendor) via `upload_file`.
-4. Verify observation 2 created with different fields and source_priority.
-5. Query entity snapshot via `get_entity_snapshot` MCP action.
-6. Verify snapshot correctly merges observations:
-   - Fields from both observations present.
-   - Merge policies applied correctly (highest_priority, last_write, etc.).
-   - Provenance tracks which observation contributed each field.
-7. Query field provenance via `get_field_provenance` MCP action.
-8. Verify provenance chain: field → observation → document → file.
-**Expected Results:**
-- Multiple observations about same entity coexist.
-- Reducer merges observations correctly based on merge policies.
-- Provenance traces each field to correct observation and document.
-- MCP actions return correct merged snapshot and provenance.
-**Machine-Checkable:**
-- Query: `SELECT COUNT(*) FROM observations WHERE entity_id = '{entity_id}'` returns 2.
-- Query: `SELECT observation_count FROM entity_snapshots WHERE entity_id = '{entity_id}'` returns 2.
-- Snapshot contains fields from both observations.
-- Provenance maps fields to correct observation_ids.
-**test:** "tests/integration/release/v0.1.0/it_009_multi_source_entity_resolution.test.ts"
-#### IT-010: Reducer Determinism Validation
-**Goal:** Verify that reducers are deterministic (same observations + merge rules → same snapshot).
-**Preconditions:**
-- System running with FU-056, FU-058 deployed.
-- Test observations for entity.
-**Steps:**
-1. Create observations for entity with known fields and priorities.
-2. Compute snapshot via reducer.
-3. Record snapshot fields and provenance.
-4. Recompute snapshot with same observations (trigger reducer again).
-5. Verify snapshot identical (same fields, same provenance).
-6. Test with out-of-order observations:
-   - Create observations in different order.
-   - Compute snapshot.
-   - Verify same result regardless of input order.
-**Expected Results:**
-- Same observations → same snapshot (100% deterministic).
-- Out-of-order observations → same snapshot (order-independent).
-- Provenance mapping deterministic.
-**Machine-Checkable:**
-- Property-based test: 100 runs with same observations, assert all snapshots identical.
-- Order-independence test: Different observation orders produce same snapshot.
-**test:** "tests/integration/release/v0.1.0/it_010_reducer_determinism.test.ts"
-#### IT-011: Relationship Types Validation
-**Goal:** Verify that first-class typed relationships work correctly.
-**Preconditions:**
-- System running with FU-059, FU-061 deployed.
-- Entities created (e.g., invoice, payment).
-**Steps:**
-1. Create relationship via `create_relationship` MCP action:
-   - Type: `SETTLES`
-   - Source: payment entity
-   - Target: invoice entity
-     .2. Verify relationship created in `relationships` table.
-2. Query relationships via `list_relationships` MCP action:
-   - Query outbound relationships for payment entity.
-   - Query inbound relationships for invoice entity.
-3. Verify relationship metadata preserved.
-4. Test cycle detection:
-   - Attempt to create cycle (e.g., PART_OF relationship that would create cycle).
-   - Verify cycle detection prevents creation.
-**Expected Results:**
-- Relationships created successfully.
-- Graph traversal queries work.
-- Relationship metadata preserved.
-- Cycle detection prevents invalid relationships.
-**Machine-Checkable:**
-- Query: `SELECT COUNT(*) FROM relationships WHERE source_entity_id = '{entity_id}'` returns expected count.
-- MCP action `list_relationships` returns relationships with correct types and metadata.
-- Cycle detection query prevents invalid relationships.
-**test:** "tests/integration/release/v0.1.0/it_011_relationship_types.test.ts"
-### 4. Execution per Batch
-**After Batch 0.6:** Event-sourcing foundation tests (IT-007 partial: events emitted, reducers applied)
-**After Batch 1:** Smoke tests (MCP server starts, basic file upload works)
-**After Batch 4:** Graph integrity tests (IT-004), search determinism tests (partial IT-005)
-**After Batch 5:** Event-sourcing MCP action tests (IT-007 complete: store_record, update_record, delete_record emit events)
-**After Batch 0.7:** Observation storage tests (IT-008 partial: observations created)
-**After Batch 0.8:** Reducer tests (IT-010: reducer determinism)
-**After Batch 6.5:** Observation ingestion tests (IT-008, IT-009: full observation flow)
-**After Batch 6.6:** Observation MCP action tests (IT-008, IT-009, IT-011: MCP actions functional)
-**After Batch 6:** Full integration test suite (IT-001 through IT-011)
-**Before Release:** Complete integration test suite must pass
-### 5. Manual Validation Requirements
-**Cursor Integration:**
-- Connect Cursor to MCP server.
-- Test `upload_file` and `retrieve_records` via Cursor.
-- Verify responses match expected structure.
-**ChatGPT Integration:**
-- Connect ChatGPT to MCP server.
-- Test `store_record` and `retrieve_records` via ChatGPT.
-- Verify responses match expected structure.
-### 6. Test Automation
-All tests should be automated where possible:
-- Unit tests for each FU.
-- Integration tests for cross-FU flows.
-- Property-based tests for determinism.
-- E2E tests via MCP client.
-Manual validation required only for Cursor/ChatGPT integration (external tools).

package/docs/releases/v0.1.0/manifest.yaml

@@ -1,291 +0,0 @@
-release:
-  id: "v0.1.0"
-  name: "Internal MCP Release"
-  type: "not_marketed" # marketed | not_marketed
-  status: "planning" # planning | in_progress | in_testing | ready_for_deployment | deployed | completed
-  target_date: "when ready"
-  priority: "P0"
-  marketing_required: false
-
-# Execution strategy
-execution_strategy:
-  type: "multi_agent" # "multi_agent" or "sequential"
-  max_parallel_fus: 3 # Maximum FUs executing simultaneously
-  max_high_risk_in_parallel: 1 # Maximum high-risk FUs executing simultaneously
-  agent_spawning:
-    enabled: true
-    status_tracking: "file" # "file" or "api"
-    status_file: "docs/releases/v0.1.0/agent_status.json"
-
-feature_units:
-  # Infrastructure
-  - id: "FU-000"
-    priority: "P0"
-    dependencies: []
-  - id: "FU-002"
-    priority: "P0"
-    dependencies: []
-
-  # Blockchain-ready architecture foundation
-  - id: "FU-050"
-    priority: "P0"
-    dependencies: ["FU-000"]
-  - id: "FU-051"
-    priority: "P0"
-    dependencies: ["FU-000"]
-  - id: "FU-052"
-    priority: "P0"
-    dependencies: ["FU-050"]
-  - id: "FU-053"
-    priority: "P0"
-    dependencies: ["FU-050"]
-  - id: "FU-054"
-    priority: "P0"
-    dependencies: ["FU-050"]
-
-  # Observation architecture (builds on event-sourcing foundation)
-  - id: "FU-055"
-    priority: "P0"
-    dependencies: ["FU-050", "FU-051", "FU-052"]
-  - id: "FU-056"
-    priority: "P0"
-    dependencies: ["FU-050", "FU-052", "FU-055"]
-  - id: "FU-057"
-    priority: "P0"
-    dependencies: ["FU-000", "FU-055"]
-  - id: "FU-058"
-    priority: "P0"
-    dependencies: ["FU-055", "FU-056", "FU-100", "FU-101"]
-  - id: "FU-059"
-    priority: "P0"
-    dependencies: ["FU-055", "FU-103"]
-  - id: "FU-060"
-    priority: "P1"
-    dependencies: ["FU-057", "FU-058"]
-  - id: "FU-061"
-    priority: "P0"
-    dependencies: ["FU-055", "FU-056", "FU-059", "FU-200"]
-
-  # Core services
-  - id: "FU-100"
-    priority: "P0"
-    dependencies: ["FU-000"]
-    notes: "Includes type detection analytics (see type_detection_analytics.md)"
-  - id: "FU-101"
-    priority: "P0"
-    dependencies: ["FU-100"]
-  - id: "FU-102"
-    priority: "P0"
-    dependencies: ["FU-100"]
-  - id: "FU-103"
-    priority: "P0"
-    dependencies: ["FU-101", "FU-102"]
-  - id: "FU-105"
-    priority: "P0"
-    dependencies: ["FU-103"]
-
-  # MCP layer
-  - id: "FU-200"
-    priority: "P0"
-    dependencies: ["FU-000"]
-  - id: "FU-201"
-    priority: "P0"
-    dependencies: ["FU-200", "FU-050", "FU-051"]
-  - id: "FU-202"
-    priority: "P0"
-    dependencies: ["FU-200", "FU-105"]
-  - id: "FU-203"
-    priority: "P0"
-    dependencies: ["FU-200", "FU-050", "FU-051"]
-  - id: "FU-204"
-    priority: "P0"
-    dependencies: ["FU-200", "FU-050", "FU-051"]
-  - id: "FU-205"
-    priority: "P0"
-    dependencies: ["FU-200", "FU-100"]
-  - id: "FU-206"
-    priority: "P0"
-    dependencies: ["FU-200"]
-
-  # Optional
-  - id: "FU-104"
-    priority: "P1"
-    dependencies: ["FU-100"]
-  - id: "FU-208"
-    priority: "P1"
-    dependencies: ["FU-200"]
-
-execution_schedule:
-  batches:
-    # Batch 0: Infrastructure (can run in parallel)
-    - batch_id: 0
-      feature_units: ["FU-000", "FU-002"]
-      dependencies: []
-
-    # Batch 0.5: Blockchain-ready architecture foundation (can run in parallel)
-    - batch_id: 0.5
-      feature_units: ["FU-050", "FU-051"]
-      dependencies: ["FU-000"]
-
-    # Batch 0.6: Complete blockchain foundation (depends on FU-050)
-    - batch_id: 0.6
-      feature_units: ["FU-052", "FU-053", "FU-054"]
-      dependencies: ["FU-050"]
-
-    # Batch 0.7: Observation architecture storage (can run in parallel after blockchain foundation)
-    - batch_id: 0.7
-      feature_units: ["FU-055", "FU-057"]
-      dependencies: ["FU-050", "FU-051", "FU-052"]
-
-    # Batch 0.8: Observation services (depends on observation storage)
-    - batch_id: 0.8
-      feature_units: ["FU-056", "FU-059"]
-      dependencies: ["FU-055", "FU-057"]
-
-    # Batch 1: MCP core + File analysis (can run in parallel)
-    - batch_id: 1
-      feature_units: ["FU-200", "FU-100"]
-      dependencies: ["FU-000"]
-
-    # Batch 2: Entity and event services (can run in parallel)
-    - batch_id: 2
-      feature_units: ["FU-101", "FU-102"]
-      dependencies: ["FU-100"]
-
-    # Batch 3: Graph builder
-    - batch_id: 3
-      feature_units: ["FU-103"]
-      dependencies: ["FU-101", "FU-102"]
-
-    # Batch 4: Search service
-    - batch_id: 4
-      feature_units: ["FU-105"]
-      dependencies: ["FU-103"]
-
-    # Batch 5: Core MCP actions (can run in parallel, now use event-sourcing)
-    - batch_id: 5
-      feature_units: ["FU-201", "FU-203", "FU-204", "FU-206"]
-      dependencies: ["FU-200", "FU-050", "FU-051"]
-
-    # Batch 6: MCP actions requiring services
-    - batch_id: 6
-      feature_units: ["FU-202", "FU-205"]
-      dependencies: ["FU-200", "FU-105", "FU-100"]
-
-    # Batch 6.5: Observation-aware ingestion (depends on observation services)
-    - batch_id: 6.5
-      feature_units: ["FU-058"]
-      dependencies: ["FU-055", "FU-056", "FU-100", "FU-101"]
-
-    # Batch 6.6: Observation MCP actions (depends on observation services and MCP core)
-    - batch_id: 6.6
-      feature_units: ["FU-061"]
-      dependencies: ["FU-055", "FU-056", "FU-059", "FU-200"]
-
-    # Batch 7: Optional features (can run in parallel)
-    - batch_id: 7
-      feature_units: ["FU-104", "FU-208", "FU-060"]
-      dependencies: ["FU-100", "FU-200", "FU-057", "FU-058"]
-
-checkpoints:
-  checkpoint_0.5_after_batch: 0.6 # Review blockchain foundation before proceeding
-  checkpoint_1_after_batch: 4 # Mid-release review after graph builder and search
-
-acceptance_criteria:
-  product:
-    - criterion: "Core workflow functional via MCP (upload → extraction → query)"
-      test: "tests/integration/mcp_workflow.test.ts"
-      metric: null
-    - criterion: "Entity resolution validated (canonical IDs)"
-      test: "tests/integration/entity_resolution.test.ts"
-      metric: null
-    - criterion: "Timeline events validated"
-      test: "tests/integration/event_generation.test.ts"
-      metric: null
-  technical:
-    - criterion: "All P0 FUs deployed and passing tests"
-      test: null
-      metric: "SELECT COUNT(*) FROM feature_units WHERE priority='P0' AND status='completed'"
-    - criterion: "0 orphan nodes, 0 cycles in memory graph"
-      test: "tests/integration/graph_integrity.test.ts"
-      metric: "SELECT COUNT(*) FROM events WHERE record_id NOT IN (SELECT id FROM records) = 0"
-    - criterion: "Deterministic ingestion (same file → same output)"
-      test: "tests/integration/determinism.test.ts"
-      metric: null
-    - criterion: "Deterministic search ranking"
-      test: "tests/integration/search_determinism.test.ts"
-      metric: null
-    - criterion: "100% critical path test coverage"
-      test: "npm run test:coverage -- --critical-path"
-      metric: "coverage.critical_path >= 100"
-    - criterion: "MCP server operational with 6 core actions"
-      test: "tests/integration/mcp_actions.test.ts"
-      metric: null
-    - criterion: "Event-sourcing foundation operational (events emitted, reducers applied)"
-      test: "tests/integration/event_sourcing.test.ts"
-      metric: null
-    - criterion: "Historical replay functional (get record at timestamp)"
-      test: "tests/integration/historical_replay.test.ts"
-      metric: null
-    - criterion: "Repository abstractions in place (domain logic isolated from storage)"
-      test: "tests/integration/repository_abstractions.test.ts"
-      metric: null
-    - criterion: "Type detection analytics functional (metadata stored, telemetry emitted)"
-      test: "tests/integration/type_detection_analytics.test.ts"
-      metric: null
-    - criterion: "Observation layer operational (observations created, snapshots computed)"
-      test: "tests/integration/observation_flow.test.ts"
-      metric: null
-    - criterion: "4-layer model functional (Document → Entity → Observation → Snapshot)"
-      test: "tests/integration/four_layer_model.test.ts"
-      metric: null
-    - criterion: "Reducer determinism validated (same observations → same snapshot)"
-      test: "tests/integration/reducer_determinism.test.ts"
-      metric: null
-    - criterion: "Provenance tracking functional (every snapshot field traces to observations)"
-      test: "tests/integration/provenance_tracking.test.ts"
-      metric: null
-    - criterion: "Relationship types operational (PART_OF, CORRECTS, etc.)"
-      test: "tests/integration/relationships.test.ts"
-      metric: null
-    - criterion: "Schema registry functional (config-driven schemas loaded and applied)"
-      test: "tests/integration/schema_registry.test.ts"
-      metric: null
-  business:
-    - criterion: "Cursor integration tested"
-      test: null
-      metric: "Manual validation via Cursor MCP integration"
-    - criterion: "ChatGPT integration tested"
-      test: null
-      metric: "Manual validation via ChatGPT MCP integration"
-
-pre_mortem:
-  failure_modes:
-    - mode: "Graph integrity regressions"
-      early_warning: "Integration tests fail, orphan node count > 0"
-      mitigation: "FU-103 includes property-based tests, batch-level integration tests"
-      rollback: "Disable graph builder, revert to single-record inserts"
-    - mode: "Determinism failures"
-      early_warning: "Property-based tests fail, same input produces different output"
-      mitigation: "FU-100, FU-101, FU-102 include determinism tests, 100-run validation"
-      rollback: "Identify and fix nondeterministic code paths"
-    - mode: "MCP action failures"
-      early_warning: "MCP integration tests fail, Cursor/ChatGPT cannot connect"
-      mitigation: "FU-200 includes comprehensive MCP protocol tests"
-      rollback: "Revert MCP server changes, check protocol compliance"
-
-deployment:
-  target: "production" # All releases deploy to production at neotoma.io
-  target_url: "neotoma.io"
-  marketing: false # Not marketed release - no marketing activities
-  rollback_plan: "Revert code changes and redeploy to neotoma.io"
-
-monitoring:
-  key_metrics:
-    - "upload_success_rate"
-    - "upload_latency_p95"
-    - "search_latency_p95"
-    - "graph_orphan_count"
-    - "graph_cycle_count"
-    - "mcp_action_success_rate"
-    - "determinism_test_pass_rate"