Developer Architecture Notes

This index points to architecture references that mirror the live implementation. Always validate statements against the cited source modules.

Core Architecture References

• Daemon and services — lifecycle, IPC, plugin hosting
• Architecture: Daemon and Services
• Plan: Daemon Simplification V2 (FSM-first)
• Plugin pipeline — manifest parsing, trust, runtime loaders
• Architecture: Plugin and Content Extraction
• Search pipeline — ingestion, ranking, hybrid fusion
• Architecture: Search System
• Vector subsystem — embedding providers, storage, repair routines
• Architecture: Vector Search

Supporting Design Notes

• Content handlers and normalization pathways
• Design: Content Handler Architecture
• Synchronization protocol details
• Design: Sync Protocol

API References

• API Overview
• Search API
• Vector Search API
• OpenAPI Definition
• MCP Tools

Operations and Performance Guides

• Admin: Operations
• Deployment Guide
• Monitoring Guide
• Backup Procedures
• Performance Report

Contribution Workflow

1. Update architecture docs and the traceability table (docs/delivery/038/artifacts/architecture-traceability.md) in the same change set.
2. Anchor new prose to specific functions, classes, or modules under src/.
3. Capture validation evidence (integration logs, benchmarks) in docs/delivery/038/artifacts/ with timestamps.
4. Run mkdocs build --strict and archive the log before submitting changes.
5. Flag future work explicitly with issue references; avoid speculative language.

Missing topics should be proposed via issue (outline + intended source references) prior to documentation work.