REPO-SYNCED SPEC DOC
Architecture Decision Records
This directory contains Architecture Decision Records (ADRs) documenting significant design decisions in the MCP-AQL protocol specification.
Source: spec/docs/adr/index.md
On this page
Jump to a section
Use the outline to move through longer pages without losing your place.
This directory contains Architecture Decision Records (ADRs) documenting significant design decisions in the MCP-AQL protocol specification.
ADR Index
| ADR | Title | Status | Summary |
|---|---|---|---|
| ADR-001 | CRUDE Pattern | Accepted | Extends CRUD with Execute endpoint for runtime operations |
| ADR-002 | GraphQL-Style Input Objects | Accepted | Nested input objects for update operations |
| ADR-003 | snake_case Parameters | Accepted | Standardizes on snake_case for LLM compatibility |
| ADR-004 | Schema-Driven Operations | Accepted | Declarative operation definitions as single source of truth |
| ADR-005 | Introspection System | Accepted | GraphQL-style runtime discovery via introspect operation |
| ADR-006 | Discriminated Responses | Accepted | { success, data } or { success, error } response format |
ADR Format
Each ADR follows this structure:
# ADR-NNN: Title
**Status:** Accepted | Proposed | Deprecated | Superseded
**Date:** YYYY-MM-DD
## Context
[Why this decision was needed]
## Decision
[What was decided, with RFC 2119 language where appropriate]
## Consequences
[Positive and negative outcomes]
## References
[Related ADRs or spec sections]Status Definitions
- Proposed: Under discussion, not yet accepted
- Accepted: Approved and in effect
- Deprecated: No longer recommended but still supported
- Superseded: Replaced by a newer ADR (link to replacement)
Contributing
When proposing a new ADR:
- Use the next available number (ADR-007, etc.)
- Follow the naming convention:
ADR-NNN-short-title.md - Use RFC 2119 keywords (MUST, SHOULD, MAY) for normative statements
- Focus on protocol-level decisions, not implementation details
- Update this index when adding new ADRs