Skip to main content
DraftWave 2Owner: TBDReviewers: unassignedLast review: not yet reviewed
Who should read this:ImplementersPolicy makers

ADR-0001 Record architecture decisions

In short
  • We record every significant architecture decision as a short Architecture Decision Record (ADR).
  • Each ADR states the context, the decision, the alternatives and the consequences.
  • ADRs are never deleted. A new ADR replaces an old one and says so.
FieldValue
StatusProposed
Date2026-09-18
DecidersArchitecture taskforce

Context​

Many organisations and countries build the Genome EDIC system over several years. People need to know why the system looks the way it does, including decisions taken before they joined.

Decision​

We record each significant architecture decision as an ADR in this chapter, using the ADR template. An ADR is "significant" when it affects more than one scope, changes an interface, or implements a governance choice.

Consequences​

  • Decisions and their reasons stay available to new taskforce members, auditors and Member Countries.
  • Writing an ADR takes time; the template is kept short to limit the effort.