Architecture Atlas | RWS Architecture

Rendered folder index

Direct articles in this section

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

index

index / activeDC 3.0 Architecture Structure

DC 3.0 is the project-facing view across the architecture vault. It groups the target architecture into the workstreams used for planning, review, and delivery, while the domain fo

This is the primary navigation and storytelling layer for architecture content in the vault.

Position	Focus	Link
You are here	Primary design narrative and domain architecture intent	Architecture Atlas
Next view	Rationale and trade-offs behind architecture choices	Decisions (ADRs)

Architecture Storyline

Start with domain architecture notes to understand target-state intent and boundaries.
Use decisions, facts, and principles as supporting evidence rather than primary entry points.
Use TOGAF and workpackages as supporting views when you move from design to execution.

Authoring Mode

Prefer early architecture notes in status: draft to lower the start barrier.
Keep first drafts small and valid, then refine as ADRs mature.
Use workflow-draft-architecture-first for the minimum viable draft pattern.
Use workflow-architecture-promotion-checklist when deciding draft -> active -> approved.

Start Here

Platform Architecture for runtime and service patterns.
Network Architecture for topology and connectivity constraints.
Storage Architecture for persistence and data-service decisions.
Security Architecture for control objectives and trust boundaries.

Role Rails

Role	Recommended Path
Architect	Platform Architecture -> Platform ADRs -> DC 3.0 Building Block Lens
Engineer	Platform Architecture (or another domain hub) -> Delivery Work Packages -> implementation ADRs
Reviewer / Governance	Decisions (ADRs) -> DC 3.0 Building Block Lens -> referenced architecture notes

Domain Hubs

Domain	Architecture	Decisions	TOGAF	Delivery
Platform	Platform Architecture	Platform ADRs	fleet-management, red-hat-advanced-cluster-management, registry, red-hat-quay	wp-08-platform-services-automation, wp-09-caas-platform
Network	Network Architecture	Network ADRs	dc-network-structure, cisco-nx-os	wp-01-dc3-0-network-and-supporting-services, wp-11-legacy-workload-migration
Storage	Storage Architecture	Storage ADRs	block-file-s3-storage, red-hat-openshift-data-foundation	wp-04-dc3-0-storage, wp-16-business-continuity-and-disaster-recovery
Security	Security Architecture	Platform ADRs (IAM/Security)	smart-access, secrets-management	wp-06-security-posture-and-hardening, wp-07-identity-and-access-management-iam

Supporting Views

Decision rationale: Decisions (ADRs).
Facts and constraints: Facts and Taxonomy.
Principles and design guardrails: Principles.
Capability-to-solution mapping: DC 3.0 Building Block Lens.
Delivery planning: Delivery Work Packages.

flowchart LR A[Architecture Atlas] --> P[Platform Architecture] A --> N[Network Architecture] A --> S[Storage Architecture] A --> X[Security Architecture] A --> T[DC 3.0 Building Block Lens] A --> W[Delivery Work Packages]

Platform views: Platform Architecture
Network views: Network Architecture
Storage views: Storage Architecture
Security views: Security Architecture

Architecture Health

Indicator	Status	Notes
Domain Architecture Coverage	High	Platform, Network, Storage, and Security each have one canonical domain hub.
ADR Traceability	Medium	Most architecture domains link into decisions; deeper per-note ADR linkage is still needed in some notes.
DC 3.0 Building Block Lens Coverage	Medium	Core capability areas are mapped; some ABB/SBB edges still need tighter domain-level mapping.
Delivery Traceability	Medium	Main workpackage touchpoints are present, but acceptance criteria linkage is still uneven.