Decisions and ADRs

RWS Architecture folder

Architecture is primary; ADRs capture the choices that make that architecture executable and governable.

RWS Architecture Vault / Decisions and ADRs

  1. Direct notes0
  2. Folders3
  3. Articles23
  4. Statusactive

Rendered folder index

Section overview

Folders and articles are both available in the left browser. This panel promotes actual notes first.

index

Architecture is primary; ADRs capture the choices that make that architecture executable and governable.

Lens PositionFocusLink
You are hereDurable decision record with reasoning and consequencesDecisions (ADRs)
Next lensMap decision context into ABB and SBB solution layersDC 3.0 Building Block Lens

Why This Section Exists

  • Use ADRs to document *why* specific design choices were made, including trade-offs and consequences.
  • Keep decision history durable over time, including superseded choices.
  • Provide traceability between architecture narratives, TOGAF mappings, and delivery work packages.

Start Here

  1. Navigate by domain to inspect context-specific decisions.
  2. Jump back to architecture pages when you need full design narrative.
  3. Use domain decision indexes when you need lane-specific decision context.

Domain Hubs

Architecture and Delivery Traceability

Lens Health

IndicatorStatusNotes
ADR Naming and Structure ComplianceHighFilename, title prefix, and ID consistency are enforced by validator rules.
Domain Decision CoverageHighPlatform, Network, and Storage have dedicated decision lanes and indexes.
Draft ADR Review DisciplineMediumDraft ADRs include explicit next decision triggers and review checkpoints.
Architecture Back-Link QualityMediumMost key ADRs are linked from architecture indexes; deeper note-level cross-linking remains incremental.
Delivery Impact TraceabilityMediumWorkpackage linkage exists, but not all ADRs yet point to explicit implementation packages.