Project MCP

--- title: Architecture Decisions created: '2026-01-01' updated: '2026-01-01' --- # Architecture Decisions This document records architecture decisions, trade-offs, and rationale for this project. ## ADR-001: Use PostgreSQL for Primary Database **Date:** January 1, 2025 **Status:** accepted **Tags:** database, infrastructure ### Context Need to choose a primary database for the application. Options considered: - PostgreSQL - MySQL - MongoDB - SQLite ### Decision Use PostgreSQL as the primary database. ### Consequences **Positive:** - Strong data integrity with ACID compliance - Excellent JSON support for flexible data - Rich ecosystem and tooling - Great performance with proper indexing **Negative:** - More complex setup than SQLite - Requires separate database server - Learning curve for JSON/JSONB features ## ADR-002: Adopt YAML Frontmatter for Task Files **Date:** January 1, 2025 **Status:** accepted **Tags:** tasks, workflow, tooling ### Context Need a format for storing task metadata that is: - Human readable - Machine parseable - Compatible with markdown - Works with git versioning ### Decision Use YAML frontmatter at the top of markdown files for task metadata. ### Consequences **Positive:** - Metadata is clearly separated from content - Standard format supported by many tools - Easy to parse programmatically - Human readable and editable **Negative:** - Requires frontmatter parsing library - Slightly more complex than plain markdown --- _Last Updated: 2025-01-01_