ADRs record consequential, hard-to-reverse “why” decisions. The current cross-module mental model
lives in docs/architecture.md. Stable product direction lives in
docs/vision.md; current capability lives in module READMEs and
docs/conformance.md. Owner and conflict rules are in
AGENTS.md.
- ADR-001: Document Codec as the Product Boundary
- ADR-002: Preserve JSON:API Wire States
- ADR-003: Strict Construction and Aggregate Validation
- ADR-004: Configured Jackson Is the Mapping Authority
- ADR-005: Separate Linkage from Inclusion
- ADR-006: Document-First Deserialization
- ADR-007: Optional Adapter Modules
- ADR-008: JSpecify Nullness
- ADR-009: Architectural Tests for Module Boundaries
- ADR-010: Presence-Aware Resource PATCH Binding
- ADR-011: Distinct Whole-Object Meta Locations
- ADR-012: Major-Neutral Level-1 Application API Contract
- ADR-013: KazForge Namespace and Maven Group
- ADR-014: Unified Release Train and Version Semantics
- ADR-015: Share Mapping Semantics, Keep Native Wire Codecs