Rendered folder index
Section overview
Folders and articles are both available in the left browser. This panel promotes actual notes first.
Architecture is primary; ADRs capture the choices that make that architecture executable and governable.
| Lens Position | Focus | Link |
|---|---|---|
| You are here | Durable decision record with reasoning and consequences | Decisions (ADRs) |
| Next lens | Map decision context into ABB and SBB solution layers | DC 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
- Navigate by domain to inspect context-specific decisions.
- Jump back to architecture pages when you need full design narrative.
- Use domain decision indexes when you need lane-specific decision context.
Navigate by Domain
Domain Hubs
| Domain | Decision Index | Architecture | DC 3.0 Building Block Lens | Delivery Impact |
|---|---|---|---|---|
| Platform | Platform ADRs | Platform Architecture | fleet-management, openshift-gitops | wp-08-platform-services-automation, wp-09-caas-platform |
| Network | Network ADRs | Network Architecture | dc-network-structure, dc-network-structure | wp-01-dc3-0-network-and-supporting-services |
| Storage | Storage ADRs | Storage Architecture | block-file-s3-storage, red-hat-openshift-data-foundation | wp-04-dc3-0-storage, wp-16-business-continuity-and-disaster-recovery |
Architecture and Delivery Traceability
- Architecture domain lenses: Network Architecture, Platform Architecture, Storage Architecture, Security Architecture.
- DC 3.0 building-block decision traceability: DC 3.0 Building Block Lens.
- Delivery sequencing and implementation impact: Delivery Work Packages.
Lens Health
| Indicator | Status | Notes |
|---|---|---|
| ADR Naming and Structure Compliance | High | Filename, title prefix, and ID consistency are enforced by validator rules. |
| Domain Decision Coverage | High | Platform, Network, and Storage have dedicated decision lanes and indexes. |
| Draft ADR Review Discipline | Medium | Draft ADRs include explicit next decision triggers and review checkpoints. |
| Architecture Back-Link Quality | Medium | Most key ADRs are linked from architecture indexes; deeper note-level cross-linking remains incremental. |
| Delivery Impact Traceability | Medium | Workpackage linkage exists, but not all ADRs yet point to explicit implementation packages. |
- folder / indexNetwork DecisionsNetwork ADRs define connectivity, topology, addressing, and operational validation choices for the target architecture.
- folder / indexPlatform DecisionsPlatform ADRs capture runtime, identity, rollout strategy, and operational control decisions for the platform domain.
- folder / indexStorage DecisionsStorage ADRs establish persistence, data protection, and encryption choices across the platform.