neotoma 0.3.0 → 0.3.2

package/docs/reference/error_codes.md

@@ -1,223 +0,0 @@
-# Error Codes Reference
-*(Complete Catalog of Neotoma Error Codes)*
-## Scope
-This document covers:
-- All canonical error codes and their meanings
-- HTTP status code mappings
-- Retry eligibility
-- Common causes and solutions
-This document does NOT cover:
-- Error handling implementation (see `docs/subsystems/errors.md`)
-- Error propagation patterns (see `docs/architecture/architecture.md`)
-## Error Envelope Format
-All errors follow this structure:
-```typescript
-interface ErrorEnvelope {
-  error_code: string;              // Canonical error code
-  message: string;                 // Human-readable description
-  details?: Record<string, any>;   // Additional context (no PII)
-  trace_id?: string;               // Distributed tracing ID
-  timestamp: string;               // ISO 8601
-}
-```
-## Ingestion Errors
-| Code | HTTP | Retry? | Description |
-|------|------|--------|-------------|
-| `INGESTION_FILE_TOO_LARGE` | 400 | No | File exceeds maximum size (50MB) |
-| `INGESTION_UNSUPPORTED_TYPE` | 400 | No | File type not supported (PDF, JPG, PNG only) |
-| `INGESTION_INVALID_FILE` | 400 | No | File is corrupted or invalid format |
-| `INGESTION_OCR_FAILED` | 500 | Yes | OCR processing failed (Tesseract error) |
-| `INGESTION_EXTRACTION_FAILED` | 500 | No | Field extraction failed (schema error) |
-| `INGESTION_NORMALIZATION_FAILED` | 500 | Yes | File format conversion failed |
-| `INGESTION_SCHEMA_DETECTION_FAILED` | 500 | No | Could not detect document schema |
-| `INGESTION_STORAGE_FAILED` | 500 | Yes | Failed to store file in storage |
-**Common Causes:**
-- `INGESTION_FILE_TOO_LARGE`: File >50MB
-- `INGESTION_UNSUPPORTED_TYPE`: File is not PDF, JPG, or PNG
-- `INGESTION_OCR_FAILED`: Image has no readable text or Tesseract error
-## Authentication Errors
-| Code | HTTP | Retry? | Description |
-|------|------|--------|-------------|
-| `AUTH_REQUIRED` | 401 | No | No bearer token provided |
-| `AUTH_INVALID` | 401 | No | Bearer token is invalid |
-| `AUTH_EXPIRED` | 401 | No | Bearer token has expired |
-| `AUTH_MALFORMED` | 401 | No | Bearer token format is invalid |
-| `FORBIDDEN` | 403 | No | Insufficient permissions (RLS policy violation) |
-**Common Causes:**
-- `AUTH_REQUIRED`: Missing `Authorization: Bearer <token>` header
-- `AUTH_INVALID`: Token doesn't match `ACTIONS_BEARER_TOKEN`
-- `FORBIDDEN`: User doesn't have access to requested resource (RLS)
-## Database Errors
-| Code | HTTP | Retry? | Description |
-|------|------|--------|-------------|
-| `DB_CONNECTION_FAILED` | 503 | Yes | Cannot connect to database |
-| `DB_QUERY_FAILED` | 500 | Yes | Query execution failed |
-| `DB_CONSTRAINT_VIOLATION` | 409 | No | Unique constraint violated (duplicate record) |
-| `DB_TRANSACTION_FAILED` | 500 | Yes | Transaction rollback failed |
-| `DB_TIMEOUT` | 504 | Yes | Database query timed out |
-
-### Resource Errors
-| Code | HTTP | Retry? | Meaning |
-|------|------|--------|---------|
-| `RESOURCE_NOT_FOUND` | 404 | No | Requested resource does not exist |
-**Common Causes:**
-- `DB_CONNECTION_FAILED`: Database unavailable or network issue
-- `DB_CONSTRAINT_VIOLATION`: Attempting to create duplicate record
-- `DB_TIMEOUT`: Query taking too long (large dataset or missing index)
-## Entity Resolution Errors
-| Code | HTTP | Retry? | Description |
-|------|------|--------|-------------|
-| `ENTITY_NORMALIZATION_FAILED` | 500 | No | Entity name normalization failed |
-| `ENTITY_ID_GENERATION_FAILED` | 500 | No | Failed to generate canonical entity ID |
-| `ENTITY_TYPE_INVALID` | 400 | No | Invalid entity type (must be person, company, location) |
-**Common Causes:**
-- `ENTITY_NORMALIZATION_FAILED`: Entity name is empty or invalid
-- `ENTITY_TYPE_INVALID`: Entity type not in allowed set
-## Search Errors
-| Code | HTTP | Retry? | Description |
-|------|------|--------|-------------|
-| `SEARCH_QUERY_INVALID` | 400 | No | Search query is malformed |
-| `SEARCH_INDEX_UNAVAILABLE` | 503 | Yes | Search index is not ready (eventual consistency) |
-| `SEARCH_LIMIT_EXCEEDED` | 400 | No | Limit exceeds maximum (1000) |
-**Common Causes:**
-- `SEARCH_QUERY_INVALID`: Invalid search_mode or malformed query
-- `SEARCH_INDEX_UNAVAILABLE`: Full-text index still building (max 5s delay)
-## File Storage Errors
-| Code | HTTP | Retry? | Description |
-|------|------|--------|-------------|
-| `STORAGE_BUCKET_NOT_FOUND` | 404 | No | Storage bucket doesn't exist |
-| `STORAGE_UPLOAD_FAILED` | 500 | Yes | File upload to storage failed |
-| `STORAGE_DELETE_FAILED` | 500 | Yes | File deletion from storage failed |
-| `STORAGE_SIGNED_URL_FAILED` | 500 | Yes | Failed to generate signed URL |
-**Common Causes:**
-- `STORAGE_BUCKET_NOT_FOUND`: Storage bucket not configured
-- `STORAGE_UPLOAD_FAILED`: Network issue or storage quota exceeded
-## Integration Errors
-### Plaid Errors
-| Code | HTTP | Retry? | Description |
-|------|------|--------|-------------|
-| `PLAID_LINK_TOKEN_EXPIRED` | 400 | No | Link token has expired (4 hours) |
-| `PLAID_ITEM_NOT_FOUND` | 404 | No | Plaid item doesn't exist |
-| `PLAID_SYNC_FAILED` | 500 | Yes | Transaction sync failed |
-| `PLAID_RATE_LIMIT_EXCEEDED` | 429 | Yes | Plaid API rate limit exceeded |
-| `PLAID_INVALID_CREDENTIALS` | 401 | No | Plaid client_id or secret invalid |
-**Common Causes:**
-- `PLAID_LINK_TOKEN_EXPIRED`: Token older than 4 hours
-- `PLAID_RATE_LIMIT_EXCEEDED`: Too many API calls (500/min sandbox)
-### External Provider Errors
-| Code | HTTP | Retry? | Description |
-|------|------|--------|-------------|
-| `PROVIDER_OAUTH_FAILED` | 500 | Yes | OAuth flow failed |
-| `PROVIDER_TOKEN_EXPIRED` | 401 | No | OAuth token expired (refresh required) |
-| `PROVIDER_RATE_LIMIT_EXCEEDED` | 429 | Yes | Provider API rate limit exceeded |
-| `PROVIDER_CONNECTOR_NOT_FOUND` | 404 | No | Connector doesn't exist |
-| `PROVIDER_SYNC_FAILED` | 500 | Yes | Provider sync failed |
-**Common Causes:**
-- `PROVIDER_TOKEN_EXPIRED`: OAuth token needs refresh
-- `PROVIDER_RATE_LIMIT_EXCEEDED`: Exceeded provider's rate limits
-### MCP OAuth Errors
-| Code | HTTP | Retry? | Description |
-|------|------|--------|-------------|
-| `OAUTH_CLIENT_REGISTRATION_FAILED` | 500 | No | Dynamic OAuth client registration failed |
-| `OAUTH_STATE_INVALID` | 400 | No | Invalid or missing OAuth state token |
-| `OAUTH_STATE_EXPIRED` | 400 | No | OAuth state token expired (10 minute limit) |
-| `OAUTH_TOKEN_EXCHANGE_FAILED` | 500 | Yes | Failed to exchange authorization code for tokens |
-| `OAUTH_TOKEN_REFRESH_FAILED` | 401 | Yes | Failed to refresh access token |
-| `OAUTH_CONNECTION_NOT_FOUND` | 404 | No | MCP OAuth connection not found |
-| `OAUTH_CONNECTION_REVOKED` | 403 | No | Connection has been revoked by user |
-| `OAUTH_ENCRYPTION_KEY_MISSING` | 500 | No | Token encryption key not configured |
-| `OAUTH_ENCRYPTION_KEY_INVALID` | 500 | No | Encryption key format is invalid (must be 64 hex chars) |
-| `OAUTH_INVALID_REDIRECT_URI` | 400 | No | Redirect URI format validation failed |
-| `OAUTH_DECRYPTION_FAILED` | 500 | No | Failed to decrypt refresh token |
-| `OAUTH_USER_INFO_FAILED` | 500 | Yes | Failed to get user info from access token |
-**Common Causes:**
-- `OAUTH_CLIENT_REGISTRATION_FAILED`: OAuth client not configured or missing env var
-- `OAUTH_STATE_INVALID`: State token not found in database or already consumed
-- `OAUTH_STATE_EXPIRED`: State created more than 10 minutes ago
-- `OAUTH_TOKEN_REFRESH_FAILED`: Refresh token expired or invalid, user needs to re-authenticate
-- `OAUTH_CONNECTION_NOT_FOUND`: Connection_id doesn't exist or was deleted
-- `OAUTH_ENCRYPTION_KEY_MISSING`: MCP_TOKEN_ENCRYPTION_KEY not set in environment
-- `OAUTH_DECRYPTION_FAILED`: Invalid encrypted token format or wrong encryption key
-## Validation Errors
-| Code | HTTP | Retry? | Description |
-|------|------|--------|-------------|
-| `VALIDATION_MISSING_FIELD` | 400 | No | Required field is missing |
-| `VALIDATION_INVALID_TYPE` | 400 | No | Field has invalid type |
-| `VALIDATION_INVALID_FORMAT` | 400 | No | Field format is invalid (e.g., date) |
-| `VALIDATION_OUT_OF_RANGE` | 400 | No | Field value out of allowed range |
-**Common Causes:**
-- `VALIDATION_MISSING_FIELD`: Missing required `type` or `properties`
-- `VALIDATION_INVALID_FORMAT`: Invalid date format or JSON structure
-## Graph Errors
-| Code | HTTP | Retry? | Description |
-|------|------|--------|-------------|
-| `GRAPH_ORPHAN_NODE` | 500 | No | Attempted to create orphan node (violates integrity) |
-| `GRAPH_CYCLE_DETECTED` | 500 | No | Graph cycle detected (should not occur) |
-| `GRAPH_EDGE_INVALID` | 400 | No | Invalid edge type or source/target |
-**Common Causes:**
-- `GRAPH_ORPHAN_NODE`: Entity or event created without record link
-- `GRAPH_EDGE_INVALID`: Invalid edge type (not in allowed set)
-## Generic Errors
-| Code | HTTP | Retry? | Description |
-|------|------|--------|-------------|
-| `INTERNAL_ERROR` | 500 | Yes | Unexpected server error |
-| `SERVICE_UNAVAILABLE` | 503 | Yes | Service temporarily unavailable |
-| `TIMEOUT` | 504 | Yes | Request timed out |
-| `NOT_IMPLEMENTED` | 501 | No | Feature not yet implemented |
-**Common Causes:**
-- `INTERNAL_ERROR`: Unexpected exception (check logs with trace_id)
-- `SERVICE_UNAVAILABLE`: Database or external service down
-## Retry Guidelines
-### Retry Eligible (Yes)
-- Network errors (`DB_CONNECTION_FAILED`, `TIMEOUT`)
-- Transient errors (`SERVICE_UNAVAILABLE`, `SEARCH_INDEX_UNAVAILABLE`)
-- Rate limits (`PLAID_RATE_LIMIT_EXCEEDED`, `PROVIDER_RATE_LIMIT_EXCEEDED`)
-**Retry Strategy:**
-- Exponential backoff: `delay = 2^attempt * 1000ms`
-- Max retries: 3-5 attempts
-- Jitter: Add random 0-1000ms to prevent thundering herd
-### Not Retry Eligible (No)
-- Client errors (4xx): Fix request before retrying
-- Validation errors: Correct input format
-- Authentication errors: Fix token/credentials
-- Constraint violations: Handle duplicate/conflict
-## Error Code Format
-Error codes follow this pattern:
-```
-<CATEGORY>_<SPECIFIC_ERROR>
-```
-**Categories:**
-- `INGESTION_*`: File upload and processing
-- `AUTH_*`: Authentication and authorization
-- `DB_*`: Database operations
-- `ENTITY_*`: Entity resolution
-- `SEARCH_*`: Search operations
-- `STORAGE_*`: File storage
-- `PLAID_*`: Plaid integration
-- `PROVIDER_*`: External provider integrations
-- `OAUTH_*`: MCP OAuth authentication
-- `VALIDATION_*`: Input validation
-- `GRAPH_*`: Graph operations
-## Agent Instructions
-### When to Load This Document
-Load when:
-- Implementing error handling
-- Debugging API errors
-- Adding new error codes
-- Understanding error responses
-### Required Co-Loaded Documents
-- `docs/subsystems/errors.md` — Error handling patterns
-- `docs/architecture/architecture.md` — Error propagation
-- `docs/api/rest_api.md` — API error responses
-### Constraints Agents Must Enforce
-1. **Use canonical error codes** — Don't invent new codes without updating this doc
-2. **Include trace_id** — For distributed tracing
-3. **Never include PII** — In error details
-4. **Follow retry guidelines** — Respect retry eligibility
-5. **Update this doc** — When adding new error codes
-### Forbidden Patterns
-- Creating ad-hoc error codes without documentation
-- Including PII in error details
-- Retrying non-retryable errors
-- Ignoring error codes in error handling
-- Using generic errors when specific code exists

package/docs/releases/archived/aspirational/README.md

@@ -1,57 +0,0 @@
-# Archived Aspirational Releases
-
-These releases were planned but did not represent actual implementation. They have been archived as part of the v0.3.0 reconciliation release (2025-02-05) to establish an accurate baseline between documented releases and actual codebase state.
-
-## Archived Releases
-
-| Release | Original Purpose | Status | Archived Date |
-|---------|------------------|--------|---------------|
-| v0.4.0 | Intelligence + Housekeeping | Planning | 2025-02-05 |
-| v0.5.0 | Agent Cryptographic Signing | Planning | 2025-02-05 |
-| v0.9.0 | MCP Support System | Planning | 2025-02-05 |
-| v1.0.0 | MVP | Planning | 2025-02-05 |
-| v2.0.0 | End-to-End Encryption | Planning | 2025-02-05 |
-| v2.1.0 | GDPR & US State Privacy Compliance | Planning | 2025-02-05 |
-| v2.2.0 | HNSW Vector Search Optimization | Planning | 2025-02-05 |
-
-## Why Archived
-
-During late 2024 and early 2025, significant development work occurred outside the formal release process. This created a gap between documented releases (which included many aspirational "planning" releases) and actual implementation.
-
-These releases were never implemented and do not reflect the actual state of the codebase. They remain here for historical reference and can be revisited for future planning.
-
-## What Happened Instead
-
-The actual implemented features during this period included:
-- Schema registry system
-- Sources-first architecture with observations
-- Entity system with resolution
-- Auto-enhancement system
-- MCP OAuth integration
-- Frontend development
-- CLI development
-- Foundation submodule integration
-- Comprehensive documentation
-
-These implementations were documented in the v0.3.0 reconciliation release.
-
-## Going Forward
-
-Future releases will be planned realistically based on the v0.3.0 baseline (which accurately documents current implementation). The release process will follow proper Feature Unit workflow to prevent this type of drift.
-
-## Lessons Learned
-
-1. **Release discipline matters** - Even in solo/rapid development, tracking prevents drift
-2. **Document as you go** - Retroactive documentation is harder and less accurate
-3. **Aspirational releases can mislead** - Planning too far ahead without implementation creates confusion
-4. **Feature Unit workflow prevents drift** - When followed consistently
-
-## References
-
-- [v0.3.0 Reconciliation Release](../../v0.3.0/release_plan.md) - Documents actual current state
-- [v0.2.15 Release](../../v0.2.15/status.md) - Last documented implemented release before reconciliation
-- [Release Workflow](../../../developer/release_workflow.md) - Proper release process going forward
-
----
-
-**Note:** These archived releases remain available for reference and for mining ideas for future planning, but they should not be considered as reflecting actual implementation history.

package/docs/releases/archived/aspirational/v0.4.0/manifest.yaml

@@ -1,94 +0,0 @@
-release:
-  id: v0.4.0
-  name: Intelligence + Housekeeping
-  type: "not_marketed"
-  priority: P2
-  status: planning
-  target_ship_date: null # After v0.3.0 is stable
-  owner: Mark Hendrickson
-  marketing_required: false
-  gate: "v0.3.0 must be stable before starting"
-  guiding_principle: "These features are only valuable with volume/diversity of data"
-
-dependencies:
-  - v0.3.0 # Operational Hardening
-
-feature_units:
-  # Intelligence Workers (deferred from v0.3.0)
-  - id: FU-133
-    name: Duplicate Detection Worker
-    priority: P1
-    status: not_started
-    dependencies: []
-    phase: 1
-    description: Heuristic duplicate flagging (weekly cron)
-
-  # Housekeeping Workers (deferred from v0.3.0)
-  - id: FU-132
-    name: Archival Job
-    priority: P1
-    status: not_started
-    dependencies: []
-    phase: 1
-    description: Old interpretation run archival (180 days)
-
-  # Schema Analytics
-  - id: FU-137
-    name: Raw Fragments Analytics
-    priority: P2
-    status: not_started
-    dependencies: []
-    phase: 2
-    description: Analytics on raw_fragments for schema promotion candidates
-
-  # Utility Tools (may be sequenced separately)
-  - id: FU-106
-    name: Chat Transcript Extraction CLI
-    priority: P2
-    status: not_started
-    dependencies: []
-    phase: 2
-    description: Standalone CLI for converting chat transcripts to JSON
-
-scope:
-  included:
-    - FU-132: Archival Job
-    - FU-133: Duplicate Detection Worker
-    - FU-137: Raw Fragments Analytics
-    - FU-106: Chat Transcript Extraction CLI (tentative)
-
-  deferred_v1x:
-    - Automated merge suggestions
-    - Semantic search integration
-    - Model-selection UI
-    - Multi-user organization features
-
-acceptance_criteria:
-  product:
-    - Duplicate entities are flagged for review
-    - Old interpretation runs are archived
-    - Schema promotion candidates are identified
-
-  technical:
-    - Duplicate Detection Worker functional
-    - Archival Job functional
-    - Raw Fragments analytics available
-
-  business:
-    - Intelligence improves data quality
-    - Housekeeping reduces storage costs
-    - Schema discovery enables evolution
-
-success_criteria:
-  - Duplicate Detection Worker functional
-  - Archival Job functional
-  - Raw Fragments analytics available
-  - Integration tests passing
-
-release_spacing:
-  v020: "Minimal ingestion + correction loop (foundation)"
-  v030: "Operational hardening (prerequisite)"
-  v040: "Intelligence + housekeeping (this release)"
-  v1x: "Experience + growth (future)"
-
-

package/docs/releases/archived/aspirational/v0.4.0/release_plan.md

@@ -1,51 +0,0 @@
-## Release v0.4.0 — Intelligence + Housekeeping
-### 1. Release Overview
-- **Release ID**: `v0.4.0`
-- **Name**: Intelligence + Housekeeping
-- **Release Type**: Not Marketed (production deployment without marketing activities)
-- **Goal**: Add intelligent features (duplicate detection, schema discovery) and housekeeping (archival) after operational hardening in v0.3.0 has proven stable.
-- **Priority**: P2 (intelligence and maintenance)
-- **Target Ship Date**: After v0.3.0 (Operational Hardening) is stable
-- **Marketing Required**: No (not marketed release)
-- **Deployment**: Production (neotoma.io)
-#### 1.0 Guiding Principle
-> These features are only valuable with volume/diversity of data.
-This release is gated on v0.3.0 stability: operational hardening must be proven before investing in intelligence and long-term maintenance features.
-### 2. Scope
-#### 2.1 Included Feature Units (Deferred from v0.3.0)
-**Intelligence Workers**
-- `FU-133`: Duplicate Detection Worker (heuristic duplicate flagging)
-- Early schema promotion from `raw_fragments` (analytics on unknown fields)
-**Housekeeping Workers**
-- `FU-132`: Archival Job (old interpretation run archival)
-**Utility Tools**
-- Chat Transcript Extraction CLI (FU-106) — may be included or sequenced separately
-#### 2.2 Explicitly Deferred
-| Item | Deferred To | Reason |
-|------|-------------|--------|
-| Automated merge suggestions | v1.x | Requires mature duplicate detection |
-| Semantic search integration | v1.x | Leverage feature for proven core |
-| Model-selection UI | v1.x | Use config/env until validated |
-| Multi-user organization features | v1.x | Should not block Tier 1 ICP validation |
-### 3. Success Criteria
-**Release is Complete When:**
-1. ✅ Duplicate Detection Worker functional (weekly cron)
-2. ✅ Archival Job functional (180-day archival)
-3. ✅ Schema analytics on `raw_fragments` available
-4. ✅ Chat Transcript CLI functional (if included)
-5. ✅ Integration tests for intelligence features
-### 4. Release Spacing Context
-| Release | Focus | Status |
-|---------|-------|--------|
-| **v0.2.0** | Minimal ingestion + correction loop | Foundation |
-| **v0.3.0** | Operational hardening | Prerequisite |
-| **v0.4.0** | Intelligence + housekeeping | This release |
-| **v1.x** | Experience + growth | Future |
-### 5. Status
-- **Current Status**: `planning`
-- **Owner**: Mark Hendrickson
-- **Gate**: v0.3.0 must be stable before starting v0.4.0
-- **Notes**:
-  - Intelligence and long-term maintenance layer
-  - Requires data volume to justify heuristics
-  - Chat Transcript CLI may be included or separate

package/docs/releases/archived/aspirational/v0.5.0/manifest.yaml

@@ -1,152 +0,0 @@
-release:
-  id: v0.5.0
-  name: Agent Cryptographic Signing
-  type: "not_marketed"
-  priority: P1
-  status: planning
-  target_ship_date: null # After v0.3.0 validation, before v1.0.0
-  owner: Mark Hendrickson
-  marketing_required: false
-  gate: "v0.3.0 must be validated with real usage before starting"
-  guiding_principle: "Enable cryptographic attribution and permissioning for multi-agent systems without breaking existing workflows"
-
-dependencies:
-  - v0.3.0 # Operational Hardening
-
-feature_units:
-  # Phase 1: Core Infrastructure
-  - id: FU-200
-    name: Agent Keypair Generation Utilities
-    priority: P0
-    status: not_started
-    dependencies: []
-    phase: 1
-    description: Client-side utilities for generating per-chat Ed25519 keypairs, key storage, and key management
-
-  - id: FU-201
-    name: Payload Signature Extension
-    priority: P0
-    status: not_started
-    dependencies: []
-    phase: 1
-    description: Extend PayloadEnvelope provenance to include signer_public_key and signature fields
-
-  - id: FU-202
-    name: Agent Identity Service Implementation
-    priority: P0
-    status: not_started
-    dependencies: [FU-200]
-    phase: 1
-    description: Implement getAgentPublicKey() to extract public key from request context, replace stub
-
-  # Phase 2: MCP Integration
-  - id: FU-203
-    name: MCP Payload Signing
-    priority: P0
-    status: not_started
-    dependencies: [FU-200, FU-201]
-    phase: 2
-    description: MCP client library helpers for signing submit_payload requests with agent keypairs
-
-  - id: FU-204
-    name: Signature Verification Middleware
-    priority: P0
-    status: not_started
-    dependencies: [FU-201, FU-202]
-    phase: 2
-    description: Verify payload signatures in submit_payload handler (optional initially, required post-MVP)
-
-  # Phase 3: Permission System Foundation
-  - id: FU-205
-    name: Agent Public Key Registry
-    priority: P1
-    status: not_started
-    dependencies: [FU-202]
-    phase: 3
-    description: Registry for agent public keys with metadata (agent_id, permissions, created_at, revoked_at)
-
-  - id: FU-206
-    name: Permission Enforcement Framework
-    priority: P1
-    status: not_started
-    dependencies: [FU-205]
-    phase: 3
-    description: Permission checking based on public key (read-only, write, financial operations, etc.)
-
-deferred_to_post_mvp:
-  - id: FU-207
-    name: Required Signatures
-    description: Make signatures mandatory for all write operations
-    reason: Requires migration period for existing clients
-
-  - id: FU-208
-    name: Agent Trust Profiles
-    description: User-configurable trust levels per agent public key
-    reason: Requires UI and user workflow
-
-  - id: FU-209
-    name: Agent Revocation UI
-    description: UI for revoking agent access
-    reason: Requires UI layer (v1.0.0+)
-
-scope:
-  included:
-    - FU-200: Agent Keypair Generation Utilities
-    - FU-201: Payload Signature Extension
-    - FU-202: Agent Identity Service Implementation
-    - FU-203: MCP Payload Signing
-    - FU-204: Signature Verification Middleware
-    - FU-205: Agent Public Key Registry (P1, optional)
-    - FU-206: Permission Enforcement Framework (P1, optional)
-
-  deferred_post_mvp:
-    - FU-207: Required Signatures (migration period needed)
-    - FU-208: Agent Trust Profiles (requires UI)
-    - FU-209: Agent Revocation UI (requires UI layer)
-
-  excluded:
-    - UI components (v1.0.0+)
-    - Multi-user agent management (v1.0.0+)
-    - Agent analytics dashboard (v1.0.0+)
-
-acceptance_criteria:
-  product:
-    - Agents can generate Ed25519 keypairs per chat session
-    - Payloads can include cryptographic signatures
-    - Signatures are verified (when provided)
-    - Agent public keys are extractable from request context
-    - MCP clients can sign payloads using provided utilities
-
-  technical:
-    - generateEd25519KeyPair() available for client-side use
-    - PayloadEnvelope.provenance includes signer_public_key and signature fields
-    - getAgentPublicKey() extracts public key from request context
-    - Signature verification in submit_payload handler (optional)
-    - MCP client library helpers for signing
-    - Agent public key registry table (if FU-205 included)
-    - Permission checking framework (if FU-206 included)
-
-  business:
-    - Enables multi-agent coordination with attribution
-    - Foundation for permission system
-    - Cryptographic audit trail for compliance
-    - Backward compatible (signatures optional initially)
-
-success_criteria:
-  - Agent keypair generation utilities functional
-  - Payload signatures can be included and verified
-  - MCP clients can sign payloads
-  - Signature verification middleware functional
-  - Integration tests passing
-  - Backward compatibility maintained (unsigned payloads still work)
-  - Documentation updated (MCP_SPEC.md, source_material_model.md)
-
-release_spacing:
-  v030: "Operational hardening (prerequisite)"
-  v050: "Agent cryptographic signing (this release)"
-  v040: "Intelligence + housekeeping (can run in parallel)"
-  v1x: "Experience + growth (future)"
-
-
-
-