neotoma 0.3.0 → 0.3.2

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

@@ -1,83 +0,0 @@
-# Feature Unit Specification Status for v0.1.0
-## Specification Status
-### ✅ FUs with Standalone Specs
-| FU ID | Name | Spec Location | Status |
-|-------|------|---------------|--------|
-| FU-050 | Event-Sourcing Foundation | `docs/feature_units/completed/FU-050/FU-050_spec.md` | ✅ Complete |
-| FU-051 | Repository Abstractions | `docs/feature_units/completed/FU-051/FU-051_spec.md` | ✅ Complete |
-| FU-052 | Reducer Versioning | `docs/feature_units/completed/FU-052/FU-052_spec.md` | ✅ Complete |
-| FU-053 | Cryptographic Schema Fields | `docs/feature_units/completed/FU-053/FU-053_spec.md` | ✅ Complete |
-| FU-054 | Hash Chaining Schema Fields | `docs/feature_units/completed/FU-054/FU-054_spec.md` | ✅ Complete |
-**Total:** 5 FUs with standalone specs
-### ⚠️ FUs with Specs in MVP_FEATURE_UNITS.md Only
-These FUs have specifications in `docs/specs/MVP_FEATURE_UNITS.md` but do not have standalone spec files:
-| FU ID | Name | Spec Location | Status in MVP_FEATURE_UNITS.md |
-|-------|------|---------------|-------------------------------|
-| FU-000 | Database Schema v1.0 | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-000) | ✅ Complete |
-| FU-002 | Configuration Management | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-002) | ✅ Complete |
-| FU-055 | Observation Storage Layer | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-055) | ⏳ Not Started |
-| FU-056 | Enhanced Reducer Engine for Observations | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-056) | ⏳ Not Started |
-| FU-057 | Schema Registry Service | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-057) | ⏳ Not Started |
-| FU-058 | Observation-Aware Ingestion Pipeline | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-058) | ⏳ Not Started |
-| FU-059 | Relationship Types | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-059) | ⏳ Not Started |
-| FU-061 | MCP Actions for Observation Architecture | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-061) | ⏳ Not Started |
-| FU-104 | Embedding Service (Optional) | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-104) | ✅ Complete |
-| FU-208 | MCP Provider Integrations (Optional) | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-208) | ⏳ Not Started |
-| FU-100 | File Analysis Service | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-100) | 🔨 Partial |
-| FU-101 | Entity Resolution Service | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-101) | 🔨 Partial |
-| FU-102 | Event Generation Service | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-102) | 🔨 Partial |
-| FU-103 | Graph Builder Service | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-103) | 🔨 Partial |
-| FU-105 | Search Service | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-105) | 🔨 Partial |
-| FU-200 | MCP Server Core | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-200) | ✅ Complete |
-| FU-201 | MCP Action — store_record | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-201) | ✅ Complete |
-| FU-202 | MCP Action — retrieve_records | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-202) | ✅ Complete |
-| FU-203 | MCP Action — update_record | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-203) | ✅ Complete |
-| FU-204 | MCP Action — delete_record | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-204) | ✅ Complete |
-| FU-205 | MCP Action — upload_file | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-205) | ✅ Complete |
-| FU-206 | MCP Action — get_file_url | `docs/specs/MVP_FEATURE_UNITS.md` (Section: FU-206) | ✅ Complete |
-**Total:** 22 FUs with specs in MVP_FEATURE_UNITS.md only (20 P0 + 2 optional P1)
-## Recommendation
-### Option 1: Use MVP_FEATURE_UNITS.md as Source of Truth (Recommended for v0.1.0)
-**Rationale:**
-- MVP_FEATURE_UNITS.md already contains detailed specifications for all FUs
-- Creating standalone specs would duplicate content
-- Standalone specs can be created later if needed for detailed implementation work
-- MVP_FEATURE_UNITS.md is sufficient for release planning and tracking
-**Action:** No changes needed. Use MVP_FEATURE_UNITS.md as the specification source.
-### Option 2: Create Standalone Specs for Critical FUs
-**Rationale:**
-- Standalone specs provide better isolation and reviewability
-- Easier to track individual FU progress
-- Aligns with Feature Unit workflow standards
-**Priority Order for Creating Standalone Specs:**
-**High Priority (Core Services):**
-1. FU-100: File Analysis Service (includes type detection analytics)
-2. FU-101: Entity Resolution Service
-3. FU-102: Event Generation Service
-4. FU-103: Graph Builder Service
-5. FU-105: Search Service
-**Medium Priority (Observation Architecture):**
-6. FU-055: Observation Storage Layer
-7. FU-056: Enhanced Reducer Engine for Observations
-8. FU-057: Schema Registry Service
-9. FU-058: Observation-Aware Ingestion Pipeline
-10. FU-059: Relationship Types
-11. FU-061: MCP Actions for Observation Architecture
-**Lower Priority (Infrastructure - already complete):**
-12. FU-000: Database Schema v1.0 (already complete, spec optional)
-13. FU-002: Configuration Management (already complete, spec optional)
-**Lowest Priority (MCP Actions - already complete):**
-14. FU-200 through FU-206 (already complete, specs optional)
-## Decision
-**For v0.1.0:** Use MVP_FEATURE_UNITS.md as the source of truth. Standalone specs are not required for release planning, but can be created during implementation if needed for detailed work.
-**Future:** Consider creating standalone specs for FUs that require significant implementation work or have complex requirements.
-## Spec Template Reference
-When creating standalone specs, use:
-- Template: `docs/feature_units/standards/feature_unit_spec.md`
-- Manifest template: `docs/feature_units/standards/manifest_template.yaml`
-- Workflow: `docs/feature_units/standards/creating_feature_units.md`
-## Summary
-- **5 FUs** have standalone specs (FU-050 through FU-054)
-- **20 FUs** have specs in MVP_FEATURE_UNITS.md only
-- **Recommendation:** Use MVP_FEATURE_UNITS.md as source of truth for v0.1.0
-- **Optional:** Create standalone specs during implementation if needed for detailed work

package/docs/releases/v0.1.0/implementation_logs/FU-000_implementation_log.md

@@ -1,51 +0,0 @@
-# Implementation Decision Log: FU-000
-**Generated:** 2025-12-14T06:22:09.719Z
-## Overview
-This log documents implementation decisions made for FU-000 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/v0.1.0/implementation_logs/FU-002_implementation_log.md

@@ -1,51 +0,0 @@
-# Implementation Decision Log: FU-002
-**Generated:** 2025-12-14T06:22:09.783Z
-## Overview
-This log documents implementation decisions made for FU-002 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/v0.1.0/implementation_logs/FU-050_implementation_log.md

@@ -1,111 +0,0 @@
-# Implementation Decision Log: FU-050
-**Generated:** 2025-12-14T06:22:41.908Z
-## Overview
-This log documents implementation decisions made for FU-050 and how each requirement from the specification was addressed.
-## Implementation Decisions
-### Decision 1: Events MUST be append-only (never updated or deleted)
-**Requirement:** Events MUST be append-only (never updated or deleted)
-**Location:** Feature Unit: FU-050 Event-Sourcing Foundation > Requirements > Invariants, line 106
-**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: Reducers MUST be pure functions (no side effects, no I/O)
-**Requirement:** Reducers MUST be pure functions (no side effects, no I/O)
-**Location:** Feature Unit: FU-050 Event-Sourcing Foundation > Requirements > Invariants, line 107
-**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: Event schema MUST include all future fields (crypto, hash) e...
-**Requirement:** Event schema MUST include all future fields (crypto, hash) even if unused
-**Location:** Feature Unit: FU-050 Event-Sourcing Foundation > Requirements > Invariants, line 108
-**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: Historical replay MUST be deterministic (same events → same ...
-**Requirement:** Historical replay MUST be deterministic (same events → same state)
-**Location:** Feature Unit: FU-050 Event-Sourcing Foundation > Requirements > Invariants, line 109
-**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 5: Event validation MUST reject invalid events before storage
-**Requirement:** Event validation MUST reject invalid events before storage
-**Location:** Feature Unit: FU-050 Event-Sourcing Foundation > Requirements > Invariants, line 110
-**Type:** must
-**Category:** validation
-**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 6: MUST NOT mutate existing events
-**Requirement:** MUST NOT mutate existing events
-**Location:** Feature Unit: FU-050 Event-Sourcing Foundation > Requirements > Invariants, line 113
-**Type:** must_not
-**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 7: MUST NOT delete events
-**Requirement:** MUST NOT delete events
-**Location:** Feature Unit: FU-050 Event-Sourcing Foundation > Requirements > Invariants, line 114
-**Type:** must_not
-**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 8: MUST NOT have side effects in reducers
-**Requirement:** MUST NOT have side effects in reducers
-**Location:** Feature Unit: FU-050 Event-Sourcing Foundation > Requirements > Invariants, line 115
-**Type:** must_not
-**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 9: MUST NOT skip event validation
-**Requirement:** MUST NOT skip event validation
-**Location:** Feature Unit: FU-050 Event-Sourcing Foundation > Requirements > Invariants, line 116
-**Type:** must_not
-**Category:** validation
-**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 10: MUST NOT write directly to `records` table (only via materia...
-**Requirement:** MUST NOT write directly to `records` table (only via materialized view refresh)
-**Location:** Feature Unit: FU-050 Event-Sourcing Foundation > Requirements > Invariants, line 117
-**Type:** must_not
-**Category:** database
-**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:** 10
-- **Implemented:** 0
-- **Partially Implemented:** 0
-- **Not Implemented:** 10
-- **Deferred:** 0

package/docs/releases/v0.1.0/implementation_logs/FU-051_implementation_log.md

@@ -1,91 +0,0 @@
-# Implementation Decision Log: FU-051
-**Generated:** 2025-12-14T06:22:09.893Z
-## Overview
-This log documents implementation decisions made for FU-051 and how each requirement from the specification was addressed.
-## Implementation Decisions
-### Decision 1: Domain logic MUST use repository interfaces (no direct stora...
-**Requirement:** Domain logic MUST use repository interfaces (no direct storage access)
-**Location:** Feature Unit: FU-051 Repository Abstractions > Requirements > Invariants, line 78
-**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: Repository implementations MUST be swappable (same interface...
-**Requirement:** Repository implementations MUST be swappable (same interface, different backend)
-**Location:** Feature Unit: FU-051 Repository Abstractions > Requirements > Invariants, line 79
-**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: File repositories MUST produce identical results to DB repos...
-**Requirement:** File repositories MUST produce identical results to DB repositories
-**Location:** Feature Unit: FU-051 Repository Abstractions > Requirements > Invariants, line 80
-**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: Repository operations MUST be deterministic
-**Requirement:** Repository operations MUST be deterministic
-**Location:** Feature Unit: FU-051 Repository Abstractions > Requirements > Invariants, line 81
-**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 5: MUST NOT have direct DB access in domain layer
-**Requirement:** MUST NOT have direct DB access in domain layer
-**Location:** Feature Unit: FU-051 Repository Abstractions > Requirements > Invariants, line 84
-**Type:** must_not
-**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 6: MUST NOT have file I/O in domain layer
-**Requirement:** MUST NOT have file I/O in domain layer
-**Location:** Feature Unit: FU-051 Repository Abstractions > Requirements > Invariants, line 85
-**Type:** must_not
-**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 7: MUST NOT break backward compatibility (existing data readabl...
-**Requirement:** MUST NOT break backward compatibility (existing data readable)
-**Location:** Feature Unit: FU-051 Repository Abstractions > Requirements > Invariants, line 86
-**Type:** must_not
-**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 8: MUST NOT introduce non-determinism
-**Requirement:** MUST NOT introduce non-determinism
-**Location:** Feature Unit: FU-051 Repository Abstractions > Requirements > Invariants, line 87
-**Type:** must_not
-**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:** 8
-- **Implemented:** 0
-- **Partially Implemented:** 0
-- **Not Implemented:** 8
-- **Deferred:** 0

package/docs/releases/v0.1.0/implementation_logs/FU-052_implementation_log.md

@@ -1,81 +0,0 @@
-# Implementation Decision Log: FU-052
-**Generated:** 2025-12-14T06:22:09.978Z
-## Overview
-This log documents implementation decisions made for FU-052 and how each requirement from the specification was addressed.
-## Implementation Decisions
-### Decision 1: Events MUST include `reducer_version` metadata
-**Requirement:** Events MUST include `reducer_version` metadata
-**Location:** Feature Unit: FU-052 Reducer Versioning > Requirements > Invariants, line 83
-**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: Reducer registry MUST map version → reducer function
-**Requirement:** Reducer registry MUST map version → reducer function
-**Location:** Feature Unit: FU-052 Reducer Versioning > Requirements > Invariants, line 84
-**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: Reducer application MUST use correct version for each event
-**Requirement:** Reducer application MUST use correct version for each event
-**Location:** Feature Unit: FU-052 Reducer Versioning > Requirements > Invariants, line 85
-**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: Old events MUST be replayable with version "1.0" reducer
-**Requirement:** Old events MUST be replayable with version "1.0" reducer
-**Location:** Feature Unit: FU-052 Reducer Versioning > Requirements > Invariants, line 86
-**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 5: MUST NOT break backward compatibility (old events must work)
-**Requirement:** MUST NOT break backward compatibility (old events must work)
-**Location:** Feature Unit: FU-052 Reducer Versioning > Requirements > Invariants, line 89
-**Type:** must_not
-**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 6: MUST NOT allow runtime reducer registry changes
-**Requirement:** MUST NOT allow runtime reducer registry changes
-**Location:** Feature Unit: FU-052 Reducer Versioning > Requirements > Invariants, line 90
-**Type:** must_not
-**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 7: MUST NOT skip version checking
-**Requirement:** MUST NOT skip version checking
-**Location:** Feature Unit: FU-052 Reducer Versioning > Requirements > Invariants, line 91
-**Type:** must_not
-**Category:** validation
-**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:** 7
-- **Implemented:** 0
-- **Partially Implemented:** 0
-- **Not Implemented:** 7
-- **Deferred:** 0

package/docs/releases/v0.1.0/implementation_logs/FU-053_implementation_log.md

@@ -1,71 +0,0 @@
-# Implementation Decision Log: FU-053
-**Generated:** 2025-12-14T06:22:10.027Z
-## Overview
-This log documents implementation decisions made for FU-053 and how each requirement from the specification was addressed.
-## Implementation Decisions
-### Decision 1: Schema fields MUST be nullable (no breaking changes)
-**Requirement:** Schema fields MUST be nullable (no breaking changes)
-**Location:** Feature Unit: FU-053 Cryptographic Schema Fields > Requirements > Invariants, line 70
-**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: Agent identity abstraction MUST exist (even if stub)
-**Requirement:** Agent identity abstraction MUST exist (even if stub)
-**Location:** Feature Unit: FU-053 Cryptographic Schema Fields > Requirements > Invariants, line 71
-**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: Schema MUST support future crypto implementation
-**Requirement:** Schema MUST support future crypto implementation
-**Location:** Feature Unit: FU-053 Cryptographic Schema Fields > Requirements > Invariants, line 72
-**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: MUST NOT break existing events (fields nullable)
-**Requirement:** MUST NOT break existing events (fields nullable)
-**Location:** Feature Unit: FU-053 Cryptographic Schema Fields > Requirements > Invariants, line 75
-**Type:** must_not
-**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 5: MUST NOT implement signature verification yet (deferred)
-**Requirement:** MUST NOT implement signature verification yet (deferred)
-**Location:** Feature Unit: FU-053 Cryptographic Schema Fields > Requirements > Invariants, line 76
-**Type:** must_not
-**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 6: MUST NOT require signatures for events (optional)
-**Requirement:** MUST NOT require signatures for events (optional)
-**Location:** Feature Unit: FU-053 Cryptographic Schema Fields > Requirements > Invariants, line 77
-**Type:** must_not
-**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:** 6
-- **Implemented:** 0
-- **Partially Implemented:** 0
-- **Not Implemented:** 6
-- **Deferred:** 0

package/docs/releases/v0.1.0/implementation_logs/FU-054_implementation_log.md

@@ -1,71 +0,0 @@
-# Implementation Decision Log: FU-054
-**Generated:** 2025-12-14T06:22:10.100Z
-## Overview
-This log documents implementation decisions made for FU-054 and how each requirement from the specification was addressed.
-## Implementation Decisions
-### Decision 1: Schema fields MUST be nullable (no breaking changes)
-**Requirement:** Schema fields MUST be nullable (no breaking changes)
-**Location:** Feature Unit: FU-054 Hash Chaining Schema Fields > Requirements > Invariants, line 71
-**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: Hash computation utilities MUST exist (even if stub)
-**Requirement:** Hash computation utilities MUST exist (even if stub)
-**Location:** Feature Unit: FU-054 Hash Chaining Schema Fields > Requirements > Invariants, line 72
-**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: Schema MUST support future Merkle implementation
-**Requirement:** Schema MUST support future Merkle implementation
-**Location:** Feature Unit: FU-054 Hash Chaining Schema Fields > Requirements > Invariants, line 73
-**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: MUST NOT break existing events (fields nullable)
-**Requirement:** MUST NOT break existing events (fields nullable)
-**Location:** Feature Unit: FU-054 Hash Chaining Schema Fields > Requirements > Invariants, line 76
-**Type:** must_not
-**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 5: MUST NOT implement Merkle root computation yet (deferred)
-**Requirement:** MUST NOT implement Merkle root computation yet (deferred)
-**Location:** Feature Unit: FU-054 Hash Chaining Schema Fields > Requirements > Invariants, line 77
-**Type:** must_not
-**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 6: MUST NOT require hashes for events (optional)
-**Requirement:** MUST NOT require hashes for events (optional)
-**Location:** Feature Unit: FU-054 Hash Chaining Schema Fields > Requirements > Invariants, line 78
-**Type:** must_not
-**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:** 6
-- **Implemented:** 0
-- **Partially Implemented:** 0
-- **Not Implemented:** 6
-- **Deferred:** 0