Why this matters
ADR files in docs/adr/ capture the rationale behind impactful decisions so future contributors can understand trade-offs.
For changes that affect architecture, data models, external APIs, security posture, deployment topology, or cost (>10%), create an ADR in docs/adr/ using the standard template (Context, Decision, Consequences) and link the PR and issue IDs.
ADR files in docs/adr/ capture the rationale behind impactful decisions so future contributors can understand trade-offs.
Side-by-side examples engineers can pattern-match during review.
# Implement gRPC
// Switched REST to gRPC. No doc.# docs/adr/0007-adopt-grpc.md
## Context
High p99 latency on REST.
## Decision
Adopt gRPC for internal service-to-service calls.
## Consequences
Update gateway; monitor egress; PR #1234; Issue PROJ-56.docs/adr/0007-adopt-grpc.mdREADME: 'we changed to gRPC' (no ADR, no issue/PR links)From the same buckets as this rule.