Architecture Decision Records
TruePPM keeps Architecture Decision Records (ADRs) at the source-of-record location in the monorepo, not in this docs site. ADRs change often during early development; mirroring them here would constantly drift.
Where the ADRs live
Section titled “Where the ADRs live”Each ADR is a markdown file using the Michael Nygard format. The numbering is monotonic; status (Proposed, Accepted, Deprecated, Superseded) is in the front matter.
Headline decisions
Section titled “Headline decisions”The ADRs most worth reading first if you are evaluating TruePPM:
- ADR-0011 — HistoricalRecords retention (90-day window for audit trail)
- ADR-0013 — REST endpoint design and the API-first principle
- ADR-0027 — Incremental CPM recompute (subgraph delta strategy)
- ADR-0030 — Project navigation shell (tab order, landing surface)
- ADR-0035 — Board PPM signals (CP, blocked, risk, EVM annotations)
- ADR-0036 — Hybrid PM philosophy and the sprint model — the wedge document; pairs with The Story
- ADR-0037 — Sprint model: data, API, board integration
- ADR-0040 — Schedule view: bar/drawer/gutter and the canvas renderer rationale
- ADR-0041 — Project methodology preset (tab visibility per planning model)
Why ADRs?
Section titled “Why ADRs?”Decisions matter more than code; code can change in a refactor, but the why is gone unless captured. ADRs prevent re-litigating the same trade-offs every quarter and give new contributors a way to understand the system without interrogating its authors.