Architecture Decision Records - Katana MCP Server¶
This directory contains Architecture Decision Records (ADRs) specific to the katana-mcp-server package.
What is an ADR?¶
An Architecture Decision Record (ADR) is a document that captures an important architectural decision made along with its context and consequences.
Format¶
We use the format proposed by Michael Nygard in his article Documenting Architecture Decisions:
- Title: A short noun phrase describing the decision
- Status: Proposed | Accepted | Deprecated | Superseded
- Context: What is the issue that we're seeing that is motivating this decision?
- Decision: What is the change that we're proposing and/or doing?
- Consequences: What becomes easier or more difficult to do because of this change?
ADR Lifecycle¶
- Proposed: The ADR is proposed and under discussion
- Accepted: The ADR has been accepted and is being implemented
- Deprecated: The ADR is no longer recommended but still in use
- Superseded: The ADR has been replaced by another ADR
Index¶
Accepted Architecture Decisions¶
Creating a New ADR¶
- Copy the template from the shared ADR directory
- Update the number (NNNN) to be the next sequential number
- Fill in the sections
- Create a PR for discussion
- After acceptance, update status to "Accepted"
Related Documentation¶
- Architecture Design - MCP architecture and patterns
- Implementation Plan - MCP v0.1.0 roadmap
- Development Guide - Development workflow
- Contributing Guide - Contribution guidelines
- Monorepo ADRs - Shared/monorepo-level ADRs