Architecture Decision Records
ADRs capture the context and rationale behind architectural choices. Once an ADR is accepted, the decision is binding unless superseded by a later ADR with a higher number.
| Number | Title | Status | Source |
|---|---|---|---|
| ADR-001 | Rust Coding Standards | Accepted | View |
| ADR-002 | Edge Provenance and LSIF/Tree-sitter Precedence Policy | Accepted | View |
| ADR-003 | Personalized PageRank: Damping Factor, Convergence Tolerance, and Seed-Distribution Policy | Accepted | View |
| ADR-004 | Error Taxonomy | Accepted | View |
| ADR-005 | Per-Language Corpus Naming Convention | Accepted | View |
| ADR-006 | rust-analyzer Subprocess Trust Model | Accepted | View |
| ADR-007 | PCST Lambda Parameter Selection | Accepted | View |
| ADR-008 | Website Stack: Astro, Docusaurus, and Cloudflare Pages | Accepted | View |
Writing an ADR
Create a file docs/adrs/ADR-NNN-short-title.md in the main travsr repository using the template below. Open a pull request and tag it adr. The ADR is accepted when the pull request is merged.
# ADR-NNN: Title
**Date:** YYYY-MM-DD
**Status:** Proposed | Accepted | Superseded by ADR-NNN
## Context
What situation prompted this decision?
## Decision
What was decided, and how?
## Consequences
What are the results of this decision, positive and negative?