Skip to content

Repository navigation

README.md

Latest commit

 

History

History
60 lines (53 loc) · 5.31 KB

README.md

File metadata and controls

60 lines (53 loc) · 5.31 KB
Raw

Architecture decision records

ADRs record point-in-time decisions that affected Wright's observable product/compiler contract or component boundaries. They preserve rationale and consequences; they are not a database of current implementation reality.

Current architecture contracts are routed from docs/architecture/README.md. Source, Cargo metadata, tests, CI, integrations, and real-project runs establish implementation reality. An Accepted ADR means the decision was approved at that point in project history; it does not by itself prove that current code still conforms to the decision.

Conventions

  • Files use a zero-padded sequence and a short title, for example 0003-ir-boundary.md.
  • An ADR starts as Proposed and becomes Accepted when the decision is approved.
  • Superseded ADRs remain for history and link to the decision that replaces them.
  • An accepted ADR is not rewritten to hide history. A material change gets a new ADR when the rationale/decision history is worth preserving, while the current invariant is reflected in docs/architecture/ or another focused current contract.
  • Decisions state their scope, consequences, compatibility impact, and scope boundaries. Historical implementation mechanisms may remain in the record without becoming current architecture authority.
  • Do not use ADR status to encode current release versions, feature counts, migration progress, or Issue/PR state.

The post-ADR-0010 decision inventory records the candidate classification and source decisions for the backfill set covered by its audit date.

Index